Re: [PATCH] arm64: dts: allwiner: h5: OrangePi PC2: add ethernet LEDs
From: Aleksander Jan Bajkowski
Date: Sun Sep 27 2026 - 18:51:42 EST
Hi Andre,
I see that my previous reply didn't reach lkml
On 09/09/2025 02:24, Andre Przywara wrote:
On Mon, 18 Aug 2025 18:35:13 +0200
Aleksander Jan Bajkowski <olek2@xxxxx> wrote:
This patch adds support for Ethernet LEDs.So I tried this on my OPi-PC2, but I cannot influence the LEDs. I have
CONFIG_LED_TRIGGER_PHY and CONFIG_LEDS_TRIGGER_NETDEV built in, and I
see mdio_mux-0.2:01:amber:lan and mdio_mux-0.2:01:green:lan in
/sys/class/leds, but anything I write into trigger does not seem to
change the output: it always stays on the network functionality, I
guess because it's still configured to the PHY hardware wired function?
What am I missing?
You should also set up the name of the device that controls the activity:
Example:
root@OpenWrt:/sys/class/leds/mdio_mux-0.2:01:green:lan# echo "eth0" > device_name
root@OpenWrt:/sys/class/leds/mdio_mux-0.2:01:green:lan# echo "1" > link_10
root@OpenWrt:/sys/class/leds/mdio_mux-0.2:01:green:lan# echo "1" > link_1000
root@OpenWrt:/sys/class/leds/mdio_mux-0.2:01:amber:lan# echo "eth0" > device_name
root@OpenWrt:/sys/class/leds/mdio_mux-0.2:01:amber:lan# echo "1" > rx
root@OpenWrt:/sys/class/leds/mdio_mux-0.2:01:amber:lan# echo "1" > tx
In the second iteration, I added the default-spate = “keep” property. By default,
the LEDs will be activated as before.
Regards,
Aleksander