All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen-Yu Tsai <wens@csie.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [linux-sunxi] Re: [RFC PATCH 0/3] sunxi: video: Add support for HDMI output on H3
Date: Wed, 14 Dec 2016 11:02:33 +0800	[thread overview]
Message-ID: <CAGb2v65sgv_hZoo3Mxn=97gbJvggB0ZPZ0A1gihTds+=nfuQ3w@mail.gmail.com> (raw)
In-Reply-To: <324251481663810@web33j.yandex.ru>

On Wed, Dec 14, 2016 at 5:16 AM, Icenowy Zheng <icenowy@aosc.xyz> wrote:
>
>
> 14.12.2016, 04:29, "Simon Glass" <sjg@chromium.org>:
>> Hi,
>>
>> On 12 December 2016 at 19:36, Jernej Skrabec <jernej.skrabec@siol.net> wrote:
>>>  This patch series add support for HDMI output. Support for other,
>>>  newer, SoCs, which also uses DE2 and same or similar HDMI controller
>>>  and PHY can be easily added later (A83T/A64/H5/R40). Current driver
>>>  can also be easily extended with TV out support, just like video
>>>  driver for older Allwinner SoCs.
>>>
>>>  While driver works, I would like to get few opinions first.
>>>  - From what I understand, drivers which supports DT are preferred.
>>>    Would it be better to rewrite this driver to support device tree?
>>
>> Yes I think so, and in fact it should use driver model also.
>>
>> The rockchip driver provides a reasonable example of how to split the
>> driver up as you suggest below. The VIDEO driver provides the
>> top-level video interface, DISPLAY drivers provide display output for
>> the video, and you have PANEL as well for receiving the display
>> output. VIDCONSOLE works automatically to display text.
>>
>> I actually took a bit of a look at this a few weeks ago so am happy to
>> help with review or discussions.
>
> Yes, I think go to Driver Model is also valuable, as Allwinner's display parts
> are really in reusable components.
>
> In addition, Driver Model provides the possibility to use EFI GOP, which can
> be a more standardized replacement of SimpleFB, especially for OSes other
> than Linux. (For example, Windows, if we can really get it running ;-) )

We're going to use EFI now? Doesn't EFI mean we have to leave another bit
of firmware in memory running under the OS? What about PSCI and ATF on
ARMv8?

ChenYu

>
>>
>>>  - TCON code is currently exactly the same as in driver for older
>>>    SoCs. Should I split it out into shared module? Also TV out code
>>>    seems to be similar, but I didn't manage to confirm that it works
>>>    as-is on H3.
>>>  - A80 SoC is mix of older display engine and newer HDMI controller,
>>>    so it doesn't really work with either of sunxi video drivers. Two
>>>    solutions I see here are either combine both driver into one massive
>>>    display driver or, much better, split everything by components
>>>    (TCON/DE/DE2/HDMI/TV) and instantiate compatible ones. I guess this
>>>    is not much different than adding support for DT in drivers. Note
>>>    that I don't have any A80 board, I'm just thinking ahead.
>>>
>>>  Best regards,
>>>  Jernej Skrabec
>>>
>>>  Jernej Skrabec (3):
>>>    sunxi: Add clocks for DE2/HDMI/TCON
>>>    sunxi: video: Add video driver for H3 SoC
>>>    sunxi: Enable H3 video driver in defconfigs
>>>
>>>   arch/arm/include/asm/arch-sunxi/clock_sun6i.h | 43 +
>>>   arch/arm/include/asm/arch-sunxi/cpu_sun4i.h | 8 +
>>>   arch/arm/include/asm/arch-sunxi/display2.h | 377 +++++++++
>>>   arch/arm/mach-sunxi/clock_sun6i.c | 28 +
>>>   board/sunxi/Kconfig | 4 +-
>>>   configs/orangepi_2_defconfig | 1 +
>>>   configs/orangepi_lite_defconfig | 1 +
>>>   configs/orangepi_one_defconfig | 1 +
>>>   configs/orangepi_pc_defconfig | 1 +
>>>   configs/orangepi_pc_plus_defconfig | 1 +
>>>   configs/orangepi_plus2e_defconfig | 1 +
>>>   configs/orangepi_plus_defconfig | 1 +
>>>   drivers/video/Makefile | 1 +
>>>   drivers/video/sunxi_display2.c | 1037 +++++++++++++++++++++++++
>>>   include/configs/sunxi-common.h | 17 +-
>>>   scripts/config_whitelist.txt | 1 +
>>>   16 files changed, 1516 insertions(+), 7 deletions(-)
>>>   create mode 100644 arch/arm/include/asm/arch-sunxi/display2.h
>>>   create mode 100644 drivers/video/sunxi_display2.c
>>>
>>>  --
>>>  2.10.2
>>
>> Regards,
>> Simon
>>
>> --
>> You received this message because you are subscribed to the Google Groups "linux-sunxi" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe at googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups "linux-sunxi" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe at googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

  reply	other threads:[~2016-12-14  3:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13  0:36 [U-Boot] [RFC PATCH 0/3] sunxi: video: Add support for HDMI output on H3 Jernej Skrabec
2016-12-13  0:36 ` [U-Boot] [RFC PATCH 1/3] sunxi: Add clocks for DE2/HDMI/TCON Jernej Skrabec
2016-12-13 15:18   ` Maxime Ripard
2016-12-13 19:20     ` Jernej Škrabec
2016-12-14  2:39       ` Chen-Yu Tsai
2016-12-13  0:36 ` [U-Boot] [RFC PATCH 2/3] sunxi: video: Add video driver for H3 SoC Jernej Skrabec
2016-12-13 15:40   ` Maxime Ripard
2016-12-13 16:33     ` Chen-Yu Tsai
2016-12-13 20:13     ` Jernej Škrabec
2016-12-14 10:28       ` Maxime Ripard
2016-12-14 22:11         ` Jernej Škrabec
2016-12-19 13:28           ` Maxime Ripard
2017-02-05 22:23   ` Rask Ingemann Lambertsen
2016-12-13  0:36 ` [U-Boot] [RFC PATCH 3/3] sunxi: Enable H3 video driver in defconfigs Jernej Skrabec
2016-12-13 20:28 ` [U-Boot] [RFC PATCH 0/3] sunxi: video: Add support for HDMI output on H3 Simon Glass
2016-12-13 21:16   ` [U-Boot] [linux-sunxi] " Icenowy Zheng
2016-12-14  3:02     ` Chen-Yu Tsai [this message]
2016-12-14  9:25       ` Maxime Ripard
2016-12-14  9:37         ` Alexander Graf
2016-12-14  9:51           ` Emmanuel Vadot
2016-12-20 10:47           ` Maxime Ripard
2016-12-14  8:37   ` [U-Boot] " Hans de Goede
2016-12-14  9:24     ` Maxime Ripard
2016-12-17 22:47     ` Simon Glass
2017-02-05 22:14 ` Rask Ingemann Lambertsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGb2v65sgv_hZoo3Mxn=97gbJvggB0ZPZ0A1gihTds+=nfuQ3w@mail.gmail.com' \
    --to=wens@csie.org \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.