Hi, On Sat, Feb 11, 2017 at 07:44:01PM +0200, Priit Laes wrote: > Add variable to enable either 'rgb' or 'lvds' output. > > Signed-off-by: Priit Laes <plaes@xxxxxxxxx> > --- > Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt b/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt > index b82c004..c367ede 100644 > --- a/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt > +++ b/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt > @@ -43,6 +43,9 @@ Required properties: > - reset-names: the reset names mentioned above > - clock-output-names: Name of the pixel clock created > > +- mode: Defines which encoder will be enabled. Values are 'rgb', 'lvds'. > + Defaults to 'rgb' if not set. > + Unfortunately, this won't really work. You could very well have two panels and switch from one to another by changing the pin muxing, so we have to use an enpoint for that. This is pretty much the same case that we have with the A10s where we need to have two output endpoints for the TV Encoder and HDMI, something we cannot support right now in our binding, since we assume that we have the two channels that only have one user, which turned out to be wrong. I guess an easy way would be to have an extra property defining which channel the endpoint is attached to. Thanks, Maxime -- Maxime Ripard, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
