devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Icenowy Zheng <icenowy@aosc.io>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree <devicetree@vger.kernel.org>,
	Mike Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-sunxi <linux-sunxi@googlegroups.com>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Chen-Yu Tsai <wens@csie.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 7/15] dt-bindings: display: sun4i: Add allwinner,tcon-channel property
Date: Tue, 28 Mar 2017 18:05:08 +0800	[thread overview]
Message-ID: <20170328100519.145DE203419@relay.mailchannels.net> (raw)


2017年3月27日 上午5:11于 Maxime Ripard <maxime.ripard@free-electrons.com>写道:
>
> On Fri, Mar 17, 2017 at 11:34:45AM +0800, Chen-Yu Tsai wrote: 
> > On Thu, Mar 16, 2017 at 1:37 AM, Rob Herring <robh@kernel.org> wrote: 
> > > On Tue, Mar 07, 2017 at 09:56:26AM +0100, Maxime Ripard wrote: 
> > >> The Allwinner Timings Controller has two, mutually exclusive, channels. 
> > >> When the binding has been introduced, it was assumed that there would be 
> > >> only a single user per channel in the system. 
> > >> 
> > >> While this is likely for the channel 0 which only connects to LCD displays, 
> > >> it turns out that the channel 1 can be connected to multiple controllers in 
> > >> the SoC (HDMI and TV encoders for example). And while the simultaneous use 
> > >> of HDMI and TV outputs cannot be achieved, switching from one to the other 
> > >> at runtime definitely sounds plausible. 
> > >> 
> > >> Add an extra property, allwinner,tcon-channel, to specify for a given 
> > >> endpoint which TCON channel it is connected to, while falling back to the 
> > >> previous mechanism if that property is missing. 
> > > 
> > > I think perhaps TCON channels should have been ports rather than 
> > > endpoints. The fact that the channels are mutually exclusive can be 
> > > handled in the driver and doesn't really matter in the binding. How 
> > > painful would it be to rework things to move TCON channel 1 from port 0, 
> > > endpoint 1 to port 1? 
> > 
> > Having a separate output port for channel 1 was one option we discussed. 
> > However it wouldn't work well with the kernel's of_graph based crtc 
> > detection (drm_of_find_possible_crtcs / drm_of_find_possible_crtcs), 
> > which has the crtcs bound via the output port. As the logic is used 
> > by multiple drivers, I'm not sure it's easy to rework or test. 
>
> Can't we use a different logic than drm_of_find_possible_crtcs to fill 
> the same role? 
>
> > Also, we still have to support old device trees using channel 1 from 
> > output port 0 endpoint 1. This is the TV encoder on sun5i (A10s/A13/R8). 

And from A83T on we will face channel-1 only TCONs., which do not
have channel 0 at all in hardware.

>
> We could probably work something out if we go that way to deal with 
> old DTs though. 
>
> Maxime 
>
> -- 
> Maxime Ripard, Free Electrons 
> Embedded Linux and Kernel engineering 
> http://free-electrons.com
>
> _______________________________________________ 
> linux-arm-kernel mailing list 
> linux-arm-kernel@lists.infradead.org 
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel 
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-03-28 10:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 10:05 Icenowy Zheng [this message]
     [not found] ` <20170328100519.145DE203419-Y9/x5g2N/Tt0ykcd9G8QkxTxI0vvWBSX@public.gmane.org>
2017-03-29 12:31   ` [PATCH 7/15] dt-bindings: display: sun4i: Add allwinner,tcon-channel property Maxime Ripard
  -- strict thread matches above, loose matches on Subject: below --
2017-03-28 10:05 Icenowy Zheng
2017-03-07  8:56 [PATCH 0/15] drm: sun4i: Add support for the HDMI controller Maxime Ripard
2017-03-07  8:56 ` [PATCH 7/15] dt-bindings: display: sun4i: Add allwinner, tcon-channel property Maxime Ripard
     [not found]   ` <46fdec2d680d539652f87d79c627973b3a568438.1488876832.git-series.maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2017-03-08  3:38     ` [PATCH 7/15] dt-bindings: display: sun4i: Add allwinner,tcon-channel property Chen-Yu Tsai
2017-03-15 17:37     ` Rob Herring
2017-03-17  3:34       ` Chen-Yu Tsai
     [not found]         ` <CAGb2v67A2T4KeLBttAGLKoo7igBTnQH+5yxN-jJo1k7Ewfd9mQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-26 21:11           ` 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=20170328100519.145DE203419@relay.mailchannels.net \
    --to=icenowy@aosc.io \
    --cc=daniel.vetter@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.org \
    --cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).