[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6895344b-fe6f-f79e-806b-d77f20ea76e5@gmail.com>
Date: Mon, 3 Jul 2023 23:39:49 +0200
From: Jacek Anaszewski <jacek.anaszewski@...il.com>
To: Astrid Rost <astrid.rost@...s.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Rob Herring <robh@...nel.org>, Pavel Machek <pavel@....cz>,
Lee Jones <lee@...nel.org>
Cc: kernel@...s.com, linux-leds@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/2] led: led-class: Read max-brightness from
devicetree
Hi Astrid,
Thanks for the update.
On 7/3/23 15:03, Astrid Rost wrote:
> Normally, the maximum brightness is determined by the hardware, and this
> property is not required. This property is used to set a software limit.
> It could happen that an LED is made so bright that it gets damaged or
> causes damage due to restrictions in a specific system, such as mounting
> conditions.
> Note that this flag is mainly used for PWM-LEDs, where it is not possible
> to map brightness to current. Drivers for other controllers should use
> led-max-microamp.
>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
> Signed-off-by: Astrid Rost <astrid.rost@...s.com>
> ---
> drivers/leds/led-class.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/leds/led-class.c b/drivers/leds/led-class.c
> index 9255bc11f99d..ce652abf9336 100644
> --- a/drivers/leds/led-class.c
> +++ b/drivers/leds/led-class.c
> @@ -457,6 +457,10 @@ int led_classdev_register_ext(struct device *parent,
> if (fwnode_property_present(init_data->fwnode,
> "retain-state-shutdown"))
> led_cdev->flags |= LED_RETAIN_AT_SHUTDOWN;
> +
> + fwnode_property_read_u32(init_data->fwnode,
> + "max-brightness",
> + &led_cdev->max_brightness);
> }
> } else {
> proposed_name = led_cdev->name;
For the whole set:
Acked-by: Jacek Anaszewski <jacek.anaszewski@...il.com>
--
Best regards,
Jacek Anaszewski
Powered by blists - more mailing lists