On Tue, 05 Mar 2024, Lee Jones wrote: > On Mon, 04 Mar 2024 21:56:29 +0100, Heiner Kallweit wrote: > > If a simple trigger is assigned to a LED, then the LED may be off until > > the next led_trigger_event() call. This may be an issue for simple > > triggers with rare led_trigger_event() calls, e.g. power supply > > charging indicators (drivers/power/supply/power_supply_leds.c). > > Therefore persist the brightness value of the last led_trigger_event() > > call and use this value if the trigger is assigned to a LED. > > This change allows to use simple triggers in more cases. > > As a first use case simplify handling of the mute audio trigger. > > > > [...] > > Applied, thanks! > > [1/3] leds: trigger: Store brightness set by led_trigger_event() > commit: 575129855dee0e364af7df84a77ab5cca54b1442 > [2/3] ALSA: control-led: Integrate mute led trigger > commit: ba8adb1646ee498029ac12b20e792d9d0dd17920 > [3/3] leds: trigger: audio: Remove this trigger > commit: 2c61168294d0ea42a5542dbc864afb03a76bbc11 Submitted for build testing. Once succeeded, a PR will follow for other maintainers to pull from. -- Lee Jones [李琼斯]
