Lines Matching refs:to
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
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.
16 is usually 1:1 for hardware to LED signals, but through the activity/link
19 controlled you are still able to make it blink or light it up if it isn't,
20 but you can't turn it off if the hardware decides to light it up. For this
44 - reg : LED pin number (only LEDs 0 to 23 are valid).
47 a) Optional properties for sub-nodes related to software controlled LEDs:
56 b) Optional properties for sub-nodes related to hardware controlled LEDs:
60 signal sources. Up to four link hardware signals can get muxed into
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
63 4 to 7. A signal can be muxed to more than one LED, and one LED can
66 signal sources. Up to four activity hardware signals can get muxed into
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
69 4 to 7. A signal can be muxed to more than one LED, and one LED can
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 */
259 /* USB/INET link/activity routed to USB LED */
265 /* EPHY0/1/2/3 link routed to EPHY0 LED */
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 */