From: "Rob Herring (Arm)" <robh@kernel.org>
To: Jun Yan <jerrysteve1101@gmail.com>
Cc: krzk+dt@kernel.org, conor+dt@kernel.org, lee@kernel.org,
luccafachinetti@gmail.com, linux-kernel@vger.kernel.org,
pzalewski@thegoodpenguin.co.uk, daniel@zonque.org,
devicetree@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH v4 3/5] dt-bindings: leds: leds-is31fl32xx: Add powerdown-gpios property
Date: Wed, 6 May 2026 16:49:17 -0500 [thread overview]
Message-ID: <177810415685.3271172.11733343287673514343.robh@kernel.org> (raw)
In-Reply-To: <20260505145354.1267095-4-jerrysteve1101@gmail.com>
On Tue, 05 May 2026 22:53:52 +0800, Jun Yan wrote:
> The IS31FL32XX series features an SDB shutdown pin.
> Driving it low (active low) places the chip into hardware shutdown mode
> for power saving, while all register contents are preserved
> and registers are not reset.
>
> Add powerdown-gpios property to describe the GPIO connected to the
> SDB pin of IS31FL32XX series LED controllers.
>
> Signed-off-by: Jun Yan <jerrysteve1101@gmail.com>
> ---
> .../devicetree/bindings/leds/issl,is31fl32xx.yaml | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-05-06 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 14:53 [PATCH v4 0/5] leds: Add powerdown gpio for is31fl32xx Jun Yan
2026-05-05 14:53 ` [PATCH v4 1/5] dt-bindings: leds: is31fl32xx: convert the binding to yaml Jun Yan
2026-05-05 14:53 ` [PATCH v4 2/5] dt-bindings: leds: leds-is31fl32xx: add support for is31fl3236a Jun Yan
2026-05-05 14:53 ` [PATCH v4 3/5] dt-bindings: leds: leds-is31fl32xx: Add powerdown-gpios property Jun Yan
2026-05-06 21:49 ` Rob Herring (Arm) [this message]
2026-05-05 14:53 ` [PATCH v4 4/5] leds: is31fl32xx: Add powerdown pin to exit hardware shutdown mode Jun Yan
2026-05-05 14:53 ` [PATCH v4 5/5] leds: is31f132xx: Fix missing brightness_steps for is31f13236 Jun Yan
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=177810415685.3271172.11733343287673514343.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=jerrysteve1101@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=luccafachinetti@gmail.com \
--cc=pzalewski@thegoodpenguin.co.uk \
/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