leds: trigger: netdev: add additional modes
Subsystems (3)
v5 cover leds: trigger: netdev: add additional modes
This is a continue of [1]. It was decided to take a more gradual approach to implement LEDs support for switch and phy starting with basic support and then implementing the hw control part when we have all the prereq done.
This should be the final part for the netdev trigger.
I added net-next tag and added netdev mailing list since I was informed that this should be merged with netdev branch.
We collect some info around and we found a good set of modes that are common in almost all the PHY and Switch.
These modes are:
- Modes for dedicated link speed(10, 100, 1000 mbps). Additional mode can be added later following this example.
- Modes for half and full duplex.
The original idea was to add hw control only modes.
While the concept makes sense in practice it would results in lots of additional code and extra check to make sure we are setting correct modes.
With the suggestion from Andrew it was pointed out that using the ethtool APIs we can actually get the current link speed and duplex and this effectively removed the problem of having hw control only modes since we can fallback to software.
Since these modes are supported by software, we can skip providing an user for this in the LED driver to support hw control for these new modes (that will come right after this is merged) and prevent this to be another multi subsystem series.
For link speed and duplex we use ethtool APIs.
To call ethtool APIs, rtnl lock is needed but this can be skipped on handling netdev events as the lock is already held.
[1] https://lore.kernel.org/lkml/[email protected]/
Changes v5:
- Fix conflict error on rebase
- Add Review-by tag by Andrew
Changes v4:
- Add net-next tag
- Add additional patch to expose hw_control via sysfs
- CC netdev mailing list
Changes v3:
- Add Andrew review tag
- Use SPEED_UNKNOWN to init link_speed
- Fix using HALF_DUPLEX as duplex init and use DUPLEX_UNKNOWN instead Changes v2:
- Drop ACTIVITY patch as it can be handled internally in the LED driver
- Reduce duplicate code and move the link state to a dedicated helper
Christian Marangi (3):
leds: trigger: netdev: add additional specific link speed mode
leds: trigger: netdev: add additional specific link duplex mode
leds: trigger: netdev: expose hw_control status via sysfs
drivers/leds/trigger/ledtrig-netdev.c | 114 +++++++++++++++++++++++--- include/linux/leds.h | 5 ++ 2 files changed, 109 insertions(+), 10 deletions(-)
Signature · 1 line
2.40.1
PATCH v5 1/3 leds: trigger: netdev: add additional specific link speed mode
Add additional modes for specific link speed. Use ethtool APIs to get the current link speed and enable the LED accordingly. Under netdev event handler the rtnl lock is already held and is not needed to be set to access ethtool APIs.
This is especially useful for PHY and Switch that supports LEDs hw control for specific link speed. (example scenario a PHY that have 2 LED connected one green and one orange where the green is turned on with 1000mbps speed and orange is turned on with 10mpbs speed)
On mode set from sysfs we check if we have enabled split link speed mode and reject enabling generic link mode to prevent wrong and redundant configuration.
Rework logic on the set baseline state to support these new modes to select if we need to turn on or off the LED.
Add additional modes:
- link_10: Turn on LED when link speed is 10mbps
- link_100: Turn on LED when link speed is 100mbps
- link_1000: Turn on LED when link speed is 1000mbps
--- drivers/leds/trigger/ledtrig-netdev.c | 80 +++++++++++++++++++++++---- include/linux/leds.h | 3 + 2 files changed, 73 insertions(+), 10 deletions(-)
drivers/leds/trigger/ledtrig-netdev.c +70 -10
@@ -13,6 +13,7 @@#include <linux/atomic.h> #include <linux/ctype.h> #include <linux/device.h> +#include <linux/ethtool.h> #include <linux/init.h> #include <linux/jiffies.h> #include <linux/kernel.h>
@@ -21,6 +22,7 @@#include <linux/module.h> #include <linux/netdevice.h> #include <linux/mutex.h> +#include <linux/rtnetlink.h> #include <linux/timer.h> #include "../leds.h"
@@ -52,6 +54,8 @@ struct led_netdev_data {unsigned int last_activity;unsigned long mode; +int link_speed; +bool carrier_link_up;bool hw_control; };
@@ -77,7 +81,24 @@ static void set_baseline_state(struct led_netdev_data *trigger_data)if (!trigger_data->carrier_link_up) {led_set_brightness (led_cdev,LED_OFF ); }else { +bool blink_on = false; +if (test_bit (TRIGGER_NETDEV_LINK , &trigger_data->mode)) + blink_on = true; + +if (test_bit (TRIGGER_NETDEV_LINK_10 , &trigger_data->mode) && + trigger_data->link_speed ==SPEED_10 ) + blink_on = true; + +if (test_bit (TRIGGER_NETDEV_LINK_100 , &trigger_data->mode) && + trigger_data->link_speed ==SPEED_100 ) + blink_on = true; + +if (test_bit (TRIGGER_NETDEV_LINK_1000 , &trigger_data->mode) && + trigger_data->link_speed ==SPEED_1000 ) + blink_on = true; + +if (blink_on)led_set_brightness (led_cdev, led_cdev->blink_brightness);else
@@ -161,6 +182,18 @@ static bool can_hw_control(struct led_netdev_data *trigger_data)return true; } +static void get_device_state (struct led_netdev_data *trigger_data) +{ +struct ethtool_link_ksettings cmd; + + trigger_data->carrier_link_up =netif_carrier_ok (trigger_data->net_dev); +if (!trigger_data->carrier_link_up) +return ; + +if (!__ethtool_get_link_ksettings (trigger_data->net_dev, &cmd)) + trigger_data->link_speed = cmd.base.speed; +} +static ssize_t device_name_show (struct device *dev,struct device_attribute *attr,char *buf) {
@@ -196,8 +229,12 @@ static int set_device_name(struct led_netdev_data *trigger_data,dev_get_by_name (&init_net, trigger_data->device_name); trigger_data->carrier_link_up = false; -if (trigger_data->net_dev !=NULL ) - trigger_data->carrier_link_up =netif_carrier_ok (trigger_data->net_dev); + trigger_data->link_speed =SPEED_UNKNOWN ; +if (trigger_data->net_dev !=NULL ) { +rtnl_lock (); +get_device_state (trigger_data); +rtnl_unlock (); + } trigger_data->last_activity =0 ;
@@ -234,6 +271,9 @@ static ssize_t netdev_led_attr_show(struct device *dev, char *buf,switch (attr) {case TRIGGER_NETDEV_LINK : +case TRIGGER_NETDEV_LINK_10 : +case TRIGGER_NETDEV_LINK_100 : +case TRIGGER_NETDEV_LINK_1000 :case TRIGGER_NETDEV_TX :case TRIGGER_NETDEV_RX : bit = attr;
@@ -249,7 +289,7 @@ static ssize_t netdev_led_attr_store(struct device *dev, const char *buf, size_t size, enum led_trigger_netdev_modes attr) {struct led_netdev_data *trigger_data =led_trigger_get_drvdata (dev); -unsigned long state; +unsigned long state, mode = trigger_data->mode;int ret;int bit;
@@ -259,6 +299,9 @@ static ssize_t netdev_led_attr_store(struct device *dev, const char *buf,switch (attr) {case TRIGGER_NETDEV_LINK : +case TRIGGER_NETDEV_LINK_10 : +case TRIGGER_NETDEV_LINK_100 : +case TRIGGER_NETDEV_LINK_1000 :case TRIGGER_NETDEV_TX :case TRIGGER_NETDEV_RX : bit = attr;
@@ -267,13 +310,20 @@ static ssize_t netdev_led_attr_store(struct device *dev, const char *buf,return -EINVAL ; } -cancel_delayed_work_sync (&trigger_data->work); -if (state) -set_bit (bit, &trigger_data->mode); +set_bit (bit, &mode);else -clear_bit (bit, &trigger_data->mode); +clear_bit (bit, &mode); + +if (test_bit (TRIGGER_NETDEV_LINK , &mode) && + (test_bit (TRIGGER_NETDEV_LINK_10 , &mode) || +test_bit (TRIGGER_NETDEV_LINK_100 , &mode) || +test_bit (TRIGGER_NETDEV_LINK_1000 , &mode))) +return -EINVAL ; + +cancel_delayed_work_sync (&trigger_data->work); + trigger_data->mode = mode; trigger_data->hw_control =can_hw_control (trigger_data);set_baseline_state (trigger_data);
@@ -295,6 +345,9 @@ static ssize_t netdev_led_attr_store(struct device *dev, const char *buf,static DEVICE_ATTR_RW (trigger_name)DEFINE_NETDEV_TRIGGER (link, TRIGGER_NETDEV_LINK); +DEFINE_NETDEV_TRIGGER (link_10,TRIGGER_NETDEV_LINK_10 ); +DEFINE_NETDEV_TRIGGER (link_100,TRIGGER_NETDEV_LINK_100 ); +DEFINE_NETDEV_TRIGGER (link_1000,TRIGGER_NETDEV_LINK_1000 );DEFINE_NETDEV_TRIGGER (tx,TRIGGER_NETDEV_TX );DEFINE_NETDEV_TRIGGER (rx,TRIGGER_NETDEV_RX );
@@ -338,6 +391,9 @@ static DEVICE_ATTR_RW(interval);static struct attribute *netdev_trig_attrs[] = { &dev_attr_device_name.attr, &dev_attr_link.attr, + &dev_attr_link_10.attr, + &dev_attr_link_100.attr, + &dev_attr_link_1000.attr, &dev_attr_rx.attr, &dev_attr_tx.attr, &dev_attr_interval.attr,
@@ -368,9 +424,10 @@ static int netdev_trig_notify(struct notifier_block *nb,mutex_lock (&trigger_data->lock); trigger_data->carrier_link_up = false; + trigger_data->link_speed =SPEED_UNKNOWN ;switch (evt) {case NETDEV_CHANGENAME : - trigger_data->carrier_link_up =netif_carrier_ok (dev); +get_device_state (trigger_data); fallthrough;case NETDEV_REGISTER :if (trigger_data->net_dev)
@@ -384,7 +441,7 @@ static int netdev_trig_notify(struct notifier_block *nb,break ;case NETDEV_UP :case NETDEV_CHANGE : - trigger_data->carrier_link_up =netif_carrier_ok (dev); +get_device_state (trigger_data);break ; }
@@ -427,7 +484,10 @@ static void netdev_trig_work(struct work_struct *work)if (trigger_data->last_activity != new_activity) {led_stop_software_blink (trigger_data->led_cdev); - invert =test_bit (TRIGGER_NETDEV_LINK , &trigger_data->mode); + invert =test_bit (TRIGGER_NETDEV_LINK , &trigger_data->mode) || +test_bit (TRIGGER_NETDEV_LINK_10 , &trigger_data->mode) || +test_bit (TRIGGER_NETDEV_LINK_100 , &trigger_data->mode) || +test_bit (TRIGGER_NETDEV_LINK_1000 , &trigger_data->mode); interval =jiffies_to_msecs (atomic_read (&trigger_data->interval));/* base state is ON (link present) */
include/linux/leds.h +3 -0
@@ -555,6 +555,9 @@ static inline void *led_get_trigger_data(struct led_classdev *led_cdev)/* Trigger specific enum */ enum led_trigger_netdev_modes {TRIGGER_NETDEV_LINK =0 , +TRIGGER_NETDEV_LINK_10 , +TRIGGER_NETDEV_LINK_100 , +TRIGGER_NETDEV_LINK_1000 ,TRIGGER_NETDEV_TX ,TRIGGER_NETDEV_RX ,
Signature · 1 line
2.40.1
Re: [net-next PATCH v5 1/3] leds: trigger: netdev: add additional specific link speed mode
Quoted 22 lines · Christian Marangi
Add additional modes for specific link speed. Use ethtool APIs to get the current link speed and enable the LED accordingly. Under netdev event handler the rtnl lock is already held and is not needed to be set to access ethtool APIs.
This is especially useful for PHY and Switch that supports LEDs hw control for specific link speed. (example scenario a PHY that have 2 LED connected one green and one orange where the green is turned on with 1000mbps speed and orange is turned on with 10mpbs speed)
On mode set from sysfs we check if we have enabled split link speed mode and reject enabling generic link mode to prevent wrong and redundant configuration.
Rework logic on the set baseline state to support these new modes to select if we need to turn on or off the LED.
Add additional modes:
-link_10: Turn on LED when link speed is 10mbps
-link_100: Turn on LED when link speed is 100mbps
-link_1000: Turn on LED when link speed is 1000mbps
Quoted 6 lines
Signed-off-by Christian Marangi <[email protected]>Reviewed-by Andrew Lunn <[email protected]>--- drivers/leds/trigger/ledtrig-netdev.c | 80 +++++++++++++++++++++++---- include/linux/leds.h | 3 + 2 files changed, 73 insertions(+), 10 deletions(-)
Signature · 1 line
Lee Jones [李琼斯]
PATCH v5 2/3 leds: trigger: netdev: add additional specific link duplex mode
In reply to Christian MarangiAdd additional modes for specific link duplex. Use ethtool APIs to get the current link duplex and enable the LED accordingly. Under netdev event handler the rtnl lock is already held and is not needed to be set to access ethtool APIs.
This is especially useful for PHY and Switch that supports LEDs hw control for specific link duplex.
Add additional modes:
- half_duplex: Turn on LED when link is half duplex
- full_duplex: Turn on LED when link is full duplex
--- drivers/leds/trigger/ledtrig-netdev.c | 27 +++++++++++++++++++++++++-- include/linux/leds.h | 2 ++ 2 files changed, 27 insertions(+), 2 deletions(-)
drivers/leds/trigger/ledtrig-netdev.c +25 -2
@@ -55,6 +55,7 @@ struct led_netdev_data {unsigned long mode;int link_speed; +u8 duplex;bool carrier_link_up;bool hw_control;
@@ -98,6 +99,14 @@ static void set_baseline_state(struct led_netdev_data *trigger_data) trigger_data->link_speed == SPEED_1000) blink_on = true; +if (test_bit (TRIGGER_NETDEV_HALF_DUPLEX , &trigger_data->mode) && + trigger_data->duplex ==DUPLEX_HALF ) + blink_on = true; + +if (test_bit (TRIGGER_NETDEV_FULL_DUPLEX , &trigger_data->mode) && + trigger_data->duplex ==DUPLEX_FULL ) + blink_on = true; +if (blink_on)led_set_brightness (led_cdev, led_cdev->blink_brightness);
@@ -190,8 +199,10 @@ static void get_device_state(struct led_netdev_data *trigger_data)if (!trigger_data->carrier_link_up)return ; -if (!__ethtool_get_link_ksettings (trigger_data->net_dev, &cmd)) +if (!__ethtool_get_link_ksettings (trigger_data->net_dev, &cmd)) { trigger_data->link_speed = cmd.base.speed; + trigger_data->duplex = cmd.base.duplex; + } } static ssize_t device_name_show(struct device *dev,
@@ -230,6 +241,7 @@ static int set_device_name(struct led_netdev_data *trigger_data, trigger_data->carrier_link_up = false; trigger_data->link_speed =SPEED_UNKNOWN ; + trigger_data->duplex =DUPLEX_UNKNOWN ;if (trigger_data->net_dev !=NULL ) {rtnl_lock ();get_device_state (trigger_data);
@@ -274,6 +286,8 @@ static ssize_t netdev_led_attr_show(struct device *dev, char *buf,case TRIGGER_NETDEV_LINK_10 :case TRIGGER_NETDEV_LINK_100 :case TRIGGER_NETDEV_LINK_1000 : +case TRIGGER_NETDEV_HALF_DUPLEX : +case TRIGGER_NETDEV_FULL_DUPLEX :case TRIGGER_NETDEV_TX :case TRIGGER_NETDEV_RX : bit = attr;
@@ -302,6 +316,8 @@ static ssize_t netdev_led_attr_store(struct device *dev, const char *buf,case TRIGGER_NETDEV_LINK_10 :case TRIGGER_NETDEV_LINK_100 :case TRIGGER_NETDEV_LINK_1000 : +case TRIGGER_NETDEV_HALF_DUPLEX : +case TRIGGER_NETDEV_FULL_DUPLEX :case TRIGGER_NETDEV_TX :case TRIGGER_NETDEV_RX : bit = attr;
@@ -348,6 +364,8 @@ DEFINE_NETDEV_TRIGGER(link, TRIGGER_NETDEV_LINK);DEFINE_NETDEV_TRIGGER (link_10,TRIGGER_NETDEV_LINK_10 );DEFINE_NETDEV_TRIGGER (link_100,TRIGGER_NETDEV_LINK_100 );DEFINE_NETDEV_TRIGGER (link_1000,TRIGGER_NETDEV_LINK_1000 ); +DEFINE_NETDEV_TRIGGER (half_duplex,TRIGGER_NETDEV_HALF_DUPLEX ); +DEFINE_NETDEV_TRIGGER (full_duplex,TRIGGER_NETDEV_FULL_DUPLEX );DEFINE_NETDEV_TRIGGER (tx,TRIGGER_NETDEV_TX );DEFINE_NETDEV_TRIGGER (rx,TRIGGER_NETDEV_RX );
@@ -394,6 +412,8 @@ static struct attribute *netdev_trig_attrs[] = { &dev_attr_link_10.attr, &dev_attr_link_100.attr, &dev_attr_link_1000.attr, + &dev_attr_full_duplex.attr, + &dev_attr_half_duplex.attr, &dev_attr_rx.attr, &dev_attr_tx.attr, &dev_attr_interval.attr,
@@ -425,6 +445,7 @@ static int netdev_trig_notify(struct notifier_block *nb, trigger_data->carrier_link_up = false; trigger_data->link_speed =SPEED_UNKNOWN ; + trigger_data->duplex =DUPLEX_UNKNOWN ;switch (evt) {case NETDEV_CHANGENAME :get_device_state (trigger_data);
@@ -487,7 +508,9 @@ static void netdev_trig_work(struct work_struct *work) invert =test_bit (TRIGGER_NETDEV_LINK , &trigger_data->mode) ||test_bit (TRIGGER_NETDEV_LINK_10 , &trigger_data->mode) ||test_bit (TRIGGER_NETDEV_LINK_100 , &trigger_data->mode) || -test_bit (TRIGGER_NETDEV_LINK_1000 , &trigger_data->mode); +test_bit (TRIGGER_NETDEV_LINK_1000 , &trigger_data->mode) || +test_bit (TRIGGER_NETDEV_HALF_DUPLEX , &trigger_data->mode) || +test_bit (TRIGGER_NETDEV_FULL_DUPLEX , &trigger_data->mode); interval =jiffies_to_msecs (atomic_read (&trigger_data->interval));/* base state is ON (link present) */
include/linux/leds.h +2 -0
@@ -558,6 +558,8 @@ enum led_trigger_netdev_modes {TRIGGER_NETDEV_LINK_10 ,TRIGGER_NETDEV_LINK_100 ,TRIGGER_NETDEV_LINK_1000 , +TRIGGER_NETDEV_HALF_DUPLEX , +TRIGGER_NETDEV_FULL_DUPLEX ,TRIGGER_NETDEV_TX , TRIGGER_NETDEV_RX,
Signature · 1 line
2.40.1
Re: [net-next PATCH v5 2/3] leds: trigger: netdev: add additional specific link duplex mode
Quoted 12 lines · Christian Marangi
Add additional modes for specific link duplex. Use ethtool APIs to get the current link duplex and enable the LED accordingly. Under netdev event handler the rtnl lock is already held and is not needed to be set to access ethtool APIs.
This is especially useful for PHY and Switch that supports LEDs hw control for specific link duplex.
Add additional modes:
-half_duplex: Turn on LED when link is half duplex
-full_duplex: Turn on LED when link is full duplex
Quoted 6 lines
Signed-off-by Christian Marangi <[email protected]>Reviewed-by Andrew Lunn <[email protected]>--- drivers/leds/trigger/ledtrig-netdev.c | 27 +++++++++++++++++++++++++-- include/linux/leds.h | 2 ++ 2 files changed, 27 insertions(+), 2 deletions(-)
Signature · 1 line
Lee Jones [李琼斯]
PATCH v5 3/3 leds: trigger: netdev: expose hw_control status via sysfs
In reply to Christian MarangiExpose hw_control status via sysfs for the netdev trigger to give userspace better understanding of the current state of the trigger and the LED.
--- drivers/leds/trigger/ledtrig-netdev.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
drivers/leds/trigger/ledtrig-netdev.c +11 -0
@@ -406,6 +406,16 @@ static ssize_t interval_store(struct device *dev,static DEVICE_ATTR_RW (interval); +static ssize_t hw_control_show (struct device *dev, +struct device_attribute *attr,char *buf) +{ +struct led_netdev_data *trigger_data =led_trigger_get_drvdata (dev); + +return sprintf (buf,"%d\n" , trigger_data->hw_control); +} + +static DEVICE_ATTR_RO (hw_control); +static struct attribute *netdev_trig_attrs[] = { &dev_attr_device_name.attr, &dev_attr_link.attr,
@@ -417,6 +427,7 @@ static struct attribute *netdev_trig_attrs[] = { &dev_attr_rx.attr, &dev_attr_tx.attr, &dev_attr_interval.attr, + &dev_attr_hw_control.attr, NULL };ATTRIBUTE_GROUPS (netdev_trig);
Signature · 1 line
2.40.1
Re: [net-next PATCH v5 3/3] leds: trigger: netdev: expose hw_control status via sysfs
Quoted 17 lines · Christian Marangi
Expose
hw_controlstatus via sysfs for the netdev trigger to give userspace better understanding of the current state of the trigger and the LED.Signed-off-by Christian Marangi <[email protected]>Reviewed-by Andrew Lunn <[email protected]>--- drivers/leds/trigger/ledtrig-netdev.c | 11 +++++++++++ 1 file changed, 11 insertions(+)drivers/leds/trigger/ledtrig-netdev.c +0
-0@@ -406,6 +406,16 @@ static ssize_t interval_store(struct device *dev,
drivers/leds/trigger/ledtrig-netdev.c static ssize_t interval_store(struct device *dev, · line 416
Quoted 10 lines
drivers/leds/trigger/ledtrig-netdev.c +6
-0static DEVICE_ATTR_RW (interval); +static ssize_t hw_control_show (struct device *dev, +struct device_attribute *attr,char *buf) +{ +struct led_netdev_data *trigger_data =led_trigger_get_drvdata (dev); + +return sprintf (buf,"%d\n" , trigger_data->hw_control);
[Kalesh]: How about using sysfs_emit?
Quoted 20 lines
drivers/leds/trigger/ledtrig-netdev.c +4
-0+} + +static DEVICE_ATTR_RO (hw_control); +static struct attribute *netdev_trig_attrs[] = {&dev_attr_device_name.attr,
&dev_attr_link.attr,drivers/leds/trigger/ledtrig-netdev.c +1
-1@@ -417,6 +427,7 @@ static struct attribute *netdev_trig_attrs[] = { &dev_attr_rx.attr, &dev_attr_tx.attr, &dev_attr_interval.attr, + &dev_attr_hw_control.attr, NULL };ATTRIBUTE_GROUPS (netdev_trig); --2.40.1
Signature · 2 lines
Regards, Kalesh A P
Re: [net-next PATCH v5 3/3] leds: trigger: netdev: expose hw_control status via sysfs
Quoted 9 lines
+static ssize_t hw_control_show(struct device *dev, + struct device_attribute *attr, char *buf) +{ + struct led_netdev_data *trigger_data = led_trigger_get_drvdata (dev); + + return sprintf(buf, "%d\n", trigger_data->hw_control);[Kalesh]: How about using
sysfs_emit?
Currently, there are zero instances of sysfs_emit() in ledtrig-netdev, and in any files in drivers/leds/trigger/, or even drivers/leds.
So i think it would be better to keep this consistent with the rest of the code in this file, and have a follow up patchset which reviews and converts the 52 sprintf() in drivers/leds.
Andrew
Kalesh Anakkur Purayil
Reviewed-byRe: [net-next PATCH v5 3/3] leds: trigger: netdev: expose hw_control status via sysfs
Quoted 10 lines · Andrew Lunn
Quoted 2 lines
+static
ssize_thw_control_show(struct device *dev,
+ structdevice_attribute*attr, char*buf)
Quoted 2 lines
+{
+ structled_netdev_data*trigger_data=
led_trigger_get_drvdataQuoted 4 lines
(dev); + + return sprintf(buf, "%d\n", trigger_data->hw_control);
Quoted 9 lines
Quoted 1 line
[Kalesh]: How about using
sysfs_emit?Currently, there are zero instances of
sysfs_emit()in ledtrig-netdev, and in any files indrivers/leds/trigger/, or evendrivers/leds.So i think it would be better to keep this consistent with the rest of the code in this file, and have a follow up patchset which reviews and converts the 52
sprintf()indrivers/leds.
Sounds good, thank you
Quoted 3 lines
Andrew
Signature · 2 lines
Regards, Kalesh A P
Re: [net-next PATCH v5 3/3] leds: trigger: netdev: expose hw_control status via sysfs
In reply to Christian MarangiQuoted 9 lines · Christian Marangi
Expose
hw_controlstatus via sysfs for the netdev trigger to give userspace better understanding of the current state of the trigger and the LED.Signed-off-by Christian Marangi <[email protected]>Reviewed-by Andrew Lunn <[email protected]>--- drivers/leds/trigger/ledtrig-netdev.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
Signature · 1 line
Lee Jones [李琼斯]
This series was applied to netdev/net-next.git (main) by Jakub Kicinski <[email protected]>:
Hello:
This series was applied to netdev/net-next.git (main) by Jakub Kicinski <[email protected]>:
Quoted 10 lines · On Mon, 19 Jun 2023 22:46:57 +0200 you wrote:
This is a continue of [1]. It was decided to take a more gradual approach to implement LEDs support for switch and phy starting with basic support and then implementing the hw control part when we have all the prereq done.
This should be the final part for the netdev trigger.
I added net-next tag and added netdev mailing list since I was informed that this should be merged with netdev branch.[...]
Here is the summary with links:
- [net-next,v5,1/3] leds: trigger: netdev: add additional specific link speed mode
https://git.kernel.org/netdev/net-next/c/d5e01266e7f5 - [net-next,v5,2/3] leds: trigger: netdev: add additional specific link duplex mode https://git.kernel.org/netdev/net-next/c/f22f95b9ff15 - [net-next,v5,3/3] leds: trigger: netdev: expose hw_control status via sysfs https://git.kernel.org/netdev/net-next/c/b655892ffd6d
You are awesome, thank you!
Signature · 2 lines
Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html