Hello, this RFC series adds API for transparent offloading of LED triggers to hardware and implements this for the netdev trigger. It is then used by Marvell PHY driver, which gains support for probing LEDs connected to a PHY chip. When a netdev trigger is enabled on a Marvell PHY LED and configured in a compatible setting (the network device in the trigger settings must be the one attached to the PHY, and the link/tx/rx/interval settings must be supported by that particular LED), instead of blinking the LED in software, blinking is done by the PHY itself. Marek Marek Behún (7): leds: trigger: netdev: don't explicitly zero kzalloced data leds: trigger: netdev: simplify the driver by using bit field members leds: trigger: add API for HW offloading of triggers leds: trigger: netdev: support HW offloading net: phy: add simple incrementing phyindex member to phy_device struct net: phy: add support for LEDs connected to ethernet PHYs net: phy: marvell: support LEDs connected on Marvell PHYs Documentation/leds/leds-class.rst | 20 ++ drivers/leds/led-triggers.c | 1 + drivers/leds/trigger/ledtrig-netdev.c | 111 +++----- drivers/net/phy/marvell.c | 388 +++++++++++++++++++++++++- drivers/net/phy/phy_device.c | 143 ++++++++++ include/linux/leds.h | 27 ++ include/linux/ledtrig.h | 40 +++ include/linux/phy.h | 53 ++++ 8 files changed, 709 insertions(+), 74 deletions(-) create mode 100644 include/linux/ledtrig.h base-commit: cd29296fdfca919590e4004a7e4905544f4c4a32 -- 2.26.2
