path: root/dts/Bindings/leds/leds-bcm6328.txt
diff options
authorSascha Hauer <>2021-05-25 09:18:30 +0200
committerSascha Hauer <>2021-05-25 09:18:30 +0200
commit4104b26d8b2d5feb372de613597143605e4bfe38 (patch)
treec0e26a3856a00f506b7f185a752606b7816f4900 /dts/Bindings/leds/leds-bcm6328.txt
parent17f08774cc14ceaedcf9f2dc37aa73e0ebbd2585 (diff)
dts: update to v5.13-rc3
Signed-off-by: Sascha Hauer <>
Diffstat (limited to 'dts/Bindings/leds/leds-bcm6328.txt')
1 files changed, 2 insertions, 2 deletions
diff --git a/dts/Bindings/leds/leds-bcm6328.txt b/dts/Bindings/leds/leds-bcm6328.txt
index ccebce597..a555d9408 100644
--- a/dts/Bindings/leds/leds-bcm6328.txt
+++ b/dts/Bindings/leds/leds-bcm6328.txt
@@ -4,8 +4,8 @@ This controller is present on BCM6318, BCM6328, BCM6362 and BCM63268.
In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
However, on some devices there are Serial LEDs (LEDs connected to a 74x164
controller), which can either be controlled by software (exporting the 74x164
-as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
-by hardware using this driver.
+as spi-gpio. See Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml),
+or by hardware using this driver.
Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
controlled, so the only chance to keep them working is by using this driver.