On Fri, Dec 13, 2024 at 06:32:48PM +0100, J. Neuschäfer wrote: > The Fairchild MM74HC595 and other compatible parts have a latch clock > input (also known as storage register clock input), which must be > clocked once in order to apply any value that was serially shifted in. That sounds like all the existing parts have the signal and it is required to operate? Or just needed to write settings, but not read GPIO input state for example? If the new parts are usable without latch, then they should have a fallback compatible. If they aren't usable, then it should be 1 binding patch. > > This patch adds a latch-gpios property to the binding to allow > specifying a GPIO that connects to the latch clock. > > Signed-off-by: J. Neuschäfer <j.ne@xxxxxxxxxx> > --- > Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml b/Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml > index 629cf9b2ab8e4a63fbe17f56792a46d2066d40c3..38d473a3852154e53faec88dc911dc0a4f9cbd1f 100644 > --- a/Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml > +++ b/Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml > @@ -34,6 +34,10 @@ properties: > description: GPIO connected to the OE (Output Enable) pin. > maxItems: 1 > > + latch-gpios: > + description: GPIO connected to the latch clock or storage register clock pin. > + maxItems: 1 > + > patternProperties: > "^(hog-[0-9]+|.+-hog(-[0-9]+)?)$": > type: object > > -- > 2.45.2 >
