public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH 0/3] leds: trigger: netdev: add additional modes
@ 2023-06-09 13:51 Christian Marangi
  2023-06-09 13:51 ` [PATCH 1/3] leds: trigger: netdev: add additional specific link speed mode Christian Marangi
                   ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: Christian Marangi @ 2023-06-09 13:51 UTC (permalink / raw)
  To: Pavel Machek, Lee Jones, Christian Marangi, Andrew Lunn,
	David S. Miller, Yang Li, linux-leds, linux-kernel

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.

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.
- Mode for unified tx and rx traffic.

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. For the unified tx and rx
mode, we simply add extra logic to the work function we already have in
the netdev trigger.

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/20230216013230.22978-1-ansuelsmth@gmail.com/
Christian Marangi (3):
  leds: trigger: netdev: add additional specific link speed mode
  leds: trigger: netdev: add additional specific link duplex mode
  leds: trigger: netdev: add additional mode for unified tx/rx traffic

 drivers/leds/trigger/ledtrig-netdev.c | 129 +++++++++++++++++++++++---
 include/linux/leds.h                  |   6 ++
 2 files changed, 124 insertions(+), 11 deletions(-)

-- 
2.40.1


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2023-06-09 14:37 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-06-09 13:51 [PATCH 0/3] leds: trigger: netdev: add additional modes Christian Marangi
2023-06-09 13:51 ` [PATCH 1/3] leds: trigger: netdev: add additional specific link speed mode Christian Marangi
2023-06-09 14:25   ` Andrew Lunn
2023-06-09 13:51 ` [PATCH 2/3] leds: trigger: netdev: add additional specific link duplex mode Christian Marangi
2023-06-09 13:51 ` [PATCH 3/3] leds: trigger: netdev: add additional mode for unified tx/rx traffic Christian Marangi
2023-06-09 14:36   ` Andrew Lunn

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox