[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8c8ba30d-dbec-47db-ae8c-a734fb2468c0@lunn.ch>
Date: Wed, 10 Jul 2024 15:33:30 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Lukasz Majewski <lukma@...x.de>
Cc: Pavel Machek <pavel@....cz>, Lee Jones <lee@...nel.org>,
Heiner Kallweit <hkallweit1@...il.com>,
Christian Marangi <ansuelsmth@...il.com>,
Jakub Kicinski <kuba@...nel.org>,
Marek BehĂșn <kabel@...nel.org>,
Daniel Golle <daniel@...rotopia.org>,
Li Zetao <lizetao1@...wei.com>, linux-leds@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 net-next] leds: trigger: netdev: Add support for
tx_err and rx_err notification with LEDs
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@...001a000.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. Do you have a real customer use case for this? What sort of systems
do you have which do have sufficient errors to justify an LED?
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.
Andrew
Powered by blists - more mailing lists