From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Matt Ranostay <mranostay@gmail.com>
Cc: zonque@gmail.com, linux-input@vger.kernel.org,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt: add cap11xx LED documentation
Date: Mon, 22 Jun 2015 10:59:14 -0700 [thread overview]
Message-ID: <20150622175914.GA15851@dtor-ws> (raw)
In-Reply-To: <1434599897-22505-2-git-send-email-mranostay@gmail.com>
On Wed, Jun 17, 2015 at 08:58:16PM -0700, Matt Ranostay wrote:
> Signed-off-by: Matt Ranostay <mranostay@gmail.com>
> ---
> .../devicetree/bindings/input/cap11xx.txt | 25 ++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/input/cap11xx.txt b/Documentation/devicetree/bindings/input/cap11xx.txt
> index 7d0a300..09cdc43 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.
Please mention the device does not allow controlling brightness of leds
individually and that is why this property is at device level, not
individual led level.
Also, why does it have "linux" prefix? It does not appear to control
any linux-specific functionality.
> +
> +
> Example:
>
> i2c_controller {
> @@ -55,5 +60,25 @@ i2c_controller {
> <105>, /* KEY_LEFT */
> <109>, /* KEY_PAGEDOWN */
> <104>; /* KEY_PAGEUP */
> +
> + linux,led-brightness = <15>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + 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
>
Thanks.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
next prev parent reply other threads:[~2015-06-22 17:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 3:58 [PATCH v5 0/2] cap11xx: add LED support Matt Ranostay
2015-06-18 3:58 ` [PATCH v5 1/2] dt: add cap11xx LED documentation Matt Ranostay
2015-06-18 6:49 ` Jacek Anaszewski
2015-06-22 17:59 ` Dmitry Torokhov [this message]
2015-06-23 8:36 ` Jacek Anaszewski
[not found] ` <55891A84.1070509-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-06-23 17:23 ` Matt Ranostay
2015-06-23 18:07 ` Dmitry Torokhov
2015-06-23 18:24 ` Matt Ranostay
[not found] ` <CAKzfze_n7hf629=aUb6j-tcPcBLcwTH-a8yLJWS0cLM=dOkEVQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-23 18:52 ` Dmitry Torokhov
2015-06-24 7:28 ` Jacek Anaszewski
2015-06-24 7:44 ` Jacek Anaszewski
2015-06-18 3:58 ` [PATCH v5 2/2] cap11xx: add LED support Matt Ranostay
2015-06-18 6:51 ` Jacek Anaszewski
2015-06-20 2:32 ` Matt Ranostay
2015-06-22 18:08 ` Dmitry Torokhov
2015-06-23 7:00 ` Jacek Anaszewski
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=20150622175914.GA15851@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mranostay@gmail.com \
--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).