Hi Sergei, On Friday, 12 January 2018 17:14:33 EET Sergei Shtylyov wrote: > On 01/12/2018 03:58 AM, Laurent Pinchart wrote: > > The internal LVDS encoders now have their own DT bindings, representing > > them as part of the DU is deprecated. > > > > Signed-off-by: Laurent Pinchart > > <laurent.pinchart+renesas@xxxxxxxxxxxxxxxx> > > --- > > > > .../devicetree/bindings/display/renesas,du.txt | 26 ++++++++--------- > > 1 file changed, 11 insertions(+), 15 deletions(-) > > > > diff --git a/Documentation/devicetree/bindings/display/renesas,du.txt > > b/Documentation/devicetree/bindings/display/renesas,du.txt index > > cd48aba3bc8c..8f6e0e118e3e 100644 > > --- a/Documentation/devicetree/bindings/display/renesas,du.txt > > +++ b/Documentation/devicetree/bindings/display/renesas,du.txt > > > > @@ -17,9 +17,7 @@ Required Properties: > > - reg: A list of base address and length of each memory resource, one > > for > > each entry in the reg-names property. > > - reg-names: Name of the memory resources. The DU requires one memory > > > > - resource for the DU core (named "du") and one memory resource for > > each > > - LVDS encoder (named "lvds.x" with "x" being the LVDS controller > > numerical > > - index). > > + resource for the DU core (named "du"). > > Could we get rid of this prop altogether? Actually yes, as unlike what I thought the driver doesn't use it. I'll drop it in v2. -- Regards, Laurent Pinchart
