device-tree-bindings/leds/leds-bcm6328.txt

1 LEDs connected to Broadcom BCM6328 controller
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
7 as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
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
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";
45 		#address-cells = <1>;
46 		#size-cells = <0>;
51 			active-low;
56 			active-low;
61 			active-low;
66 Scenario 2 : BCM63268 with Serial LEDs
67 	leds0: led-controller@10001900 {
68 		compatible = "brcm,bcm6328-leds";
69 		#address-cells = <1>;
70 		#size-cells = <0>;
72 		brcm,serial-leds;
73 		brcm,serial-dat-low;
74 		brcm,serial-shift-inv;
78 			active-low;
83 			active-low;
88 			active-low;
93 			active-low;
98 			active-low;
103 			active-low;