[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <13d593fb-053e-c6de-3237-ec3b6d1c82c5@gmail.com>
Date: Tue, 17 Mar 2020 21:43:57 +0100
From: Jacek Anaszewski <jacek.anaszewski@...il.com>
To: Denis Osterland-Heim <denis.osterland@...hl.com>,
"dmurphy@...com" <dmurphy@...com>, "pavel@....cz" <pavel@....cz>,
"mark.rutland@....com" <mark.rutland@....com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-leds@...r.kernel.org" <linux-leds@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v3 2/3] leds: pwm: add support for default-state device
property
Hi Denis,
On 3/16/20 9:24 PM, Denis Osterland-Heim wrote:
> Hi Jacek,
>
> Am Montag, den 16.03.2020, 19:36 +0100 schrieb Jacek Anaszewski:
>> Hi Denis,
>>
>> On 3/16/20 1:53 PM, Denis Osterland-Heim wrote:
> ...
>>>
>>> @@ -92,13 +96,27 @@ static int led_pwm_add(struct device *dev, struct led_pwm_priv *priv,
>>>
>>> pwm_init_state(led_data->pwm, &led_data->pwmstate);
>>>
>>> + if (led->default_state == LEDS_PWM_DEFSTATE_ON)
>>> + led_data->cdev.brightness = led->max_brightness;
>>> + else if (led->default_state == LEDS_PWM_DEFSTATE_KEEP) {
>>> + uint64_t brightness;
>>> +
>>> + pwm_get_state(led_data->pwm, &led_data->pwmstate);
>>
>> This seems to not be reading the device state, i.e. what you tried
>> to address by direct call to pwm->chip->ops->get_state() before.
>>
>> Am I missing something?
>>
>
> well, not you, but I missed cfc4c189bc70b1acc17e6f1abf1dc1c0ae890bd8.
> Since this commit pwm_get_state() is sufficient.
I assume you tested it?
With that, for the whole set:
Acked-by: Jacek Anaszewski <jacek.anaszewski@...il.com>
--
Best regards,
Jacek Anaszewski
Powered by blists - more mailing lists