From: Grant Feng <von81@163.com>
To: von81@163.com, jacek.anaszewski@gmail.com, pavel@ucw.cz,
dmurphy@ti.com, robh+dt@kernel.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 2/2] leds: Add an optional property named 'sdb-gpios'
Date: Sat, 8 Aug 2020 10:04:39 +0800 [thread overview]
Message-ID: <20200808020439.20606-2-von81@163.com> (raw)
In-Reply-To: <20200808020439.20606-1-von81@163.com>
The chip enters hardware shutdown when the SDB pin is pulled low.
The chip releases hardware shutdown when the SDB pin is pulled high.
Signed-off-by: Grant Feng <von81@163.com>
---
Documentation/devicetree/bindings/leds/leds-is31fl32xx.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/leds/leds-is31fl32xx.txt b/Documentation/devicetree/bindings/leds/leds-is31fl32xx.txt
index 926c2117942c..94f02827fd83 100644
--- a/Documentation/devicetree/bindings/leds/leds-is31fl32xx.txt
+++ b/Documentation/devicetree/bindings/leds/leds-is31fl32xx.txt
@@ -15,6 +15,8 @@ Required properties:
- reg: I2C slave address
- address-cells : must be 1
- size-cells : must be 0
+- sdb-gpios : (optional)
+ Specifier of the GPIO connected to SDB pin.
LED sub-node properties:
- reg : LED channel number (1..N)
@@ -31,6 +33,7 @@ is31fl3236: led-controller@3c {
reg = <0x3c>;
#address-cells = <1>;
#size-cells = <0>;
+ sdb-gpios = <&gpio0 11 GPIO_ACTIVE_HIGH>;
led@1 {
reg = <1>;
--
2.17.1
next prev parent reply other threads:[~2020-08-08 2:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 2:04 [PATCH v2 1/2] leds: is31fl32xx: Add sdb pin and generate a 5ms low pulse when startup Grant Feng
2020-08-08 2:04 ` Grant Feng [this message]
2020-08-08 3:37 [PATCH v2 1/2] leds: is31fl319x: " Grant Feng
2020-08-08 3:37 ` [PATCH v2 2/2] leds: Add an optional property named 'sdb-gpios' Grant Feng
2020-08-24 22:21 ` Rob Herring
2020-08-25 8:05 ` Grant Feng
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=20200808020439.20606-2-von81@163.com \
--to=von81@163.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).