Hi Sergei,
On Friday, 23 February 2018 11:51:59 EET Sergei Shtylyov wrote:
> On 2/21/2018 2:10 AM, Laurent Pinchart wrote:
> > The internal LVDS encoder now has DT bindings separate from the DU. Port
> > the device tree over to the new model.
> >
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@xxxxxxxxxxxxxxxx>
>
> [...]
>
> > diff --git a/arch/arm/boot/dts/r8a7791.dtsi
> > b/arch/arm/boot/dts/r8a7791.dtsi index 008a260f86a5..8660f8a329c7 100644
> > --- a/arch/arm/boot/dts/r8a7791.dtsi
> > +++ b/arch/arm/boot/dts/r8a7791.dtsi
>
> [...]
>
> > @@ -1126,6 +1123,33 @@
> > port@1 {
> > reg = <1>;
> > du_out_lvds0: endpoint {
> > + remote-endpoint = <&lvds0_in>;
> > + };
> > + };
> > + };
> > + };
> > +
> > + lvds0: lvds@feb90000 {
>
> I suggest that we use the label "lvds" w/o #, compatible with the manual...
The manual uses "LVDS" in some places (figure 25.1b or table 25.1 for
instance) and LVDS0 in other (table 25.3 for instance). I don't think this is
a big deal, and if we need to refer to the LVDS node by phandle, I'd rather
use lvds0 consistently on all SoCs to make writing shared DT sources easier.
--
Regards,
Laurent Pinchart
