Hi Jacopo, Thank you for the patch. On Thursday, 19 April 2018 12:31:03 EEST Jacopo Mondi wrote: > The THC63LVD1024 LVDS to RGB bridge supports two different input mapping > modes, selectable by means of an external pin. > > Describe the LVDS mode map through a newly defined mandatory property in > device tree bindings. > > Signed-off-by: Jacopo Mondi <jacopo+renesas@xxxxxxxxxx> > --- > .../devicetree/bindings/display/bridge/thine,thc63lvd1024.txt | 3 > +++ 1 file changed, 3 insertions(+) > > diff --git > a/Documentation/devicetree/bindings/display/bridge/thine,thc63lvd1024.txt > b/Documentation/devicetree/bindings/display/bridge/thine,thc63lvd1024.txt > index 37f0c04..0937595 100644 > --- > a/Documentation/devicetree/bindings/display/bridge/thine,thc63lvd1024.txt > +++ > b/Documentation/devicetree/bindings/display/bridge/thine,thc63lvd1024.txt > @@ -12,6 +12,8 @@ Required properties: > - compatible: Shall be "thine,thc63lvd1024" > - vcc-supply: Power supply for TTL output, TTL CLOCKOUT signal, LVDS input, > PPL and digital circuitry > +- thine,map: LVDS mapping mode selection signal, pin name "MAP". Shall be > <1> > + for mapping mode 1, <0> for mapping mode 2 That's sounds like an odd mapping. I suppose you have modeled it based on the state of the MAP pin instead of the mode number (MAP low means mode 2, MAP high means mode 1). To avoid confusing readers I would write it as - thine,map: level of the MAP pin that selects the LVDS mapping mode. Shall be <0> for low level (mapping mode 2) or <1> for high level (mapping mode 1). Apart from that this patch looks good to me. Reviewed-by: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> > Optional properties: > - powerdown-gpios: Power down GPIO signal, pin name "/PDWN". Active low > @@ -36,6 +38,7 @@ Example: > > vcc-supply = <®_lvds_vcc>; > powerdown-gpios = <&gpio4 15 GPIO_ACTIVE_LOW>; > + thine,map = <1>; > > ports { > #address-cells = <1>; -- Regards, Laurent Pinchart -- 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