From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Matt Ranostay <mranostay@gmail.com>
Cc: Daniel Mack <zonque@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
linux-leds@vger.kernel.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] dt: add cap11xx LED documentation
Date: Mon, 15 Jun 2015 12:10:33 +0200 [thread overview]
Message-ID: <557EA499.2020701@samsung.com> (raw)
In-Reply-To: <CAKzfze9Ji73youadk9zzqahN6E4VCJUXOgzmP4wnoynrQSwRMQ@mail.gmail.com>
On 06/15/2015 10:48 AM, Matt Ranostay wrote:
> On Mon, Jun 15, 2015 at 1:15 AM, Jacek Anaszewski
> <j.anaszewski@samsung.com> wrote:
>> Hi Matt,
>>
>> On 06/13/2015 06:17 AM, Matt Ranostay wrote:
>>>
>>> Some cap11xx devices have LEDs that can be controlled from userpace
>>> and via triggers. Document their use and functionality here.
>>>
>>> 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..ef89c27 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
>>> 0-15.
>>> + By default a value of 15 is set.
>>
>>
>> The ON brightness is controlled with the 'brightness' sysfs property.
>> The levels start from 1 and 0 turns the LED off. I think that this
>> property is useless then.
>>
>
> Yes but this defines the brightness for the ON state.. since it can be
> from 0-100% duty cycle.
Doesn't 0 mean that LED is off? If so, then valid values should start
from 1.
>>
>>> +
>>> 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";
>>> + };
>>> };
>>> }
>>>
>>
>> --
>> Best Regards,
>> Jacek Anaszewski
>
--
Best Regards,
Jacek Anaszewski
next prev parent reply other threads:[~2015-06-15 10:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 4:17 [PATCH v3 0/2] cap11xx: Add LED support to driver Matt Ranostay
2015-06-13 4:17 ` [PATCH v3 1/2] dt: add cap11xx LED documentation Matt Ranostay
2015-06-15 8:15 ` Jacek Anaszewski
[not found] ` <557E8990.5060702-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-06-15 8:48 ` Matt Ranostay
2015-06-15 10:10 ` Jacek Anaszewski [this message]
2015-06-15 17:00 ` Matt Ranostay
2015-06-13 4:17 ` [PATCH v3 2/2] cap11xx: add LED support Matt Ranostay
2015-06-15 8:15 ` Jacek Anaszewski
2015-06-15 8:56 ` Matt Ranostay
2015-06-15 9:03 ` Daniel Mack
2015-06-15 17:01 ` Matt Ranostay
2015-06-15 10:11 ` Jacek Anaszewski
2015-06-15 17:02 ` 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=557EA499.2020701@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--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).