From: Jun Yan <jerrysteve1101@gmail.com>
To: linusw@kernel.org
Cc: alexandre.torgue@st.com, andersson@kernel.org,
andre.przywara@arm.com, andrew@lunn.ch, baruch@tkos.co.il,
conor+dt@kernel.org, devicetree@vger.kernel.org,
gregory.clement@bootlin.com, jerrysteve1101@gmail.com,
konradybcio@kernel.org, krzk+dt@kernel.org, krzk@kernel.org,
lee@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, paul.barker@sancloud.com,
pavel@kernel.org, pavel@ucw.cz, peda@axentia.se,
robert.marko@sartura.hr, robh@kernel.org,
romain.perier@gmail.com, sebastian.hesselbarth@gmail.com,
vincent.knecht@mailoo.org, von81@163.com, xuwei5@hisilicon.com
Subject: Re: [PATCH 2/5] leds: is31fl319x: Fix shutdown GPIO initial state and remove redundant startup pulse
Date: Wed, 13 May 2026 22:44:10 +0800 [thread overview]
Message-ID: <20260513144414.244968-1-jerrysteve1101@gmail.com> (raw)
In-Reply-To: <CAD++jLk0BrV+MAh4n6+wAqNX+O8BcHcoehbX574F2_Vcm4qvGQ@mail.gmail.com>
> On Fri, May 8, 2026 at 5:26=E2=80=AFPM Jun Yan <jerrysteve1101@gmail.com> w=
> rote:
>
> > 1. Per IS31FL319x datasheet [1], the hardware shutdown pin (SDB) is
> > active-low.
>
> So that means that driving the line low will shut down the hardware.
Yes, that is right.
>
> > - is31->shutdown_gpio =3D devm_gpiod_get_optional(dev, "shutdown", =
> GPIOD_OUT_HIGH);
> > + is31->shutdown_gpio =3D devm_gpiod_get_optional(dev, "shutdown", =
> GPIOD_OUT_LOW);
>
> Add a comment here that this will in fact drive the line high,
> because the GPIO line will be flagged as GPIO_ACTIVE_LOW
> in the provider (such as the device tree).
>
> At least write this in the commit message, it's a missing piece
> that helps readers understand what is going on.
Okay, I will add the necessary comment in the V2 version.
>
> Have you checked any existing device trees so you don't
> break something here?
I have modified the problematic device trees and CC'd
the relevant platform mailing lists as well as the device‑tree mailing list [1].
[1] https://lore.kernel.org/linux-devicetree/20260508152435.21389-1-jerrysteve1101@gmail.com/
>
> If you're breaking platforms you may need a fixup in
> drivers/gpio/gpiolib-of.c to force the consumer active
> low for legacy device trees.
Thanks for the reminder. I will add the necessary fixup in the V2 version.
>
> Yours,
> Linus Walleij
>
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2026-05-13 14:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 15:24 [PATCH 0/5] leds: is31fl319x: Fix shutdown GPIO and update DT bindings Jun Yan
2026-05-08 15:24 ` [PATCH 1/5] dt-bindings: leds: issi,is31fl319x: Add description for the shutdown-gpios property Jun Yan
2026-05-13 23:26 ` Rob Herring (Arm)
2026-05-08 15:24 ` [PATCH 2/5] leds: is31fl319x: Fix shutdown GPIO initial state and remove redundant startup pulse Jun Yan
2026-05-11 9:10 ` Linus Walleij
2026-05-13 14:44 ` Jun Yan [this message]
2026-05-13 15:54 ` Dmitry Baryshkov
2026-05-08 15:24 ` [PATCH 3/5] arm64: dts: qcom: msm8916-alcatel-idol347: Fix sn3190 shutdown GPIO polarity Jun Yan
2026-05-14 10:58 ` Konrad Dybcio
2026-05-08 15:24 ` [PATCH 4/5] ARM: dts: qcom: msm8974-oneplus-bacon: Fix sn3193 " Jun Yan
2026-05-14 10:58 ` Konrad Dybcio
2026-05-08 15:24 ` [PATCH 5/5] arm64: dts: marvell: armada-7040-mochabin: Fix is31fl3199 " Jun Yan
2026-05-13 15:56 ` [PATCH 0/5] leds: is31fl319x: Fix shutdown GPIO and update DT bindings Dmitry Baryshkov
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=20260513144414.244968-1-jerrysteve1101@gmail.com \
--to=jerrysteve1101@gmail.com \
--cc=alexandre.torgue@st.com \
--cc=andersson@kernel.org \
--cc=andre.przywara@arm.com \
--cc=andrew@lunn.ch \
--cc=baruch@tkos.co.il \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=paul.barker@sancloud.com \
--cc=pavel@kernel.org \
--cc=pavel@ucw.cz \
--cc=peda@axentia.se \
--cc=robert.marko@sartura.hr \
--cc=robh@kernel.org \
--cc=romain.perier@gmail.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=vincent.knecht@mailoo.org \
--cc=von81@163.com \
--cc=xuwei5@hisilicon.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.