linux-kernel - Re: [PATCH v2 3/3] dt-bindings: gpio: fairchild,74hc595: Document chip select vs. latch clock

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] [day] [month] [year] [list]

Message-ID: <CACRpkdZwN0reH7K0e0wN9d30DJkyHVoBAaG9tk-+MELjOHeh_w@mail.gmail.com>
Date: Fri, 27 Dec 2024 09:39:16 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: j.ne@...teo.net
Cc: Bartosz Golaszewski <brgl@...ev.pl>, Rob Herring <robh@...nel.org>, 
	Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, 
	Maxime Ripard <mripard@...nel.org>, linux-gpio@...r.kernel.org, devicetree@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 3/3] dt-bindings: gpio: fairchild,74hc595: Document
 chip select vs. latch clock

On Tue, Dec 24, 2024 at 9:02 AM J. Neuschäfer via B4 Relay
<devnull+j.ne.posteo.net@...nel.org> wrote:

> From: "J. Neuschäfer" <j.ne@...teo.net>
>
> From looking at the data sheets, it is not obvious that CS# and latch
> clock can be treated at the same, but doing so works fine and saves the
> hassle of (1) trying to specify a SPI device without CS, and (2) adding
> another property to drive the latch clock[1].
>
> [1]: https://lore.kernel.org/lkml/20241213-gpio74-v1-2-fa2c089caf41@posteo.net/
>
> Signed-off-by: J. Neuschäfer <j.ne@...teo.net>

Fair enough!
Reviewed-by: Linus Walleij <linus.walleij@...aro.org>

Yours,
Linus Walleij