linux-kernel - Re: [PATCH v2] arm64: dts: renesas: r8a77961: Add lvds0 device node

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <82b37f1e-a461-8d16-219b-2319e11e1991@cogentembedded.com>
Date:   Fri, 24 Dec 2021 08:00:44 +0300
From:   Nikita Yushchenko <nikita.yoush@...entembedded.com>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Magnus Damm <magnus.damm@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Sergey Shtylyov <s.shtylyov@....ru>,
        Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] arm64: dts: renesas: r8a77961: Add lvds0 device node

>> +               lvds0: lvds@...90000 {
>> +                       compatible = "renesas,r8a7796-lvds";
> 
> This should be "renesas,r8a77961-lvds".
> To handle that, both the DT bindings[1] and the driver[2] should
> be updated.
> 
> [1] Documentation/devicetree/bindings/display/bridge/renesas,lvds.yaml
> [2] drivers/gpu/drm/rcar-du/rcar_lvds.c

Ok, will redo that way, although I don't really understand what for to have different compatible strings 
for exactly same IP inside different chips.

Also note that arch/arm64/boot/dts/renesas/r8a77951.dtsi currently has renesas,r8a7795-lvds

Nikita