linux-kernel - Re: [PATCH 0/2] gpio: 74x164: use a compatible fallback and don't extend the driver

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: <75cf4aa1-e9ab-4c61-a577-b7b866f161c7@kernel.org>
Date: Sat, 11 Jan 2025 11:56:05 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Csókás Bence <csokas.bence@...lan.hu>,
 Bartosz Golaszewski <brgl@...ev.pl>, Linus Walleij
 <linus.walleij@...aro.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Maxime Ripard <mripard@...nel.org>,
 J . Neuschäfer <j.ne@...teo.net>,
 "Geert Uytterhoeven via gmail . com" <geert@...ux-m68k.org>
Cc: linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org,
 Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [PATCH 0/2] gpio: 74x164: use a compatible fallback and don't
 extend the driver

On 10/01/2025 14:32, Csókás Bence wrote:
> Hi,
> 
> On 2025. 01. 10. 14:00, Bartosz Golaszewski wrote:
>> From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
>>
>> There were other suggested solutions (for instance: just use the
>> existing compatible for the On Semi variant) but I figured the most
>> common approach is to use a fallback value for 100% compatible models
>> and this is what Rob suggested as well.
>>
>> This reverts the driver change and makes the "onnn,74hc595a" compatible
>> use "fairchild,74hc595" as fallback.
> 
> Is there any reason to introduce a new compatible name at all? Does some 

Yes, DT bindings preference, see writing bindings. I assume of course
this is a separate device. You cannot use other compatible "foo" for
some other device "bar".

Best regards,
Krzysztof