From: "Rob Herring (Arm)" <robh@kernel.org>
To: Chanhong Jung <happycpu@gmail.com>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, Linus Walleij <linusw@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Maxime Ripard <mripard@kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: gpio: fairchild,74hc595: add lines-initial-states property
Date: Tue, 5 May 2026 20:43:21 -0500 [thread overview]
Message-ID: <177803180135.280005.13996377729144610896.robh@kernel.org> (raw)
In-Reply-To: <20260429035134.1023330-2-happycpu@gmail.com>
On Wed, 29 Apr 2026 12:51:33 +0900, Chanhong Jung wrote:
> The 74HC595 and 74LVC594 shift registers latch their outputs until the
> first serial write, so boards that depend on a specific power-on pattern
> (for example active-low indicators, reset lines, or other signals that
> must come up non-zero) have no way to express that today: the Linux
> driver always writes zeros from its zero-initialised buffer during
> probe.
>
> Document support for the existing lines-initial-states bitmask, already
> defined for nxp,pcf8575, so the same convention covers this output-only
> device. Bit N corresponds to GPIO line N. Because the 74HC595/74LVC594
> family is push-pull output only (no input mode, no high-impedance state
> under software control), bit=0 drives the line low and bit=1 drives it
> high; this differs from nxp,pcf8575, where the 0/1 polarity reflects the
> quasi-bidirectional nature of that part.
>
> The bitmask covers up to 32 lines, which fits the typical 1-4 chip
> cascades that appear in tree. Should longer chains require seeding in
> the future, the property can be extended to a uint32-array without
> breaking the bit-N-equals-line-N convention.
>
> Suggested-by: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Chanhong Jung <happycpu@gmail.com>
> ---
> .../devicetree/bindings/gpio/fairchild,74hc595.yaml | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-05-06 1:43 UTC|newest]
Thread overview: 20+ 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
2026-04-28 9:07 ` Linus Walleij
2026-04-29 3:50 ` Chanhong Jung
2026-04-29 9:03 ` Bartosz Golaszewski
2026-05-05 9:45 ` Linus Walleij
2026-05-05 11:00 ` Bartosz Golaszewski
2026-05-05 20:24 ` Rob Herring
2026-04-22 16:05 ` [PATCH v1 2/2] gpio: 74x164: support 'registers-default' DT property for initial state Chanhong Jung
2026-04-29 3:51 ` [PATCH v2 0/2] gpio: 74x164: seed the chain from DT at probe time Chanhong Jung
2026-05-06 8:09 ` Bartosz Golaszewski
2026-04-29 3:51 ` [PATCH v2 1/2] dt-bindings: gpio: fairchild,74hc595: add lines-initial-states property Chanhong Jung
2026-04-30 12:08 ` Linus Walleij
2026-05-06 1:43 ` Rob Herring (Arm) [this message]
2026-04-29 3:51 ` [PATCH v2 2/2] gpio: 74x164: support lines-initial-states for boot-time output state Chanhong Jung
2026-04-30 12:09 ` Linus Walleij
2026-04-30 22:14 ` 정찬홍
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=177803180135.280005.13996377729144610896.robh@kernel.org \
--to=robh@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 \
/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