From: Rong Zhang <i@rong.moe>
To: Armin Wolf <W_Armin@gmx.de>, lee@kernel.org, pavel@kernel.org
Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 10/10] leds: multicolor: Adjust maximum subled intensity during initialization
Date: Mon, 19 Oct 2026 19:54:07 +0800 [thread overview]
Message-ID: <9a13ff3a5d799a50cc1353b94af9be6c70d87f47.camel@rong.moe> (raw)
In-Reply-To: <20261018135339.1109271-11-W_Armin@gmx.de>
Hi Armin,
Nice cleanup!
On Sun, 2026-10-18 at 15:46 +0200, Armin Wolf wrote:
> The maximum brightness of a LED device is fixed after having called
> led_classdev_init(), so performing the adjustment during runtime is
> no longer necessary.
>
> Signed-off-by: Armin Wolf <W_Armin@gmx.de>
> ---
> drivers/leds/led-class-multicolor.c | 40 ++++++++++++-----------------
> 1 file changed, 16 insertions(+), 24 deletions(-)
>
> diff --git a/drivers/leds/led-class-multicolor.c b/drivers/leds/led-class-multicolor.c
> index 9b8c37f7bdf4..875c615c33fc 100644
> --- a/drivers/leds/led-class-multicolor.c
> +++ b/drivers/leds/led-class-multicolor.c
> @@ -14,24 +14,6 @@
> #include <linux/uaccess.h>
> #include "leds.h"
>
> -static unsigned int led_mc_get_max_intensity(struct led_classdev_mc *mcled_cdev, size_t index)
> -{
> - unsigned int max_intensity;
> -
> - /*
> - * The maximum global brightness value might still be changed by
> - * led_classdev_register_ext() using devicetree properties. This
> - * prevents us from changing subled_info[X].max_intensity when
> - * registering a multicolor LED class device, so we have to do
> - * this during runtime.
> - */
> - max_intensity = mcled_cdev->subled_info[index].max_intensity;
> - if (max_intensity)
> - return max_intensity;
> -
> - return mcled_cdev->led_cdev.max_brightness;
> -}
> -
> int led_mc_calc_color_components(struct led_classdev_mc *mcled_cdev,
> enum led_brightness brightness)
> {
> @@ -53,12 +35,10 @@ static ssize_t multi_max_intensity_show(struct device *dev,
> {
> struct led_classdev *led_cdev = dev_get_drvdata(dev);
> struct led_classdev_mc *mcled_cdev = lcdev_to_mccdev(led_cdev);
> - unsigned int max_intensity;
> int len = 0;
>
> - for (int i = 0; i < mcled_cdev->num_colors; i++) {
> - max_intensity = led_mc_get_max_intensity(mcled_cdev, i);
> - len += sysfs_emit_at(buf, len, "%u", max_intensity);
> + for (unsigned int i = 0; i < mcled_cdev->num_colors; i++) {
> + len += sysfs_emit_at(buf, len, "%u", mcled_cdev->subled_info[i].max_intensity);
> if (i < mcled_cdev->num_colors - 1)
> len += sprintf(buf + len, " ");
> }
> @@ -98,8 +78,8 @@ static ssize_t multi_intensity_store(struct device *dev,
> goto err_out;
> }
>
> - for (int i = 0; i < mcled_cdev->num_colors; i++) {
> - max_intensity = led_mc_get_max_intensity(mcled_cdev, i);
> + for (unsigned int i = 0; i < mcled_cdev->num_colors; i++) {
> + max_intensity = mcled_cdev->subled_info[i].max_intensity;
> mcled_cdev->subled_info[i].intensity = min(intensity_value[i], max_intensity);
> }
>
> @@ -187,6 +167,18 @@ int led_classdev_multicolor_register_ext(struct device *parent,
> if (ret < 0)
> return ret;
>
> + /*
> + * The maximum global brightness value might still be changed by
s/still be/have been/ ?
Thanks,
Rong
> + * led_classdev_init() using devicetree properties. Because of this
> + * we can only adjust subled_info[X].max_intensity after said function
> + * was called.
> + */
> + for (unsigned int i = 0; i < mcled_cdev->num_colors; i++)
> + {
> + if (!mcled_cdev->subled_info[i].max_intensity)
> + mcled_cdev->subled_info[i].max_intensity = led_cdev->max_brightness;
> + }
> +
> led_cdev->dev->type = &led_multicolor_device_type;
> ret = led_classdev_add(led_cdev);
> if (ret < 0)
next prev parent reply other threads:[~2026-10-19 12:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 13:46 [PATCH 00/10] leds: class: Support custom sysfs groups on multicolor and flash LEDs Armin Wolf
2026-10-18 13:46 ` [PATCH 01/10] leds: class: Constify sysfs attributes Armin Wolf
2026-10-18 13:46 ` [PATCH 02/10] leds: multicolor: " Armin Wolf
2026-10-18 13:46 ` [PATCH 03/10] leds: flash: " Armin Wolf
2026-10-18 13:46 ` [PATCH 04/10] leds: class: Create "brightness_hw_changed" attribute atomically Armin Wolf
2026-10-19 11:51 ` Rong Zhang
2026-10-20 20:55 ` Armin Wolf
2026-10-18 13:46 ` [PATCH 05/10] leds: class: Fix race condition when creating the device Armin Wolf
2026-10-18 13:46 ` [PATCH 06/10] leds: class: Take the LED access lock when reading brightness_hw_changed Armin Wolf
2026-10-18 13:46 ` [PATCH 07/10] leds: class: Use correct type for brightness_hw_changed field Armin Wolf
2026-10-18 13:46 ` [PATCH 08/10] leds: class: Split led_classdev_register_ext() Armin Wolf
2026-10-18 13:46 ` [PATCH 09/10] leds: Support custom sysfs groups on multicolor and flash LEDs Armin Wolf
2026-10-19 11:53 ` Rong Zhang
2026-10-20 20:57 ` Armin Wolf
2026-10-18 13:46 ` [PATCH 10/10] leds: multicolor: Adjust maximum subled intensity during initialization Armin Wolf
2026-10-19 11:54 ` Rong Zhang [this message]
2026-10-20 20:59 ` Armin Wolf
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=9a13ff3a5d799a50cc1353b94af9be6c70d87f47.camel@rong.moe \
--to=i@rong.moe \
--cc=W_Armin@gmx.de \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
/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
all inboxes | Powered by JetHome®