[RFC PATCH v3 6/8] leds: trigger: add hardware-phy-activity trigger
From: Ansuel Smith
Date: Mon Nov 08 2021 - 21:26:54 EST
Add Hardware Only Trigger for PHY Activity. This special trigger is used to
configure and expose the different HW trigger that are provided by the
PHY. Each blink mode can be configured by sysfs and on trigger
activation the hardware mode is enabled.
This currently implement these hw triggers:
- blink_tx: Blink LED on tx packet receive
- blink_rx: Blink LED on rx packet receive
- keep_link_10m: Keep LED on with 10m link speed
- keep_link_100m: Keep LED on with 100m link speed
- kepp_link_1000m: Keep LED on with 1000m link speed
- keep_half_duplex: Keep LED on with half duplex link
- keep_full_duplex: Keep LED on with full duplex link
- option_linkup_over: Ignore blink tx/rx with link keep not active
- option_power_on_reset: Keep LED on with switch reset
- option_blink_2hz: Set blink speed at 2hz for every blink event
- option_blink_4hz: Set blink speed at 4hz for every blink event
- option_blink_8hz: Set blink speed at 8hz for every blink event
- option_blink_auto: Set blink speed at 2hz for 10m link speed,
4hz for 100m and 8hz for 1000m
The trigger will check if the LED driver support the various blink modes
and will expose the blink modes in sysfs.
It will finally enable hw mode for the LED without configuring any rule.
This mean that the LED will blink/follow whatever offload trigger is
active by default and the user needs to manually configure the desired
offload triggers using sysfs.
A flag is passed to configure_offload with the related rule from this
trigger to active or disable.
It's in the led driver interest the detection and knowing how to
elaborate the passed flags and should report -EOPNOTSUPP otherwise.
The different hw triggers are exposed in the led sysfs dir under the
offload-phy-activity subdir.
Signed-off-by: Ansuel Smith <ansuelsmth@xxxxxxxxx>
---
drivers/leds/trigger/Kconfig | 28 +++
drivers/leds/trigger/Makefile | 1 +
.../trigger/ledtrig-hardware-phy-activity.c | 171 ++++++++++++++++++
include/linux/leds.h | 22 +++
4 files changed, 222 insertions(+)
create mode 100644 drivers/leds/trigger/ledtrig-hardware-phy-activity.c
diff --git a/drivers/leds/trigger/Kconfig b/drivers/leds/trigger/Kconfig
index dc6816d36d06..b947b238be3f 100644
--- a/drivers/leds/trigger/Kconfig
+++ b/drivers/leds/trigger/Kconfig
@@ -154,4 +154,32 @@ config LEDS_TRIGGER_TTY
When build as a module this driver will be called ledtrig-tty.
+config LEDS_TRIGGER_HARDWARE_PHY_ACTIVITY
+ tristate "LED Trigger for PHY Activity for Hardware Controlled LED"
+ depends on LEDS_HARDWARE_CONTROL
+ help
+ This allows LEDs to be configured to run by hardware and offloaded
+ based on some rules. The LED will blink or be on based on the PHY
+ Activity for example on packet receive or based on the link speed.
+
+ The current supported offload triggers are:
+ - blink_tx: Blink LED on tx packet receive
+ - blink_rx: Blink LED on rx packet receive
+ - keep_link_10m: Keep LED on with 10m link speed
+ - keep_link_100m: Keep LED on with 100m link speed
+ - keep_link_1000m: Keep LED on with 1000m link speed
+ - keep_half_duplex: Keep LED on with half duplex link
+ - keep_full_duplex: Keep LED on with full duplex link
+ - option_linkup_over: Blink rules are ignored with absent link
+ - option_power_on_reset: Power ON Led on Switch/PHY reset
+ - option_blink_2hz: Set blink speed at 2hz for every blink event
+ - option_blink_4hz: Set blink speed at 4hz for every blink event
+ - option_blink_8hz: Set blink speed at 8hz for every blink event
+
+ These blink modes are present in the LED sysfs dir under
+ hardware-phy-activity if supported by the LED driver.
+
+ This trigger can be used only by LEDs that supports Hardware mode
+
+
endif # LEDS_TRIGGERS
diff --git a/drivers/leds/trigger/Makefile b/drivers/leds/trigger/Makefile
index 25c4db97cdd4..f5d0d0057d2b 100644
--- a/drivers/leds/trigger/Makefile
+++ b/drivers/leds/trigger/Makefile
@@ -16,3 +16,4 @@ obj-$(CONFIG_LEDS_TRIGGER_NETDEV) += ledtrig-netdev.o
obj-$(CONFIG_LEDS_TRIGGER_PATTERN) += ledtrig-pattern.o
obj-$(CONFIG_LEDS_TRIGGER_AUDIO) += ledtrig-audio.o
obj-$(CONFIG_LEDS_TRIGGER_TTY) += ledtrig-tty.o
+obj-$(CONFIG_LEDS_TRIGGER_HARDWARE_PHY_ACTIVITY) += ledtrig-hardware-phy-activity.o
diff --git a/drivers/leds/trigger/ledtrig-hardware-phy-activity.c b/drivers/leds/trigger/ledtrig-hardware-phy-activity.c
new file mode 100644
index 000000000000..7fd0557fe878
--- /dev/null
+++ b/drivers/leds/trigger/ledtrig-hardware-phy-activity.c
@@ -0,0 +1,171 @@
+// SPDX-License-Identifier: GPL-2.0-only
+
+#include <linux/kernel.h>
+#include <linux/init.h>
+#include <linux/leds.h>
+#include <linux/slab.h>
+
+#define PHY_ACTIVITY_MAX_TRIGGERS 12
+
+#define DEFINE_OFFLOAD_TRIGGER(trigger_name, trigger) \
+ static ssize_t trigger_name##_show(struct device *dev, \
+ struct device_attribute *attr, char *buf) \
+ { \
+ struct led_classdev *led_cdev = led_trigger_get_led(dev); \
+ int val; \
+ val = led_cdev->hw_control_configure(led_cdev, trigger, BLINK_MODE_READ); \
+ return sprintf(buf, "%d\n", val ? 1 : 0); \
+ } \
+ static ssize_t trigger_name##_store(struct device *dev, \
+ struct device_attribute *attr, \
+ const char *buf, size_t size) \
+ { \
+ struct led_classdev *led_cdev = led_trigger_get_led(dev); \
+ unsigned long state; \
+ int cmd, ret; \
+ ret = kstrtoul(buf, 0, &state); \
+ if (ret) \
+ return ret; \
+ cmd = !!state ? BLINK_MODE_ENABLE : BLINK_MODE_DISABLE; \
+ /* Update the configuration with every change */ \
+ led_cdev->hw_control_configure(led_cdev, trigger, cmd); \
+ return size; \
+ } \
+ DEVICE_ATTR_RW(trigger_name)
+
+/* Expose sysfs for every blink to be configurable from userspace */
+DEFINE_OFFLOAD_TRIGGER(blink_tx, BLINK_TX);
+DEFINE_OFFLOAD_TRIGGER(blink_rx, BLINK_RX);
+DEFINE_OFFLOAD_TRIGGER(keep_link_10m, KEEP_LINK_10M);
+DEFINE_OFFLOAD_TRIGGER(keep_link_100m, KEEP_LINK_100M);
+DEFINE_OFFLOAD_TRIGGER(keep_link_1000m, KEEP_LINK_1000M);
+DEFINE_OFFLOAD_TRIGGER(keep_half_duplex, KEEP_HALF_DUPLEX);
+DEFINE_OFFLOAD_TRIGGER(keep_full_duplex, KEEP_FULL_DUPLEX);
+DEFINE_OFFLOAD_TRIGGER(option_linkup_over, OPTION_LINKUP_OVER);
+DEFINE_OFFLOAD_TRIGGER(option_power_on_reset, OPTION_POWER_ON_RESET);
+DEFINE_OFFLOAD_TRIGGER(option_blink_2hz, OPTION_BLINK_2HZ);
+DEFINE_OFFLOAD_TRIGGER(option_blink_4hz, OPTION_BLINK_4HZ);
+DEFINE_OFFLOAD_TRIGGER(option_blink_8hz, OPTION_BLINK_8HZ);
+
+/* The attrs will be placed dynamically based on the supported triggers */
+static struct attribute *phy_activity_attrs[PHY_ACTIVITY_MAX_TRIGGERS + 1];
+
+static int offload_phy_activity_activate(struct led_classdev *led_cdev)
+{
+ u32 checked_list = 0;
+ int i, trigger, ret;
+
+ /* Scan the supported offload triggers and expose them in sysfs if supported */
+ for (trigger = 0, i = 0; trigger < PHY_ACTIVITY_MAX_TRIGGERS; trigger++) {
+ if (!(checked_list & BLINK_TX) &&
+ led_trigger_blink_mode_is_supported(led_cdev, BLINK_TX)) {
+ phy_activity_attrs[i++] = &dev_attr_blink_tx.attr;
+ checked_list |= BLINK_TX;
+ }
+
+ if (!(checked_list & BLINK_RX) &&
+ led_trigger_blink_mode_is_supported(led_cdev, BLINK_RX)) {
+ phy_activity_attrs[i++] = &dev_attr_blink_rx.attr;
+ checked_list |= BLINK_RX;
+ }
+
+ if (!(checked_list & KEEP_LINK_10M) &&
+ led_trigger_blink_mode_is_supported(led_cdev, KEEP_LINK_10M)) {
+ phy_activity_attrs[i++] = &dev_attr_keep_link_10m.attr;
+ checked_list |= KEEP_LINK_10M;
+ }
+
+ if (!(checked_list & KEEP_LINK_100M) &&
+ led_trigger_blink_mode_is_supported(led_cdev, KEEP_LINK_100M)) {
+ phy_activity_attrs[i++] = &dev_attr_keep_link_100m.attr;
+ checked_list |= KEEP_LINK_100M;
+ }
+
+ if (!(checked_list & KEEP_LINK_1000M) &&
+ led_trigger_blink_mode_is_supported(led_cdev, KEEP_LINK_1000M)) {
+ phy_activity_attrs[i++] = &dev_attr_keep_link_1000m.attr;
+ checked_list |= KEEP_LINK_1000M;
+ }
+
+ if (!(checked_list & KEEP_HALF_DUPLEX) &&
+ led_trigger_blink_mode_is_supported(led_cdev, KEEP_HALF_DUPLEX)) {
+ phy_activity_attrs[i++] = &dev_attr_keep_half_duplex.attr;
+ checked_list |= KEEP_HALF_DUPLEX;
+ }
+
+ if (!(checked_list & KEEP_FULL_DUPLEX) &&
+ led_trigger_blink_mode_is_supported(led_cdev, KEEP_FULL_DUPLEX)) {
+ phy_activity_attrs[i++] = &dev_attr_keep_full_duplex.attr;
+ checked_list |= KEEP_FULL_DUPLEX;
+ }
+
+ if (!(checked_list & OPTION_LINKUP_OVER) &&
+ led_trigger_blink_mode_is_supported(led_cdev, OPTION_LINKUP_OVER)) {
+ phy_activity_attrs[i++] = &dev_attr_option_linkup_over.attr;
+ checked_list |= OPTION_LINKUP_OVER;
+ }
+
+ if (!(checked_list & OPTION_POWER_ON_RESET) &&
+ led_trigger_blink_mode_is_supported(led_cdev, OPTION_POWER_ON_RESET)) {
+ phy_activity_attrs[i++] = &dev_attr_option_power_on_reset.attr;
+ checked_list |= OPTION_POWER_ON_RESET;
+ }
+
+ if (!(checked_list & OPTION_BLINK_2HZ) &&
+ led_trigger_blink_mode_is_supported(led_cdev, OPTION_BLINK_2HZ)) {
+ phy_activity_attrs[i++] = &dev_attr_option_blink_2hz.attr;
+ checked_list |= OPTION_BLINK_2HZ;
+ }
+
+ if (!(checked_list & OPTION_BLINK_4HZ) &&
+ led_trigger_blink_mode_is_supported(led_cdev, OPTION_BLINK_4HZ)) {
+ phy_activity_attrs[i++] = &dev_attr_option_blink_4hz.attr;
+ checked_list |= OPTION_BLINK_4HZ;
+ }
+
+ if (!(checked_list & OPTION_BLINK_8HZ) &&
+ led_trigger_blink_mode_is_supported(led_cdev, OPTION_BLINK_8HZ)) {
+ phy_activity_attrs[i++] = &dev_attr_option_blink_8hz.attr;
+ checked_list |= OPTION_BLINK_8HZ;
+ }
+ }
+
+ /* Enable hardware mode. No custom configuration is applied,
+ * the LED driver will use whatever default configuration is
+ * currently configured.
+ */
+ ret = led_cdev->hw_control_start(led_cdev);
+ if (ret)
+ return ret;
+
+ return 0;
+}
+
+static void offload_phy_activity_deactivate(struct led_classdev *led_cdev)
+{
+ led_cdev->hw_control_stop(led_cdev);
+}
+
+static const struct attribute_group phy_activity_group = {
+ .name = "hardware-phy-activity",
+ .attrs = phy_activity_attrs,
+};
+
+static const struct attribute_group *phy_activity_groups[] = {
+ &phy_activity_group,
+ NULL,
+};
+
+static struct led_trigger offload_phy_activity_trigger = {
+ .supported_blink_modes = HARDWARE_ONLY,
+ .name = "hardware-phy-activity",
+ .activate = offload_phy_activity_activate,
+ .deactivate = offload_phy_activity_deactivate,
+ .groups = phy_activity_groups,
+};
+
+static int __init offload_phy_activity_init(void)
+{
+ return led_trigger_register(&offload_phy_activity_trigger);
+}
+device_initcall(offload_phy_activity_init);
diff --git a/include/linux/leds.h b/include/linux/leds.h
index 087debe6716d..3d2e06db6839 100644
--- a/include/linux/leds.h
+++ b/include/linux/leds.h
@@ -555,6 +555,28 @@ enum led_trigger_netdev_modes {
TRIGGER_NETDEV_RX,
};
+#ifdef CONFIG_LEDS_TRIGGER_HARDWARE_PHY_ACTIVITY
+/* 3 main category for offload trigger:
+ * - blink: the led will blink on trigger
+ * - keep: the led will be kept on with condition
+ * - option: a configuration value internal to the led on how offload works
+ */
+enum hardware_phy_activity {
+ BLINK_TX, /* Blink on TX traffic */
+ BLINK_RX, /* Blink on RX traffic */
+ KEEP_LINK_10M, /* LED on with 10M link */
+ KEEP_LINK_100M, /* LED on with 100M link */
+ KEEP_LINK_1000M, /* LED on with 1000M link */
+ KEEP_HALF_DUPLEX, /* LED on with Half-Duplex link */
+ KEEP_FULL_DUPLEX, /* LED on with Full-Duplex link */
+ OPTION_LINKUP_OVER, /* LED will be on with KEEP blink mode and blink on BLINK traffic */
+ OPTION_POWER_ON_RESET, /* LED will be on Switch reset */
+ OPTION_BLINK_2HZ, /* LED will blink with any offload_trigger at 2Hz */
+ OPTION_BLINK_4HZ, /* LED will blink with any offload_trigger at 4Hz */
+ OPTION_BLINK_8HZ, /* LED will blink with any offload_trigger at 8Hz */
+};
+#endif
+
/* Trigger specific functions */
#ifdef CONFIG_LEDS_TRIGGER_DISK
void ledtrig_disk_activity(bool write);
--
2.32.0