Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1490630 > unrolled thread

Re: [PATCH v3 1/2] leds: ncp5623: Add device tree binding documentation

Started byPavel Machek <pavel@ucw.cz>
First post2016-09-24 14:00 +0200
Last post2016-09-28 13:00 +0200
Articles 5 — 3 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v3 1/2] leds: ncp5623: Add device tree binding  documentation Pavel Machek <pavel@ucw.cz> - 2016-09-24 14:00 +0200
    Re: [PATCH v3 1/2] leds: ncp5623: Add device tree binding  documentation Jacek Anaszewski <jacek.anaszewski@gmail.com> - 2016-09-24 21:10 +0200
      Re: [PATCH v3 1/2] leds: ncp5623: Add device tree binding  documentation Florian Vaussard <florian.vaussard@gmail.com> - 2016-09-28 12:10 +0200
    Re: [PATCH v3 1/2] leds: ncp5623: Add device tree binding  documentation Florian Vaussard <florian.vaussard@gmail.com> - 2016-09-28 12:10 +0200
      Re: [PATCH v3 1/2] leds: ncp5623: Add device tree binding  documentation Pavel Machek <pavel@ucw.cz> - 2016-09-28 13:00 +0200

#1490630 — Re: [PATCH v3 1/2] leds: ncp5623: Add device tree binding documentation

FromPavel Machek <pavel@ucw.cz>
Date2016-09-24 14:00 +0200
SubjectRe: [PATCH v3 1/2] leds: ncp5623: Add device tree binding documentation
Message-ID<skTMB-wL-5@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Hi!

