Linux LED subsystem development
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: plaztininikolai@gmail.com
Cc: Pavel Machek <pavel@kernel.org>, Hans de Goede <hansg@kernel.org>,
	linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] leds: triggers: Add led_trigger_walk_leds()
Date: Thu, 15 Oct 2026 15:14:13 +0100	[thread overview]
Message-ID: <20261015141413.GB1907748@google.com> (raw)
In-Reply-To: <20260930-leds-input-events-brightness-v2-1-3948d3cddd83@gmail.com>

On Wed, 30 Sep 2026, Nikolay Plastinin via B4 Relay wrote:

> From: Nikolay Plastinin <plaztininikolai@gmail.com>
> 
> led_trigger_event() sets one brightness for all LEDs using a trigger.
> A trigger which restores a different brightness per LED, such as the
> input-events trigger turning keyboard backlights back on at the level
> the user picked, needs to walk the trigger's LEDs itself. That means
> using trig->led_cdevs and led_cdev->trig_list outside the LED core.
> 
> Add led_trigger_walk_leds(), which calls a function for each LED
> using the trigger under rcu_read_lock(), the same way led_trigger_event()
> does, so that such triggers do not have to walk the list themselves.
> 
> Assisted-by: LLM
> Signed-off-by: Nikolay Plastinin <plaztininikolai@gmail.com>
> ---
>  drivers/leds/led-triggers.c | 25 +++++++++++++++++++++++++
>  include/linux/leds.h        |  7 +++++++
>  2 files changed, 32 insertions(+)
> 
> diff --git a/drivers/leds/led-triggers.c b/drivers/leds/led-triggers.c
> index b1223218b..b5fc14e47 100644
> --- a/drivers/leds/led-triggers.c
> +++ b/drivers/leds/led-triggers.c
> @@ -422,6 +422,31 @@ void led_trigger_event(struct led_trigger *trig,
>  }
>  EXPORT_SYMBOL_GPL(led_trigger_event);
>  
> +/**
> + * led_trigger_walk_leds - call a function for each LED using a trigger
> + * @trig: the trigger, may be NULL
> + * @fn: the function to call for each LED
> + * @data: pointer passed to @fn
> + *
> + * Walks the LEDs currently using @trig under rcu_read_lock() and calls @fn
> + * for each of them. This is for triggers which set a different brightness
> + * per LED, where led_trigger_event() is not enough. @fn must not sleep.
> + */
> +void led_trigger_walk_leds(struct led_trigger *trig, led_trigger_walk_fn_t fn,
> +			   void *data)

I'm really not keen on pointers to functions being passed as function
arguments.

What about a simple iterator macro in 'include/linux/leds.h' which
results in no new exported functions, no callbacks, no 'typedef', and no
'void *' casting.

#define led_trigger_for_each_led(pos, trig) \
    list_for_each_entry_rcu(pos, &(trig)->led_cdevs, trig_list)

Then in Patch 2, 'input_events_set_leds(bool on)' doesn't need to be split into
two functions or pack 'bool on' into 'void *arg'.  It just does:

    guard(rcu)();
    led_trigger_for_each_led(led_cdev, &input_events_trigger) { }

When turning the LEDs off in Patch 2, it could even just call
led_trigger_event(&input_events_trigger, LED_OFF) directly or handle
both branches right inside that single loop.

> +{
> +	struct led_classdev *led_cdev;
> +
> +	if (!trig)
> +		return;
> +
> +	rcu_read_lock();
> +	list_for_each_entry_rcu(led_cdev, &trig->led_cdevs, trig_list)
> +		fn(led_cdev, data);
> +	rcu_read_unlock();
> +}
> +EXPORT_SYMBOL_GPL(led_trigger_walk_leds);
> +
>  void led_mc_trigger_event(struct led_trigger *trig,
>  			  unsigned int *intensity_value, unsigned int num_colors,
>  			  enum led_brightness brightness)
> diff --git a/include/linux/leds.h b/include/linux/leds.h
> index a515f075c..c971a6aa5 100644
> --- a/include/linux/leds.h
> +++ b/include/linux/leds.h
> @@ -476,6 +476,9 @@ static inline bool led_sysfs_is_disabled(struct led_classdev *led_cdev)
>  #define DEFINE_LED_TRIGGER(x)		static struct led_trigger *x;
>  #define DEFINE_LED_TRIGGER_GLOBAL(x)	struct led_trigger *x;
>  
> +/* Callback for led_trigger_walk_leds() */
> +typedef void (*led_trigger_walk_fn_t)(struct led_classdev *led_cdev, void *data);
> +
>  #ifdef CONFIG_LEDS_TRIGGERS
>  
>  #define TRIG_NAME_MAX 50
> @@ -521,6 +524,8 @@ void led_trigger_register_simple(const char *name,
>  				struct led_trigger **trigger);
>  void led_trigger_unregister_simple(struct led_trigger *trigger);
>  void led_trigger_event(struct led_trigger *trigger,  enum led_brightness event);
> +void led_trigger_walk_leds(struct led_trigger *trig, led_trigger_walk_fn_t fn,
> +			   void *data);
>  void led_mc_trigger_event(struct led_trigger *trig,
>  			  unsigned int *intensity_value, unsigned int num_colors,
>  			  enum led_brightness brightness);
> @@ -566,6 +571,8 @@ static inline void led_trigger_register_simple(const char *name,
>  static inline void led_trigger_unregister_simple(struct led_trigger *trigger) {}
>  static inline void led_trigger_event(struct led_trigger *trigger,
>  				enum led_brightness event) {}
> +static inline void led_trigger_walk_leds(struct led_trigger *trig,
> +					 led_trigger_walk_fn_t fn, void *data) {}
>  static inline void led_mc_trigger_event(struct led_trigger *trig,
>  				unsigned int *intensity_value, unsigned int num_colors,
>  				enum led_brightness brightness) {}
> 
> -- 
> 2.55.0
> 
> 

-- 
Lee Jones

  parent reply	other threads:[~2026-10-15 14:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  6:54 [PATCH v2 0/2] leds: trigger: input-events: Restore previous brightness on input Nikolay Plastinin via B4 Relay
2026-09-30  6:54 ` [PATCH v2 1/2] leds: triggers: Add led_trigger_walk_leds() Nikolay Plastinin via B4 Relay
2026-09-30  6:58   ` sashiko-bot
2026-10-15 14:14   ` Lee Jones [this message]
2026-09-30  6:54 ` [PATCH v2 2/2] leds: trigger: input-events: Restore previous brightness on input Nikolay Plastinin via B4 Relay
2026-09-30  7:02   ` sashiko-bot

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=20261015141413.GB1907748@google.com \
    --to=lee@kernel.org \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@kernel.org \
    --cc=plaztininikolai@gmail.com \
    /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