Lines Matching full:led

13 BCM6328 LED controller has a HWDIS register, which controls whether a LED
16 is usually 1:1 for hardware to LED signals, but through the activity/link
18 explained later in brcm,link-signal-sources). Even if a LED is hardware
21 reason, hardware controlled LEDs aren't registered as LED class devices.
27   - reg : BCM6328 LED controller address and size.
41 Each LED is represented as a sub-node of the brcm,bcm6328-leds device.
43 LED sub-node required properties:
44   - reg : LED pin number (only LEDs 0 to 23 are valid).
46 LED sub-node optional properties:
49     - active-low : Boolean, makes LED active low.
57     - brcm,hardware-controlled : Boolean, makes this LED hardware controlled.
61       these LEDs. Only valid for LEDs 0 to 7, where LED signals 0 to 3 may
63       4 to 7. A signal can be muxed to more than one LED, and one LED can
67       these LEDs. Only valid for LEDs 0 to 7, where LED signals 0 to 3 may
69       4 to 7. A signal can be muxed to more than one LED, and one LED can
74 	leds0: led-controller@10000800 {
115 	leds0: led-controller@10001900 {
195 Scenario 3 : BCM6362 with 1 LED for each EPHY
196 	leds0: led-controller@10001900 {
207 			/* USB link/activity routed to USB LED */
213 			/* INET activity routed to INET LED */
219 			/* EPHY0 link routed to EPHY0 LED */
225 			/* EPHY1 link routed to EPHY1 LED */
231 			/* EPHY2 link routed to EPHY2 LED */
237 			/* EPHY3 link routed to EPHY3 LED */
247 Scenario 4 : BCM6362 with 1 LED for all EPHYs
248 	leds0: led-controller@10001900 {
259 			/* USB/INET link/activity routed to USB LED */
265 			/* EPHY0/1/2/3 link routed to EPHY0 LED */
276 	leds0: led-controller@10001900 {
287 			/* USB link/act and INET act routed to USB LED */
293 			/* EPHY3 link routed to EPHY0 LED */
299 			/* EPHY2 link routed to EPHY1 LED */
305 			/* EPHY1 link routed to EPHY2 LED */
311 			/* EPHY0 link routed to EPHY3 LED */