[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230419210743.3594-1-ansuelsmth@gmail.com>
Date: Wed, 19 Apr 2023 23:07:38 +0200
From: Christian Marangi <ansuelsmth@...il.com>
To: Pavel Machek <pavel@....cz>, Lee Jones <lee@...nel.org>,
Christian Marangi <ansuelsmth@...il.com>,
Martin Schiller <ms@....tdt.de>, linux-leds@...r.kernel.org,
linux-kernel@...r.kernel.org, Andrew Lunn <andrew@...n.ch>
Subject: [PATCH 0/5] leds: trigger: netdev: fixup preparation for LEDs hw control
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 is a small series in preparation for a bigger change adding support
for LEDs hw control.
Some minor fixup and improvements are required to add support for LEDs hw
control for the netdev trigger.
The main fixes are switching to mutex from spinlocks and adding namespace
to netdev trigger enum modes. These will be exposed in the future in the
generic linux include folder so LEDs driver may supports these specific
modes.
While working on htis it was also discovered a bug addressed in the first
patch of this series.
Changes from the old v8 series:
- Reword some commits and add more info on why the changes is needed
- Add fixup patch on dev rename
Christian Marangi (5):
leds: trigger: netdev: recheck NETDEV_LED_MODE_LINKUP on dev rename
leds: trigger: netdev: drop NETDEV_LED_MODE_LINKUP from mode
leds: trigger: netdev: rename add namespace to netdev trigger enum
modes
leds: trigger: netdev: convert device attr to macro
leds: trigger: netdev: use mutex instead of spinlocks
drivers/leds/trigger/ledtrig-netdev.c | 151 ++++++++++----------------
1 file changed, 59 insertions(+), 92 deletions(-)
--
2.39.2
Powered by blists - more mailing lists