openwrt/target
Jonas Jelonek 4cf401088e realtek: dts: drop SYS LED of XikeStor SKS8310-8X
The sys_led node in the device tree is wrong and doesn't work. On GPIO
23 nothing seems to be connected. The switch has a SYS LED but as with a
lot other Realtek switches, this LED is connected to the pin A0, which
can be driven as GPIO0 or system LED. The hardware-assisted behavior is
configured during boot by u-boot.

Though it is be possible to deactivate the hardware-assisted behavior
and give userspace control over the LED, it doesn't work for this
switch. XikeStor apparently decided to hook the SYS LED to some kind of
external watchdog. This one seems to expect a LOW signal on that line
periodically. This leaves room for two options:

1) keep behavior and let the LED blink as configured by u-boot
2) turn off LED completely

Option 2) is rather odd and may confuse users, thus it is better to keep
the behavior as-is for now. u-boot configures the LED to blink fast
which might be annoying. As soon as we have a way in the device tree to
specify different blinking frequencies as supported by the hardware,
this can be smoothened.

Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/22211
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
2026-03-01 14:46:12 +01:00
..
imagebuilder toolchain: sdk: ib: allow external toolchain override 2026-02-20 22:54:26 +01:00
linux realtek: dts: drop SYS LED of XikeStor SKS8310-8X 2026-03-01 14:46:12 +01:00
llvm-bpf
sdk toolchain: sdk: ib: allow external toolchain override 2026-02-20 22:54:26 +01:00
toolchain
Config.in targets: add REGULATOR_SUPPORT auto-feature 2026-03-01 10:59:19 +01:00
Makefile