Lines Matching full:leds

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
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
17 registers you have some limited control over rerouting the LEDs (as
21 reason, hardware controlled LEDs aren't registered as LED class devices.
24   - compatible : should be "brcm,bcm6328-leds".
30   - brcm,serial-leds : Boolean, enables Serial LEDs.
32   - brcm,serial-mux : Boolean, enables Serial LEDs multiplexing.
38   - brcm,serial-shift-inv : Boolean, inverts Serial LEDs shift direction.
41 Each LED is represented as a sub-node of the brcm,bcm6328-leds device.
44   - reg : LED pin number (only LEDs 0 to 23 are valid).
47   a) Optional properties for sub-nodes related to software controlled LEDs:
48     - label : see Documentation/devicetree/bindings/leds/common.txt
52       Documentation/devicetree/bindings/leds/common.txt
54       Documentation/devicetree/bindings/leds/common.txt
56   b) Optional properties for sub-nodes related to hardware controlled LEDs:
61       these LEDs. Only valid for LEDs 0 to 7, where LED signals 0 to 3 may
62       be muxed to LEDs 0 to 3, and signals 4 to 7 may be muxed to LEDs
67       these LEDs. Only valid for LEDs 0 to 7, where LED signals 0 to 3 may
68       be muxed to LEDs 0 to 3, and signals 4 to 7 may be muxed to LEDs
73 Scenario 1 : BCM6328 with 4 EPHY LEDs
75 		compatible = "brcm,bcm6328-leds";
114 Scenario 2 : BCM63268 with Serial/GPHY0 LEDs
116 		compatible = "brcm,bcm6328-leds";
120 		brcm,serial-leds;
197 		compatible = "brcm,bcm6328-leds";
249 		compatible = "brcm,bcm6328-leds";
275 Scenario 5 : BCM6362 with EPHY LEDs swapped
277 		compatible = "brcm,bcm6328-leds";