public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: icenowy@aosc.xyz (Icenowy Zheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Re: [RFC PATCH] ARM: dts: sun8i: add simplefb node for H3
Date: Thu, 01 Dec 2016 10:02:59 +0800	[thread overview]
Message-ID: <1777251480557779@web18m.yandex.ru> (raw)
In-Reply-To: <20161130205233.mwfqlfuqg4cefink@lukather>



01.12.2016, 04:52, "Maxime Ripard" <maxime.ripard@free-electrons.com>:
> On Wed, Nov 30, 2016 at 09:41:26PM +0100, Jernej ?krabec wrote:
>> ?> > > > The only
>> ?> > > > code left from you is for DE2. HDMI stuff is basically copied from
>> ?> > > > Rockhip
>> ?> > > > driver (including EDID reading), TCON code is now reverted to the same
>> ?> > > > as
>> ?> > > > it is in sunxi_display.c. I think it is worth to take a look at EDID
>> ?> > > > code
>> ?> > > > and compare it.
>> ?> > >
>> ?> > > So is the TCON of DE 2.0 identical to the original TCON?
>> ?> > >
>> ?> > > If so, we should reuse sun4i-tcon ...
>> ?> >
>> ?> > Well, TCON is splitted in two parts (two base addresses), one for HDMI and
>> ?> > one for TV. However, register offsets are same as before, so I guess
>> ?> > driver reusage make sense. I think that there are few additional
>> ?> > registers, but they can be ignored for simplefb.
>> ?>
>> ?> The TCON1 of the H3 is not usable (no ckock). Analog TV has its own
>> ?> clock and I/O area.
>> ?>
>>
>> ?True, H3 user manual can be misleading sometimes. But this doesn't change the
>> ?fact that TCON0 has same register offsets with same meaning.
>
> Then yes, we should definitely share the drivers too. So, in the end,
> the only thing that is actually new is the display-engine?

And HDMI PHY on H3 ;-)

In my opinion, we should just put sun8i-de2-drm related code into drivers/gpu/drm/sun4i/ .
(Or rename the directory to sunxi)

>
> Maxime
>
> --
> Maxime Ripard, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com

  reply	other threads:[~2016-12-01  2:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20161130220324.3Kg4VPEw@smtp1m.mail.yandex.net>
2016-11-30 19:14 ` [linux-sunxi] Re: [RFC PATCH] ARM: dts: sun8i: add simplefb node for H3 Jernej Škrabec
2016-11-30 19:37   ` Jean-Francois Moine
2016-11-30 20:41     ` Jernej Škrabec
2016-11-30 20:52       ` Maxime Ripard
2016-12-01  2:02         ` Icenowy Zheng [this message]
2016-12-01  8:45           ` Maxime Ripard
2016-11-28  9:59 Icenowy Zheng
2016-11-28 10:06 ` Chen-Yu Tsai
2016-11-28 10:19   ` Icenowy Zheng
2016-11-28 10:24     ` [linux-sunxi] " Chen-Yu Tsai
2016-11-29 21:43       ` Maxime Ripard

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=1777251480557779@web18m.yandex.ru \
    --to=icenowy@aosc.xyz \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox