Message-ID: <385e4fc9-91cc-176c-730b-c27628027e2e@ti.com>
Date:   Thu, 31 Jan 2019 07:48:29 -0600
From:   Dan Murphy <dmurphy@...com>
To:     Jacek Anaszewski <jacek.anaszewski@...il.com>,
        <robh+dt@...nel.org>, <pavel@....cz>
CC:     <linux-kernel@...r.kernel.org>, <linux-leds@...r.kernel.org>
Subject: Re: [RFC PATCH] leds: multicolor: Add sysfs interface definition

Jacek

On 1/30/19 4:14 PM, Jacek Anaszewski wrote:
> Dan,
> 
> On 1/30/19 10:07 PM, Dan Murphy wrote:
>> Jacek
>>
>> On 1/30/19 2:20 PM, Jacek Anaszewski wrote:
>>> Dan,
>>>
>>> On 1/30/19 8:59 PM, Dan Murphy wrote:
>>>> Jacek
>>>>
>>>> On 1/30/19 1:37 PM, Jacek Anaszewski wrote:
>>>>> Hi Dan,
>>>>>
>>>>> Thank you for the RFC.
>>>>>
>>>>> One vital thing is missing - documentation of brightness file must
>>>>> be updated to define its semantics for LED multi color class.
>>>>>
>>>>> Either we need brightness-model file returning only "onoff" option
>>>>> available, or, for time being, fix the max_brightness for LED multi
>>>>> color class to 1 (which will map to max intensity level for each color).
>>>>>
>>>>
>>>> I can make max_brightness default to 1 if not set by the LED driver.
>>>>
>>>> But the LP50xx has brightness controls so setting max_brightness from the driver should over ride
>>>> the max of 1 in the upper level.
>>>
>>> Yes, so the max_brightness should be updated basing on current
>>> brightness-model. For LEDn_BRIGHTNESS of LP50xx we could have
>>> "hw" or maybe even better just "lp50xx-linear" and "lp50xx-logarithmic"
>>> - I just forgot about that capability of the device.
>>>
>>
>> OK maybe "hw" would make sense as there may be other devices that have dedicated brightness controls
>> over color controls.
> 
> Single "hw" doesn't address both linear and logarithmic.
> This is device specific, so I don't see anything wrong in
> "lp50xx-*", provided that it will be documented.
> 

OK.  This would need to be lp50xx specific.

>> Probably need to create a model for non-modeled cases like "rgb-independent".  Dumb name but I could not
>> think of anything better.
> 
> There is no point in having any rgb* brightness model since increasing
> rgb in an arbitrary way will not give the impression of increasing color
> intensity (lightness of the same hue). With DT defined hsl-<color>
> ranges there is no way to verify that levels arrangement makes sense
> with regard to preserving hue, this is a matter of trust. But we should
> state that it is highly recommended to obey this constraint so as to
> not mislead users.
> 

OK.  I will document this in v2 for discussion

>>>> For devices that do not support brightness as a separate control we can create a file called
>>>> max_brightness_<color> that defines the max that a specific color can be set to.  If max_brightness
>>>> is set to 1 then create max_brightness_<color>.  If max_brightness > 1 then do not create the files.
>>>
>>> Right. We will need dedicated max_brightness for each color.
>>> They should be placed also in the colors directory, next to the color
>>> files.
>>>
>>
>> OK will document this.
>>
>>>> I don't think we have fully vetted the brightness-model yet so I prefer to omit
>>>> it and possibly introduce that later.
>>>
>>> We need to start from something. It will give better overview of the
>>> whole idea.
>>>
>>
>> OK.  Don't get me wrong I don't oppose this idea I am just trying to figure out how the user space would
>> know what models and brightness levels are available.
> 
> $ cat brightness-model
> lp50xx-linear lp50xx-logarithmic onoff hsl-green hsl=blue
> 
> max_brightness will return available number of brightness levels
> for each brightness model.
> 

So max_brightness here would be dynamic?
Or could we read hsl-<color> and get the number of levels and not mess with the max_brightness definition?

Or should that be the current level?

> I'd not bother with presenting whole range of available color
> presets. Userspace can verify the brightness->color mapping
> by reading colors/<color> files after setting given brightness
> level.
> 

Userspace would have to have knowledge of the values set in order to verify the
color values.

> However, I'm not sure how useful it will be. This is a gist
> of this whole discussion - we cannot be certain about exact
> color effect produced with given settings.
> 
>> I mean we can read the brightness-models and present the available models but then how does the user know
>> what and how many levels are in each model?  And how do we govern putting them in the right order?
> 
> `cat max_brightness` will return number of levels for the model
> currently set. Regarding the order - we must rely on the DT array
> arrangement. In case of hardware originated brightness model we
> must trust hardware implementation.
> 

Another question on this is what is the proposed definition of the DT value?

is it supposed to be 0xrrggbb?  What about other colors like Amber?
This was demonstrated in one of the videos you sent.

Maybe it should be rgb-<color> and not hsl-<color> because these values are not hsl values
but instead RGB values.

>> The DT file can get messed up, per the previous example
>> rgb-green = <0x277c33 0x37b048 0x47e45d>;
>>
>> This is assumed to be from dimmest to brightest.  But that is just an assumption
>>
>> What if the entry looked like this?
>> rgb-green = <0x37b048 0x277c33 0x47e45d>;
> 
> We can do nothing. It is just the cost of leaving some decisions to DT.
> 

<snip>

> 
> I intended that brightness-model location would be the main LED class
> device directory.
> 
> And the whole concept is simple. We allow to set what we get from DT
> or from the hardware. Without verification exceeding beyond
> max_brightness values defined per iout.
> 

Yes this is simple will put some documentation around it for discussion

Dan

-- 
------------------
Dan Murphy

Powered by blists - more mailing lists