leds: trigger: load trigger modules on-demand if used as default trigger
Status from this message: Applied, thanks!
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | leds: trigger: load trigger modules on-demand if used as default triggerdrivers/ | +9 | 0 replies | |
| 2/2 | leds: trigger: netdev: Add module alias ledtrig:netdevdrivers/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] leds: trigger: load trigger modules on-demand if used as default trigger
Even if a trigger is set as default trigger for a LED device, the respective trigger module (if built as module) isn't automatically loaded by the kernel if the LED device is registered. I think we can do better. Try to load the module asynchronously by alias ledtrig:<trigger name>. This requires that such an alias is added to relevant triggers. At first do this for the netdev trigger.
Tested with the recently added r8169 LED support using the netdev trigger.
Heiner Kallweit (2):
leds: trigger: load trigger modules on-demand if used as default
trigger
leds: trigger: netdev: Add module alias ledtrig:netdev
drivers/leds/led-triggers.c | 9 +++++++++ drivers/leds/trigger/ledtrig-netdev.c | 1 + 2 files changed, 10 insertions(+)
Signature · 1 line
2.43.0