1 LEDs connected to Broadcom BCM6328 controller
3 This controller is present on BCM6318, BCM6328, BCM6362 and BCM63268.
4 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
5 However, on some devices there are Serial LEDs (LEDs connected to a 74x164
6 controller), which can either be controlled by software (exporting the 74x164
7 as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
8 by hardware using this driver.
9 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
11 controlled, so the only chance to keep them working is by using this driver.
14 - compatible : should be "brcm,bcm6328-leds".
15 - #address-cells : must be 1.
16 - #size-cells : must be 0.
17 - reg : BCM6328 LED controller address and size.
20 - brcm,serial-leds : Boolean, enables Serial LEDs.
22 - brcm,serial-mux : Boolean, enables Serial LEDs multiplexing.
24 - brcm,serial-clk-low : Boolean, makes clock signal active low.
26 - brcm,serial-dat-low : Boolean, makes data signal active low.
28 - brcm,serial-shift-inv : Boolean, inverts Serial LEDs shift direction.
31 Each LED is represented as a sub-node of the brcm,bcm6328-leds device.
33 LED sub-node required properties:
34 - reg : LED pin number (only LEDs 0 to 23 are valid).
36 LED sub-node optional properties:
37 - label : see Documentation/devicetree/bindings/leds/common.txt
38 - active-low : Boolean, makes LED active low.
42 Scenario 1 : BCM6328 with 4 GPIO LEDs
43 leds0: led-controller@10000800 {
44 compatible = "brcm,bcm6328-leds";
47 reg = <0x10000800 0x24>;
62 label = "green:power";
66 Scenario 2 : BCM63268 with Serial LEDs
67 leds0: led-controller@10001900 {
68 compatible = "brcm,bcm6328-leds";
71 reg = <0x10001900 0x24>;
74 brcm,serial-shift-inv;
104 label = "green:power";