From: <sean.wang@mediatek.com>
To: rpurdie@rpsys.net, jacek.anaszewski@gmail.com,
lee.jones@linaro.org, matthias.bgg@gmail.com, pavel@ucw.cz,
robh+dt@kernel.org, mark.rutland@arm.com
Cc: devicetree@vger.kernel.org, keyhaede@gmail.com,
Sean Wang <sean.wang@mediatek.com>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-leds@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] Documentation: devicetree: Add document bindings for leds-mt6323
Date: Wed, 8 Feb 2017 10:19:14 +0800 [thread overview]
Message-ID: <1486520357-13096-2-git-send-email-sean.wang@mediatek.com> (raw)
In-Reply-To: <1486520357-13096-1-git-send-email-sean.wang@mediatek.com>
From: Sean Wang <sean.wang@mediatek.com>
This patch adds documentation for devicetree bindings
for LED support on MT6323 PMIC
Signed-off-by: Sean Wang <sean.wang@mediatek.com>
Acked-by: Rob Herring <robh@kernel.org>
---
.../devicetree/bindings/leds/leds-mt6323.txt | 60 ++++++++++++++++++++++
1 file changed, 60 insertions(+)
create mode 100644 Documentation/devicetree/bindings/leds/leds-mt6323.txt
diff --git a/Documentation/devicetree/bindings/leds/leds-mt6323.txt b/Documentation/devicetree/bindings/leds/leds-mt6323.txt
new file mode 100644
index 0000000..82bbf0c
--- /dev/null
+++ b/Documentation/devicetree/bindings/leds/leds-mt6323.txt
@@ -0,0 +1,60 @@
+Device Tree Bindings for LED support on MT6323 PMIC
+
+MT6323 LED controller is subfunction provided by
+MT6323 PMIC, so the LED controller are defined as
+the subnode of the function node provided by MT6323
+PMIC controller that is being defined as one kind of
+Muti-Function Device (MFD) using shared bus called
+PMIC wrapper for each subfunction to access remote
+MT6323 PMIC hardware.
+
+For MT6323 MFD bindings see:
+Documentation/devicetree/bindings/mfd/mt6397.txt
+For MediaTek PMIC wrapper bindings see:
+Documentation/devicetree/bindings/soc/mediatek/pwrap.txt
+
+There's sub-node for the LED controller that describes
+the initial behavior for each LED physcially and currently
+only four LED sub-nodes could be supported.
+
+Required properties:
+- compatible : must be "mediatek,mt6323-led"
+
+Optional properties:
+- label : (optional)
+ see Documentation/devicetree/bindings/leds/common.txt
+- linux,default-trigger : (optional)
+ see Documentation/devicetree/bindings/leds/common.txt
+- default-state: (optional) The initial state of the LED
+ see Documentation/devicetree/bindings/leds/common.txt
+
+Example:
+
+&pwrap {
+ pmic: mt6323 {
+ compatible = "mediatek,mt6323";
+ interrupt-parent = <&pio>;
+ interrupts = <150 IRQ_TYPE_LEVEL_HIGH>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+
+ mt6323led: mt6323led{
+ compatible = "mediatek,mt6323-led";
+
+ led0: isink0 {
+ lebel = "LED0"
+ linux,default-trigger = "timer";
+ default-state = "on";
+ };
+ led1: isink1 {
+ label = "LED1";
+ default-state = "on";
+ };
+ led2: isink2 {
+ label = "LED2";
+ linux,default-trigger = "timer";
+ default-state = "off";
+ };
+ };
+ };
+};
--
1.9.1
next prev parent reply other threads:[~2017-02-08 2:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 2:19 [PATCH v2 0/4] leds: add leds-mt6323 support on MT7623 SoC sean.wang
2017-02-08 2:19 ` sean.wang [this message]
2017-02-08 2:47 ` [PATCH v2 1/4] Documentation: devicetree: Add document bindings for leds-mt6323 Andrew Lunn
[not found] ` <1486520357-13096-1-git-send-email-sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-02-08 2:19 ` [PATCH v2 2/4] Documentation: devicetree: Add LED subnode binding for MT6323 PMIC sean.wang-NuS5LvNUpcJWk0Htik3J/w
2017-02-08 12:22 ` Lee Jones
2017-02-08 2:19 ` [PATCH v2 3/4] leds: Add LED support " sean.wang
2017-02-08 21:00 ` Jacek Anaszewski
2017-02-09 6:09 ` Sean Wang
2017-02-09 14:23 ` Pavel Machek
2017-02-09 20:35 ` Jacek Anaszewski
2017-02-08 2:19 ` [PATCH v2 4/4] mfd: mt6397: Add MT6323 LED support into MT6397 driver sean.wang
2017-02-08 12:21 ` Lee Jones
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=1486520357-13096-2-git-send-email-sean.wang@mediatek.com \
--to=sean.wang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=keyhaede@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=rpurdie@rpsys.net \
/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).