On Mon, 8 Nov 2021 20:08:53 +0100 Ansuel Smith <ansuelsmth@xxxxxxxxx> wrote: > > Well, if the PHY allows to manipulate the LEDs ON/OFF state (in other > > words "full control by SW", or ability to implement brightness_set() > > method), then netdev trigger should blink the LED in SW via this > > mechanism (which is something it would do now). A new sysfs file, > > "offloaded", can indicate whether the trigger is offloaded to HW or not. > > > > Are all these sysfs entry OK? I mean if we want to add support for he > main blinking modes, the number will increase to at least 10 additional > entry. See below. > > If, on the other hand, the LED cannot be controlled by SW, and it only > > support some HW control modes, then there are multiple ways how to > > implement what should be done, and we need to discuss this. > > > > For example suppose that the PHY LED pin supports indicating LINK, > > blinking on activity, or both, but it doesn't support blinking on rx > > only, or tx only. > > > > Since the LED is always indicating something about one network device, > > the netdev trigger should be always activated for this LED and it > > should be impossible to deactivate it. Also, it should be impossible to > > change device_name. > > > > $ cd /sys/class/leds/<LED> > > $ cat device_name > > eth0 > > $ echo eth1 >device_name > > Operation not supported. > > $ echo none >trigger > > Operation not supported. > > > > Now suppose that the driver by default enabled link indication, so we > > have: > > $ cat link > > 1 > > $ cat rx > > 0 > > $ cat tx > > 0 > > > > We want to enable blink on activity, but the LED supports only blinking > > on both rx/tx activity, rx only or tx only is not supported. > > > > Currently the only way to enable this is to do > > $ echo 1 >rx > > $ echo 1 >tx > > but the first call asks for (link=1, rx=1, tx=0), which is impossible. > > > > There are multiple things which can be done: > > - "echo 1 >rx" indicates error, but remembers the setting > > - "echo 1 >rx" quietly fails, without error indication. Something can > > be written to dmesg about nonsupported mode > > - "echo 1 >rx" succeeds, but also sets tx=1 > > - rx and tx are non-writable, writing always fails. Another sysfs file > > is created, which lists modes that are actually supported, and allows > > to select between them. When a mode is selected, link,rx,tx are > > filled automatically, so that user may read them to know what the LED > > is actually doing > > - something different? > > > > Expose only the supported blinking modes? (in conjunciong with a generic > traffic blinking mode) The problem with exposing only supported blinking modes is that you can't hide rx and tx files and create a new, rxtx file. That would break netdev trigger ABI. > The initial question was Should we support a mixed mode offloaed > blinking modes and blinking modes simulated by sw? I assume no as i > don't think a device that supports that exist. If you mean something like: the PHY can blink on tx, but not on rx, and I want to blink on rx/tx, do I will enable HW blinking on tx, and on rx I will blink from software, then no. If I can blink in software, then this case should be all done in software. If software blinking is not supported, then this setting is simply unsupported by the LED. Let's at first implement offloading of only those things that are supported by netdev trigger already in SW, so link, rx and tx. When this works OK and gets merged, we can try to extend the netdev trigger to support more modes in SW, and then implement offloading of these modes. Marek
