linux-kernel - Re: [v7 1/7] dt-bindings: display: panel: Add himax hx83102 panel bindings

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: <CACRpkdZuX1gi8No1eOC2GjCZOA-1vh5iBokR75dXmc4SLy6ROA@mail.gmail.com>
Date: Tue, 28 May 2024 13:22:21 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Cong Yang <yangcong5@...qin.corp-partner.google.com>
Cc: sam@...nborg.org, neil.armstrong@...aro.org, daniel@...ll.ch, 
	dianders@...omium.org, krzysztof.kozlowski+dt@...aro.org, robh+dt@...nel.org, 
	conor+dt@...nel.org, airlied@...il.com, dmitry.baryshkov@...aro.org, 
	dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org, 
	linux-kernel@...r.kernel.org, xuxinxiong@...qin.corp-partner.google.com, 
	Conor Dooley <conor.dooley@...rochip.com>
Subject: Re: [v7 1/7] dt-bindings: display: panel: Add himax hx83102 panel bindings

On Wed, May 15, 2024 at 3:46 AM Cong Yang
<yangcong5@...qin.corp-partner.google.com> wrote:

> In V1, discussed with Doug and Linus [1], we need break out as separate
> driver for the himax83102-j02 controller. Beacuse "starry,himax83102-j02"
> and in this series "BOE nv110wum-l60" "IVO t109nw41" panels use same
> controller, they have some common CMDS. So add new documentation for
> this panels.
>
> For himax83102-j02 controller, no need 3v3 supply, so remove it.
>
> [1]: https://lore.kernel.org/all/CACRpkdbzYZAS0=zBQJUC4CB2wj4s1h6n6aSAZQvdMV95r3zRUw@mail.gmail.com
>
> Signed-off-by: Cong Yang <yangcong5@...qin.corp-partner.google.com>
> Reviewed-by: Conor Dooley <conor.dooley@...rochip.com>

Nice work,
Reviewed-by: Linus Walleij <linus.walleij@...aro.org>

Yours,
Linus Walleij