From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: cooloney@gmail.com, rpurdie@rpsys.net,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
Matthew.Fatheree@belkin.com
Subject: Re: [PATCH RESEND v6 2/2] leds: tlc591xx: Driver for the TI 8/16 Channel i2c LED driver
Date: Mon, 20 Apr 2015 15:07:31 +0200 [thread overview]
Message-ID: <5534FA13.9090502@samsung.com> (raw)
In-Reply-To: <20150420115959.GA8050@lunn.ch>
On 04/20/2015 01:59 PM, Andrew Lunn wrote:
> On Mon, Apr 20, 2015 at 11:06:09AM +0200, Jacek Anaszewski wrote:
>> Hi Andrew,
>>
>> Very nice driver.
>
> Thanks. I just hope it gets accepted into this merge window.
>
>> I have one question below.
>
[...]
>>> +static int
>>> +tlc591xx_configure(struct device *dev,
>>> + struct tlc591xx_priv *priv,
>>> + const struct tlc591xx *tlc591xx)
>>> +{
>>> + unsigned int i;
>>> + int err = 0;
>>> +
>>> + tlc591xx_set_mode(priv->regmap, MODE2_DIM);
>>
>> It seems that all leds will be initially turned on, in dim mode.
>> This shouldn't be fixed and probably an optional 'led-mode' DT node
>> property should be provided for defining the initial state. It would
>> default to OFF if not present.
>
> If you look further down, you will find
>
>>> + priv->leds[reg].ldev.default_trigger =
>>> + of_get_property(child, "linux,default-trigger", NULL);
>
> This is the normal way in DT to specify the default on/off/keep
> current value/heartbeat etc.
OK, I was initially thinking that initializing LED to MODE2_DIM
turns the LED on.
Acked-by: Jacek Anaszewski <j.anaszewski@samsung.com>
--
Best Regards,
Jacek Anaszewski
next prev parent reply other threads:[~2015-04-20 13:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 22:08 [PATCH RESEND v6 0/2] Driver for TI tlc591xx 8/16 Channel i2c LED driver Andrew Lunn
2015-03-17 22:08 ` [PATCH RESEND v6 1/2] leds: tlc591xx: Document binding for the TI " Andrew Lunn
2015-04-20 13:09 ` Jacek Anaszewski
2015-04-20 17:46 ` Bryan Wu
2015-03-17 22:08 ` [PATCH RESEND v6 2/2] leds: tlc591xx: Driver " Andrew Lunn
2015-04-20 9:06 ` Jacek Anaszewski
2015-04-20 11:59 ` Andrew Lunn
2015-04-20 13:07 ` Jacek Anaszewski [this message]
[not found] ` <5534FA13.9090502-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-04-20 17:49 ` Bryan Wu
2015-03-29 19:28 ` [PATCH RESEND v6 0/2] Driver for TI tlc591xx " Andrew Lunn
2015-03-30 22:10 ` Bryan Wu
2015-08-17 12:11 ` Tomi Valkeinen
2015-08-17 13:27 ` Andrew Lunn
2015-08-17 14:11 ` Tomi Valkeinen
2015-08-17 14:21 ` Andrew Lunn
2015-08-17 16:40 ` Tomi Valkeinen
2015-08-17 16:48 ` Andrew Lunn
2015-08-17 17:08 ` Bryan Wu
2015-08-17 20:47 ` Tomi Valkeinen
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=5534FA13.9090502@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=Matthew.Fatheree@belkin.com \
--cc=andrew@lunn.ch \
--cc=cooloney@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-leds@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.