> +Example
> +=======
> +
> +led1: ncp5623@38 {
> +	#address-cells = <1>;
> +	#size-cells = <0>;
> +	compatible = "onnn,ncp5623";
> +	reg = <0x38>;
> +	onnn,led-iref-microamp = <10>;
> +
> +	led1r@0 {
> +		label = "ncp:power:red";
> +		linux,default-trigger = "default-on";
...
> +	led1b@1 {
> +		label = "ncp:power:blue";
> +		reg = <1>;

Actually... the three LEDs are packaged such as this is one colorful
light to the user, right? Some day we'll need to group them, so that
kernel can automatically tell this is one led, and probably add extra
attributes, such as values that produce white light.

Best regards,
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[toc] | [next] | [standalone]


#1490725

FromJacek Anaszewski <jacek.anaszewski@gmail.com>
Date2016-09-24 21:10 +0200
Message-ID<sl0uK-4TP-29@gated-at.bofh.it>
In reply to#1490630
On 09/24/2016 01:58 PM, Pavel Machek wrote:
> Hi!
>
>> +Example
>> +=======
>> +
>> +led1: ncp5623@38 {
>> +	#address-cells = <1>;
>> +	#size-cells = <0>;
>> +	compatible = "onnn,ncp5623";
>> +	reg = <0x38>;
>> +	onnn,led-iref-microamp = <10>;
>> +
>> +	led1r@0 {
>> +		label = "ncp:power:red";
>> +		linux,default-trigger = "default-on";
> ...
>> +	led1b@1 {
>> +		label = "ncp:power:blue";
>> +		reg = <1>;
>
> Actually... the three LEDs are packaged such as this is one colorful
> light to the user, right? Some day we'll need to group them, so that
> kernel can automatically tell this is one led, and probably add extra
> attributes, such as values that produce white light.

We could try out the trigger approach we discussed few months ago.
Unfortunately I currently don't have enough time to propose the
implementation. Probably this work could be done on the occasion of
addition of RGB LED class driver like this, if the author had free
bandwidth for that.

-- 
Best regards,
Jacek Anaszewski

[toc] | [prev] | [next] | [standalone]


#1492507

FromFlorian Vaussard <florian.vaussard@gmail.com>
Date2016-09-28 12:10 +0200
Message-ID<smjYm-5lD-39@gated-at.bofh.it>
In reply to#1490725
Hello Jacek,

Le 24. 09. 16 à 21:06, Jacek Anaszewski a écrit :
> On 09/24/2016 01:58 PM, Pavel Machek wrote:
>> Hi!
>>
>>> +Example
>>> +=======
>>> +
>>> +led1: ncp5623@38 {
>>> +    #address-cells = <1>;
>>> +    #size-cells = <0>;
>>> +    compatible = "onnn,ncp5623";
>>> +    reg = <0x38>;
>>> +    onnn,led-iref-microamp = <10>;
>>> +
>>> +    led1r@0 {
>>> +        label = "ncp:power:red";
>>> +        linux,default-trigger = "default-on";
>> ...
>>> +    led1b@1 {
>>> +        label = "ncp:power:blue";
>>> +        reg = <1>;
>>
>> Actually... the three LEDs are packaged such as this is one colorful
>> light to the user, right? Some day we'll need to group them, so that
>> kernel can automatically tell this is one led, and probably add extra
>> attributes, such as values that produce white light.
> 
> We could try out the trigger approach we discussed few months ago.
> Unfortunately I currently don't have enough time to propose the
> implementation. Probably this work could be done on the occasion of
> addition of RGB LED class driver like this, if the author had free
> bandwidth for that.
> 

Unfortunately my bandwidth is pretty well used at the moment :)

Best regards,
Florian

[toc] | [prev] | [next] | [standalone]


#1492503

FromFlorian Vaussard <florian.vaussard@gmail.com>
Date2016-09-28 12:10 +0200
Message-ID<smjYl-5lD-1@gated-at.bofh.it>
In reply to#1490630
Hi Pavel,

Le 24. 09. 16 à 13:58, Pavel Machek a écrit :
> Hi!
> 
>> +Example
>> +=======
>> +
>> +led1: ncp5623@38 {
>> +	#address-cells = <1>;
>> +	#size-cells = <0>;
>> +	compatible = "onnn,ncp5623";
>> +	reg = <0x38>;
>> +	onnn,led-iref-microamp = <10>;
>> +
>> +	led1r@0 {
>> +		label = "ncp:power:red";
>> +		linux,default-trigger = "default-on";
> ...
>> +	led1b@1 {
>> +		label = "ncp:power:blue";
>> +		reg = <1>;
> 
> Actually... the three LEDs are packaged such as this is one colorful
> light to the user, right? Some day we'll need to group them, so that
> kernel can automatically tell this is one led, and probably add extra
> attributes, such as values that produce white light.
> 

Actually, it's up to the hardware designer to choose. On my board for instance,
this chip is driving an RGB LED, but it can really drive three independent LEDs
if you want.

I agree that the RGB case is quite common nowadays and currently not very well
managed by the LED subsystem. But I do not think that this is specific to this
driver.

Best regards,
Florian

[toc] | [prev] | [next] | [standalone]


#1492529

FromPavel Machek <pavel@ucw.cz>
Date2016-09-28 13:00 +0200
Message-ID<smkKJ-5BT-3@gated-at.bofh.it>
In reply to#1492503

[Multipart message — attachments visible in raw view] — view raw

On Wed 2016-09-28 12:02:41, Florian Vaussard wrote:
> Hi Pavel,
> 
> Le 24. 09. 16 à 13:58, Pavel Machek a écrit :
> > Hi!
> > 
> >> +Example
> >> +=======
> >> +
> >> +led1: ncp5623@38 {
> >> +	#address-cells = <1>;
> >> +	#size-cells = <0>;
> >> +	compatible = "onnn,ncp5623";
> >> +	reg = <0x38>;
> >> +	onnn,led-iref-microamp = <10>;
> >> +
> >> +	led1r@0 {
> >> +		label = "ncp:power:red";
> >> +		linux,default-trigger = "default-on";
> > ...
> >> +	led1b@1 {
> >> +		label = "ncp:power:blue";
> >> +		reg = <1>;
> > 
> > Actually... the three LEDs are packaged such as this is one colorful
> > light to the user, right? Some day we'll need to group them, so that
> > kernel can automatically tell this is one led, and probably add extra
> > attributes, such as values that produce white light.
> > 
> 
> Actually, it's up to the hardware designer to choose. On my board for instance,
> this chip is driving an RGB LED, but it can really drive three independent LEDs
> if you want.

Yup. And driving RGB LED is really a bit different from driving three
independent LEDs: you'd for example like to be able to set the RGB LED
to white, and you need to know relative intensities for that.

So it would be good to have hardware description that captures
difference between RGB LED and three LEDs.

(And then, we'll want pattern engine to drive that. One day :-) ).

> I agree that the RGB case is quite common nowadays and currently not very well
> managed by the LED subsystem. But I do not think that this is specific to this
> driver.

No, it is not.

Best regards,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web