public inbox for linux-leds@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Marek Behun <marek.behun@nic.cz>
Cc: Pavel Machek <pavel@ucw.cz>, linux-leds@vger.kernel.org
Subject: Re: [PATCH RFC leds-next] leds: initial support for Turris Omnia LEDs
Date: Thu, 2 Apr 2020 23:00:39 +0200	[thread overview]
Message-ID: <34c7c829-b478-1c13-ead8-12c6577febfe@gmail.com> (raw)
In-Reply-To: <20200402225730.2e6d9154@nic.cz>

On 4/2/20 10:57 PM, Marek Behun wrote:
> On Thu, 2 Apr 2020 22:19:50 +0200
> Jacek Anaszewski <jacek.anaszewski@gmail.com> wrote:
> 
>> On 4/2/20 4:29 PM, Marek Behun wrote:
>>> On Sun, 29 Mar 2020 14:53:57 +0200
>>> Jacek Anaszewski <jacek.anaszewski@gmail.com> wrote:
>>>   
>>>>> in the case you mentioned there is a one "global" brightness setting per
>>>>> each RGB LED. On Omnia, all 12 RGB LEDs have just one "global"
>>>>> brightness property. Ie. I press the button, and all 12 LEDs glow get
>>>>> dimmer. So there could be a 13th LED device with color LUMA, but what
>>>>> function should it be given in DTS?    
>>>>
>>>> Then, in this particular case, adding devicename prefix for the whole
>>>> family of LEDs would be justified. The question is whether it should be
>>>> hardware related name or rather something different.  
>>>
>>> Hi Jacek,
>>>
>>> so now we have
>>>   device:color:function
>>> what if we made it so that there was a 4th part of LED name, ie
>>>   group:device:color:function
>>> ?
>>>
>>> Would this be a problem?  
>>
>> Indeed, the device alone would not be a sufficient differentiator
>> since it is possible to have more than one LED controller of the
>> same type on the board.
>>
>> Nonetheless, I'd rather avoid the addition of a new generic section.
>> Probably we would have to make it specific to this device.
>>
> 
> Ok, in that case I will do it so that devicename is "omnia".
> devicename_mandatory should be set to true, yes?

If you want to have four sections then you must compose LED
name yourself and not use new *ext() API. But please hold on,
since I suppose Pavel will have something to add to that.

-- 
Best regards,
Jacek Anaszewski

  reply	other threads:[~2020-04-02 21:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 18:16 [PATCH RFC leds-next] leds: initial support for Turris Omnia LEDs Marek Behún
2020-03-21 15:33 ` Pavel Machek
2020-03-28 12:08   ` Jacek Anaszewski
2020-03-28 12:27     ` Marek Behun
2020-03-28 12:36       ` Marek Behun
2020-03-28 13:01         ` Jacek Anaszewski
2020-03-28 17:20           ` Marek Behun
2020-03-29 12:53             ` Jacek Anaszewski
2020-04-02 14:29               ` Marek Behun
2020-04-02 20:19                 ` Jacek Anaszewski
2020-04-02 20:57                   ` Marek Behun
2020-04-02 21:00                     ` Jacek Anaszewski [this message]
2020-04-06 21:10                       ` Pavel Machek
2020-04-06 21:08           ` Pavel Machek
2020-04-06 20:42       ` Pavel Machek
2020-03-21 15:34 ` Pavel Machek
2020-03-21 18:01   ` Jacek Anaszewski
2020-03-21 20:50     ` Marek Behun
2020-03-22 15:51       ` Jacek Anaszewski
2020-04-06  8:34         ` Pavel Machek
2020-04-06 13:53           ` Marek Behun
2020-03-21 18:55 ` Jacek Anaszewski
2020-03-21 20:44   ` Marek Behun
2020-03-22 15:28     ` Jacek Anaszewski
2020-03-21 21:53 ` Marek Behun
2020-03-21 22:16   ` Pavel Machek
2020-03-21 22:36     ` Marek Behun
2020-03-22 15:50       ` Dan Murphy
2020-04-06  8:40       ` Pavel Machek

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=34c7c829-b478-1c13-ead8-12c6577febfe@gmail.com \
    --to=jacek.anaszewski@gmail.com \
    --cc=linux-leds@vger.kernel.org \
    --cc=marek.behun@nic.cz \
    --cc=pavel@ucw.cz \
    /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