From: Matt Ranostay <mranostay@gmail.com>
To: zonque@gmail.com, dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, Matt Ranostay <mranostay@gmail.com>
Subject: [PATCH v4 1/2] dt: add cap11xx LED documentation
Date: Mon, 15 Jun 2015 19:46:09 -0700 [thread overview]
Message-ID: <1434422770-26896-2-git-send-email-mranostay@gmail.com> (raw)
In-Reply-To: <1434422770-26896-1-git-send-email-mranostay@gmail.com>
Signed-off-by: Matt Ranostay <mranostay@gmail.com>
---
.../devicetree/bindings/input/cap11xx.txt | 23 ++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/Documentation/devicetree/bindings/input/cap11xx.txt b/Documentation/devicetree/bindings/input/cap11xx.txt
index 7d0a300..01bb5b8 100644
--- a/Documentation/devicetree/bindings/input/cap11xx.txt
+++ b/Documentation/devicetree/bindings/input/cap11xx.txt
@@ -38,6 +38,11 @@ Optional properties:
defaults. The array must have exactly six
entries.
+ linux,led-brightness: Defines the ON brightness when the optional LED
+ functionality is used. Valid values are 1-15.
+ By default a value of 15 is set.
+
+
Example:
i2c_controller {
@@ -55,5 +60,23 @@ i2c_controller {
<105>, /* KEY_LEFT */
<109>, /* KEY_PAGEDOWN */
<104>; /* KEY_PAGEUP */
+
+ linux,led-brightness = <15>;
+
+ usr@0 {
+ label = "cap11xx:green:usr0";
+ reg = <0>;
+ };
+
+ usr@1 {
+ label = "cap11xx:green:usr1";
+ reg = <1>;
+ };
+
+ alive@2 {
+ label = "cap11xx:green:alive";
+ reg = <2>;
+ linux,default_trigger = "heartbeat";
+ };
};
}
--
1.9.1
next prev parent reply other threads:[~2015-06-16 2:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 2:46 [PATCH v4 0/2] cap118x: add LED support Matt Ranostay
2015-06-16 2:46 ` Matt Ranostay [this message]
2015-06-16 7:57 ` [PATCH v4 1/2] dt: add cap11xx LED documentation Jacek Anaszewski
2015-06-16 14:31 ` Matt Ranostay
2015-06-16 2:46 ` [PATCH v4 2/2] cap11xx: add LED support Matt Ranostay
2015-06-16 7:54 ` Jacek Anaszewski
2015-06-16 14:39 ` Matt Ranostay
2015-06-16 21:26 ` Daniel Mack
2015-06-16 21:55 ` Matt Ranostay
2015-06-17 6:34 ` Matt Ranostay
[not found] ` <CAKzfze8629xyiz1wufjoGbOu+npDRXyCgyGEhxY_1h7XHKeTQg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-17 6:49 ` Matt Ranostay
2015-06-17 8:59 ` Daniel Mack
2015-06-17 21:53 ` Matt Ranostay
[not found] ` <CAKzfze-H=m55j-1ty4xOkrVzMswU7FpXe=6pHq4ws=P+3vcZNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-17 22:38 ` Dmitry Torokhov
2015-06-17 23:36 ` Matt Ranostay
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=1434422770-26896-2-git-send-email-mranostay@gmail.com \
--to=mranostay@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=zonque@gmail.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 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).