Hi Laurent, On Fri, Feb 14, 2020 at 03:10:25PM +0200, Laurent Pinchart wrote: > Hi Maxime, > > Thank you for the patch. > > On Fri, Feb 14, 2020 at 01:32:43PM +0100, Maxime Ripard wrote: > > SoCs that have multiple TCONs can use the two set of pins on the first TCON > > to drive a dual-link display. Add a property to enable the dual link. > > > > Signed-off-by: Maxime Ripard <maxime@xxxxxxxxxx> > > --- > > .../bindings/display/allwinner,sun4i-a10-tcon.yaml | 7 +++++++ > > 1 file changed, 7 insertions(+) > > > > diff --git a/Documentation/devicetree/bindings/display/allwinner,sun4i-a10-tcon.yaml b/Documentation/devicetree/bindings/display/allwinner,sun4i-a10-tcon.yaml > > index 86ad617d2327..aa6dd8409dbc 100644 > > --- a/Documentation/devicetree/bindings/display/allwinner,sun4i-a10-tcon.yaml > > +++ b/Documentation/devicetree/bindings/display/allwinner,sun4i-a10-tcon.yaml > > @@ -105,6 +105,13 @@ properties: > > - const: edp > > - const: lvds > > > > + allwinner,lvds-dual-link: > > + type: boolean > > + description: | > > + On a SoC with two TCON with LVDS support, the first TCON can > > + operate over both pins sets to output in a dual-link setup. This > > + will be triggered by setting this property. > > Could you maybe provide an example of how this property is supposed to > be used ? I'm especially wondering what ports are used in that case and > how they're connected. It's pretty trivial to support, it's only a property to set on the encoder node itself. I'm not really sure what you meant by your question with the ports though :/ Maxime
Attachment:
signature.asc
Description: PGP signature
