On Thu, Jun 28, 2018 at 12:45 PM, Jernej Škrabec <jernej.skrabec@xxxxxxxx> wrote: > Dne četrtek, 28. junij 2018 ob 03:51:31 CEST je Chen-Yu Tsai napisal(a): >> On Mon, Jun 25, 2018 at 8:02 PM, Jernej Skrabec <jernej.skrabec@xxxxxxxx> > wrote: >> > TV TCONs (channel 1 only) are always connected to TV or HDMI encoder. >> > Because of that, all output endpoints on such TCON node will point to a >> > encoder which is part of component framework. >> > >> > Correct current graph traversing algorithm in such way that it doesn't >> > skip output enpoints with id 0 on TV TCONs. >> >> No. Our bindings say that endpoint 0 _is_ channel 0. For TCONs that don't >> have channel 0, it must be skipped. > > I'm not sure where this is stated. I read TCON binding again. Can you please > point me to it? https://elixir.bootlin.com/linux/latest/source/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt#L169 Our TCON driver still expects RGB or LVDS panel / bridges on endpoint 0. So I guess this was sort of implied historically. It's no longer true. This is something we should probably fix. In practice our drivers don't look at it (yet), but rely on the downstream encoder type to determine which channel to use. But please add the "allwinner,tcon-channel" property as specified in the binding. > So on TV TCONs on R40 (without channel 0) TVE would be endpoint 1 and HDMI > endpoint 2 (or the other way around)? Which one goes first doesn't quite matter. IIRC there's also a mux for TVE? ChenYu -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
