Hi Andrew, > On Wed, Jul 10, 2024 at 12:06:51PM +0200, Lukasz Majewski wrote: > > This patch provides support for enabling blinking of LEDs when RX > > or TX errors are detected. > > > > Approach taken in this patch is similar to one for TX or RX data > > transmission indication (i.e. TRIGGER_NETDEV_TX/RX attribute). > > > > One can inspect transmission errors with: > > ip -s link show eth0 > > > > Example LED configuration: > > cd /sys/devices/platform/amba_pl@0/a001a000.leds/leds/ > > echo netdev > mode:blue/trigger && \ > > echo eth0 > mode:blue/device_name && \ > > echo 1 > mode:blue/tx_err > > When i look at the machines around me, they all have an error count of > 0. This is mostly true for ethernet. However, it happens on some low-level drivers that errors field is not zero when e.g. the received frame is malformed due to harsh work environment. > Do you have a real customer use case for this? Yes. The problem is apparent mostly with can interfaces and transmission for it. > What sort of systems > do you have which do have sufficient errors to justify an LED? In my case it is an embedded industrial/automotive controller with 10+ RGB LEDs. It only has LEDs to communicate with user. The way how and when they blink shows the status of the device. With this patch one is able to spot if some transmission is failing (among other things). > > There is no standardisation of LEDs. Every vendor implements something > different. What i don't want is lots of different blink patterns, > which nobody ever uses. As you can assess from the code - this patch extends neatly the current code, with use case valid for my customer. > > Andrew Best regards, Lukasz Majewski -- DENX Software Engineering GmbH, Managing Director: Erika Unter HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@xxxxxxx
Attachment:
pgpIFaFrSmsny.pgp
Description: OpenPGP digital signature
