Lines Matching +full:led +full:- +full:7
7 as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
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.
24 - compatible : should be "brcm,bcm6328-leds".
25 - #address-cells : must be 1.
26 - #size-cells : must be 0.
27 - reg : BCM6328 LED controller address and size.
30 - brcm,serial-leds : Boolean, enables Serial LEDs.
32 - brcm,serial-mux : Boolean, enables Serial LEDs multiplexing.
34 - brcm,serial-clk-low : Boolean, makes clock signal active low.
36 - brcm,serial-dat-low : Boolean, makes data signal active low.
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.
43 LED sub-node required properties:
44 - reg : LED pin number (only LEDs 0 to 23 are valid).
46 LED sub-node optional properties:
47 a) Optional properties for sub-nodes related to software controlled LEDs:
48 - label : see Documentation/devicetree/bindings/leds/common.txt
49 - active-low : Boolean, makes LED active low.
51 - default-state : see
53 - linux,default-trigger : see
56 b) Optional properties for sub-nodes related to hardware controlled LEDs:
57 - brcm,hardware-controlled : Boolean, makes this LED hardware controlled.
59 - brcm,link-signal-sources : An array of hardware link
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
65 - brcm,activity-signal-sources : An array of hardware activity
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
74 leds0: led-controller@10000800 {
75 compatible = "brcm,bcm6328-leds";
76 #address-cells = <1>;
77 #size-cells = <0>;
82 active-low;
87 active-low;
92 active-low;
94 default-state = "on";
98 brcm,hardware-controlled;
102 brcm,hardware-controlled;
106 brcm,hardware-controlled;
110 brcm,hardware-controlled;
115 leds0: led-controller@10001900 {
116 compatible = "brcm,bcm6328-leds";
117 #address-cells = <1>;
118 #size-cells = <0>;
120 brcm,serial-leds;
121 brcm,serial-dat-low;
122 brcm,serial-shift-inv;
126 brcm,hardware-controlled;
127 brcm,link-signal-sources = <0>;
131 brcm,hardware-controlled;
132 brcm,link-signal-sources = <1>;
136 active-low;
141 active-low;
146 active-low;
149 wps_green@7 {
150 reg = <7>;
151 active-low;
156 active-low;
161 brcm,hardware-controlled;
165 brcm,hardware-controlled;
169 brcm,hardware-controlled;
173 brcm,hardware-controlled;
177 brcm,hardware-controlled;
181 brcm,hardware-controlled;
185 brcm,hardware-controlled;
189 active-low;
191 default-state = "on";
195 Scenario 3 : BCM6362 with 1 LED for each EPHY
196 leds0: led-controller@10001900 {
197 compatible = "brcm,bcm6328-leds";
198 #address-cells = <1>;
199 #size-cells = <0>;
204 brcm,hardware-controlled;
205 brcm,link-signal-sources = <0>;
206 brcm,activity-signal-sources = <0>;
207 /* USB link/activity routed to USB LED */
211 brcm,hardware-controlled;
212 brcm,activity-signal-sources = <1>;
213 /* INET activity routed to INET LED */
217 brcm,hardware-controlled;
218 brcm,link-signal-sources = <4>;
219 /* EPHY0 link routed to EPHY0 LED */
223 brcm,hardware-controlled;
224 brcm,link-signal-sources = <5>;
225 /* EPHY1 link routed to EPHY1 LED */
229 brcm,hardware-controlled;
230 brcm,link-signal-sources = <6>;
231 /* EPHY2 link routed to EPHY2 LED */
233 ephy3@7 {
234 reg = <7>;
235 brcm,hardware-controlled;
236 brcm,link-signal-sources = <7>;
237 /* EPHY3 link routed to EPHY3 LED */
241 active-low;
243 default-state = "on";
247 Scenario 4 : BCM6362 with 1 LED for all EPHYs
248 leds0: led-controller@10001900 {
249 compatible = "brcm,bcm6328-leds";
250 #address-cells = <1>;
251 #size-cells = <0>;
256 brcm,hardware-controlled;
257 brcm,link-signal-sources = <0 1>;
258 brcm,activity-signal-sources = <0 1>;
259 /* USB/INET link/activity routed to USB LED */
263 brcm,hardware-controlled;
264 brcm,link-signal-sources = <4 5 6 7>;
265 /* EPHY0/1/2/3 link routed to EPHY0 LED */
269 active-low;
271 default-state = "on";
276 leds0: led-controller@10001900 {
277 compatible = "brcm,bcm6328-leds";
278 #address-cells = <1>;
279 #size-cells = <0>;
284 brcm,hardware-controlled;
285 brcm,link-signal-sources = <0>;
286 brcm,activity-signal-sources = <0 1>;
287 /* USB link/act and INET act routed to USB LED */
291 brcm,hardware-controlled;
292 brcm,link-signal-sources = <7>;
293 /* EPHY3 link routed to EPHY0 LED */
297 brcm,hardware-controlled;
298 brcm,link-signal-sources = <6>;
299 /* EPHY2 link routed to EPHY1 LED */
303 brcm,hardware-controlled;
304 brcm,link-signal-sources = <5>;
305 /* EPHY1 link routed to EPHY2 LED */
307 ephy3@7 {
308 reg = <7>;
309 brcm,hardware-controlled;
310 brcm,link-signal-sources = <4>;
311 /* EPHY0 link routed to EPHY3 LED */
315 active-low;
317 default-state = "on";