From: Krzysztof Kozlowski <krzk@kernel.org>
To: Chanhong Jung <happycpu@gmail.com>
Cc: Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Ripard <mripard@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: gpio: fairchild,74hc595: add registers-default property
Date: Tue, 28 Apr 2026 10:40:50 +0200 [thread overview]
Message-ID: <006bd158-87aa-4fda-93cf-91f714fb72b6@kernel.org> (raw)
In-Reply-To: <20260423103347.4054425-1-happycpu@gmail.com>
On 23/04/2026 12:33, Chanhong Jung wrote:
> Hi Krzysztof,
>
> Thanks for the review.
>
>> You can fix the driver not to do that. Or fix the driver to properly
>> parse hogs. I don't understand why exactly this one driver needs
>> default registers stored in DT, but all other drivers in the kernel
>> don't.
>
> I thought about both, but I don't think either works for this chip.
>
> 74HC595/74LVC594 is pure write-only: no MISO path, no register
> read-back, and the data sheet defines the power-on state of the
> parallel outputs as whatever /SRCLR and /OE do before the SPI master
> is up. That's different from MCP23xxx, PCA953x, STMPE and the rest,
> which are either readable (so the driver can RMW) or have a defined
> reset value. None of those drivers need a seed property. This one
> does, because there is nothing to read back and no defined state to
> fall back on.
>
> Partial updates aren't possible either. set_value() has to shift the
> full chain every time - see __gen_74x164_write_config() - so whatever
This should also be explained in the commit msg.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-28 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 16:05 [PATCH v1 0/2] gpio: 74x164: seed the chain from DT at probe time Chanhong Jung
2026-04-22 16:05 ` [PATCH v1 1/2] dt-bindings: gpio: fairchild,74hc595: add registers-default property Chanhong Jung
2026-04-23 8:59 ` Krzysztof Kozlowski
2026-04-23 10:33 ` Chanhong Jung
2026-04-28 8:40 ` Krzysztof Kozlowski [this message]
2026-04-28 9:07 ` Linus Walleij
2026-04-22 16:05 ` [PATCH v1 2/2] gpio: 74x164: support 'registers-default' DT property for initial state Chanhong Jung
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=006bd158-87aa-4fda-93cf-91f714fb72b6@kernel.org \
--to=krzk@kernel.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=happycpu@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox