summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndrew Lunn <andrew@lunn.ch>2023-05-29 18:32:32 +0200
committerDavid S. Miller <davem@davemloft.net>2023-05-31 10:42:08 +0200
commit052c38eb17e866c5b4cd43924e7a5e20167b55c0 (patch)
treed402e50b609d13fd07d389ef56b5bbdb8ee03851
parentleds: add APIs for LEDs hw control (diff)
downloadlinux-052c38eb17e866c5b4cd43924e7a5e20167b55c0.tar.xz
linux-052c38eb17e866c5b4cd43924e7a5e20167b55c0.zip
leds: add API to get attached device for LED hw control
Some specific LED triggers blink the LED based on events from a device or subsystem. For example, an LED could be blinked to indicate a network device is receiving packets, or a disk is reading blocks. To correctly enable and request the hw control of the LED, the trigger has to check if the network interface or block device configured via a /sys/class/led file match the one the LED driver provide for hw control for. Provide an API call to get the device which the LED blinks for. Signed-off-by: Andrew Lunn <andrew@lunn.ch> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net>
-rw-r--r--include/linux/leds.h6
1 files changed, 6 insertions, 0 deletions
diff --git a/include/linux/leds.h b/include/linux/leds.h
index 4caf559b1922..3268b4e789d6 100644
--- a/include/linux/leds.h
+++ b/include/linux/leds.h
@@ -220,6 +220,12 @@ struct led_classdev {
*/
int (*hw_control_get)(struct led_classdev *led_cdev,
unsigned long *flags);
+ /*
+ * Get the device this LED blinks in response to.
+ * e.g. for a PHY LED, it is the network device. If the LED is
+ * not yet associated to a device, return NULL.
+ */
+ struct device *(*hw_control_get_device)(struct led_classdev *led_cdev);
#endif
#ifdef CONFIG_LEDS_BRIGHTNESS_HW_CHANGED