| /freebsd-src/sys/contrib/device-tree/Bindings/leds/ |
| H A D | common.yaml | 14 LED and flash LED devices provide the same basic functionality as current
15 regulators, but extended with LED and flash LED specific features like
18 Many LED devices expose more than one current output that can be connected
19 to one or more discrete LED component. Since the arrangement of connections
20 can influence the way of the LED device initialization, the LED components
21 have to be tightly coupled with the LED device binding. They are represented
22 by child nodes of the parent LED devic
[all...] |
| H A D | leds-mt6360.yaml | 7 title: LED driver for MT6360 PMIC from MediaTek Integrated.
15 Add MT6360 LED driver include 2-channel Flash LED with torch/strobe mode,
16 and 4-channel RGB LED support Register/Flash/Breath Mode
20 const: mediatek,mt6360-led
29 "^multi-led@[0-5]$":
36 description: Index of the LED.
38 - 0 # LED output ISINK1
39 - 1 # LED output ISINK2
40 - 2 # LED output ISINK3
41 - 3 # LED output ISINKML
[all …]
|
| H A D | leds-lp55xx.yaml | 7 title: TI/National Semiconductor LP55xx and LP8501 LED Drivers
15 LED Drivers.
79 '^multi-led@[0-8]$':
95 "^led@[0-8]$":
101 led-cur:
104 Current setting at each LED channel (mA x10, 0 if LED is not connected)
110 description: Maximum current at each LED channel.
118 "^led@[0-8]$":
124 led
[all...] |
| H A D | qcom,spmi-flash-led.yaml | 4 $id: http://devicetree.org/schemas/leds/qcom,spmi-flash-led.yaml#
7 title: Flash LED device inside Qualcomm Technologies, Inc. PMICs
13 Flash LED controller is present inside some Qualcomm Technologies, Inc. PMICs.
14 The flash LED module can have different number of LED channels supported
25 - qcom,pm6150l-flash-led
26 - qcom,pm8150c-flash-led
27 - qcom,pm8150l-flash-led
28 - qcom,pm8350c-flash-led
29 - qcom,pm8550-flash-led
30 - qcom,pmi8998-flash-led
[all …]
|
| H A D | register-bit-led.txt | 5 single LED. The register bit LEDs appear as children to the
10 Each LED is represented as a sub-node of the syscon device. Each
11 node's name represents the name of the corresponding LED.
13 LED sub-node properties:
16 - compatible : must be "register-bit-led"
17 - offset : register offset to the register controlling this LED
18 - mask : bit mask for the bit controlling this LED in the register
26 - default-state: (optional) The initial state of the LED
35 led@8.0 {
36 compatible = "register-bit-led";
[all …]
|
| H A D | leds-pm8058.txt | 1 Qualcomm PM8058 LED driver
4 an LED driver block for up to six LEDs: three normal LEDs, two
5 "flash" LEDs and one "keypad backlight" LED. The names are
6 quoted because sometimes these LED drivers are used for wildly
12 do they support external triggers. They are just powerful LED
19 Each LED is represented as a sub-node of the syscon device. Each
20 node's name represents the name of the corresponding LED.
22 LED sub-node properties:
26 "qcom,pm8058-led" (for the normal LEDs at 0x131, 0x132 and 0x133)
27 "qcom,pm8058-keypad-led" (for the "keypad" LED at 0x48)
[all …]
|
| H A D | leds-lp55xx.txt | 1 Binding for TI/National Semiconductor LP55xx Led Drivers
15 - led-cur: Current setting at each led channel (mA x10, 0 if led is not connected)
16 - max-cur: Maximun current at each led channel.
33 3 LED channels, external clock used. Channel names are 'lp5521_pri:channel0',
44 led-cur = /bits/ 8 <0x2f>;
50 led-cur = /bits/ 8 <0x2f>;
55 led-cur = /bits/ 8 <0x2f>;
61 9 LED channels with specific name. Internal clock used.
79 led-cur = /bits/ 8 <0x14>;
85 led-cur = /bits/ 8 <0x14>;
[all …]
|
| H A D | leds-mt6323.txt | 1 Device Tree Bindings for LED support on MT6323 PMIC
3 MT6323 LED controller is subfunction provided by MT6323 PMIC, so the LED
16 - "mediatek,mt6323-led"
17 - "mediatek,mt6331-led"
18 - "mediatek,mt6332-led"
22 Each led is represented as a child node of the mediatek,mt6323-led that
23 describes the initial behavior for each LED physically and currently only four
24 LED child nodes can be supported.
26 Required properties for the LED child node:
27 - reg : LED channel number (0..3)
[all …]
|
| H A D | leds-bcm6328.txt | 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.
[all …]
|
| H A D | leds-bcm6328.yaml | 24 BCM6328 LED controller has a HWDIS register, which controls whether a LED
27 is usually 1:1 for hardware to LED signals, but through the activity/link
29 explained later in brcm,link-signal-sources). Even if a LED is hardware
32 reason, hardware controlled LEDs aren't registered as LED class devices.
34 Each LED is represented as a sub-node of the brcm,bcm6328-leds device.
79 description: LED pin number (only LEDs 0 to 23 are valid).
83 description: Makes this LED hardware controlled.
92 where LED signals 0 to 3 may be muxed to LEDs 0 to 3, and signals 4 to
94 LED, an
[all...] |
| H A D | awinic,aw200xx.yaml | 7 title: AWINIC AW200XX LED
13 It is a matrix LED driver programmed via an I2C interface. Devices have
48 "^led@[0-9a-f]+$":
56 LED number
59 led-max-microamp:
62 Note that a driver will take the minimum of all LED limits
64 The maximum output current of each LED is calculated by the
69 where max-current-switch-number is determined by led configuration
70 and depends on how leds are physically connected to the led driver.
80 "^led
[all...] |
| H A D | leds-lp50xx.yaml | 7 title: LED driver for LP50XX RGB LED from Texas Instruments.
13 The LP50XX is multi-channel, I2C RGB LED Drivers that can group RGB LEDs into
14 a LED group or control them individually.
16 The difference in these RGB LED drivers is the number of supported RGB
47 description: LED supply.
56 '^multi-led@[0-9a-f]$':
66 This property denotes the LED module number(s) that is used on the
67 for the child node. The LED modules can either be used stand alone
77 "^led@[0-9a-f]+$":
104 led-controller@14 {
[all …]
|
| H A D | leds-cpcap.txt | 9 * "motorola,cpcap-led-mdl" (Main Display Lighting)
10 * "motorola,cpcap-led-kl" (Keyboard Lighting)
11 * "motorola,cpcap-led-adl" (Aux Display Lighting)
12 * "motorola,cpcap-led-red" (Red Triode)
13 * "motorola,cpcap-led-green" (Green Triode)
14 * "motorola,cpcap-led-blue" (Blue Triode)
15 * "motorola,cpcap-led-cf" (Camera Flash)
16 * "motorola,cpcap-led-bt" (Bluetooth)
17 * "motorola,cpcap-led-cp" (Camera Privacy LED)
19 - vdd-supply: A phandle to the regulator powering the LED
[all …]
|
| H A D | leds-lm3532.txt | 1 * Texas Instruments - lm3532 White LED driver with ambient light sensing
7 method allows for different LED currents in each current sink thus allowing
53 - reg : Indicates control bank the LED string is controlled by
54 - led-sources : see Documentation/devicetree/bindings/leds/common.txt
55 - ti,led-mode : Defines if the LED strings are manually controlled or
56 if the LED strings are controlled by the ALS.
57 0x00 - LED strings are I2C controlled via full scale
59 0x01 - LED strings are ALS controlled
61 Optional LED child properties:
65 - led-max-microamp : Defines the full scale current value for each control
[all …]
|
| H A D | leds-lgm.yaml | 7 title: Intel Lightning Mountain (LGM) SoC LED Serial Shift Output (SSO) Controller driver
43 led-controller:
58 "^led@[0-2]$":
64 description: Index of the LED.
68 led-gpios:
73 description: This property indicates Hardware driven/control LED.
77 description: This property indicates Enable LED blink by Hardware.
80 description: LED HW blink frequency.
84 description: The suspend state of LED can be retained.
88 description: Retain the state of the LED on shutdown.
[all …]
|
| H A D | issi,is31fl319x.yaml | 7 title: ISSI LED Controllers for IS31FL319{0,1,3,6,9}
13 The IS31FL319X are LED controllers with I2C interface.
57 "^led@[1-9]$":
64 description: Index of the LED.
68 led-max-microamp:
70 Note that a driver will take the lowest of all LED limits
75 equal to led-max-microamp.
97 "^led@[1-9]$":
99 led-max-microamp:
108 "^led@[1-9]$":
[all …]
|
| H A D | kinetic,ktd202x.yaml | 7 title: Kinetic KTD2026/7 RGB/White LED Driver
13 The KTD2026/7 is a RGB/White LED driver with I2C interface.
41 multi-led:
54 "^led@[0-3]$":
61 description: Index of the LED.
74 "^led@[0-3]$":
81 description: Index of the LED.
104 led-controller@30 {
113 led@0 {
119 led@1 {
[all …]
|
| /freebsd-src/sys/contrib/device-tree/src/arm/ti/omap/ |
| H A D | omap3-echo.dts | 151 multi-led@0 {
157 led@0 {
158 led-cur = /bits/ 8 <12>;
164 led@1 {
165 led-cur = /bits/ 8 <12>;
171 led@6 {
172 led-cur = /bits/ 8 <12>;
178 multi-led@1 {
184 led@2 {
185 led-cur = /bits/ 8 <12>;
[all …]
|
| H A D | am572x-idk-common.dtsi | 53 cpu0-led {
60 usr0-led {
66 heartbeat-led {
73 cpu1-led {
80 usr1-led {
86 mmc0-led {
97 red0-led {
103 green0-led {
109 blue0-led {
115 red1-led {
[all …]
|
| /freebsd-src/sys/contrib/device-tree/src/mips/mti/ |
| H A D | sead3.dts | 113 led@10.0 {
114 compatible = "register-bit-led";
119 led@10.1 {
120 compatible = "register-bit-led";
125 led@10.2 {
126 compatible = "register-bit-led";
131 led@10.3 {
132 compatible = "register-bit-led";
137 led@10.4 {
138 compatible = "register-bit-led";
[all …]
|
| /freebsd-src/sys/contrib/device-tree/src/arm/aspeed/ |
| H A D | aspeed-bmc-ibm-rainier.dts | 111 /* BMC Card fault LED at the back */
116 /* Enclosure ID LED at the back */
121 /* Enclosure fault LED at the back */
126 /* PCIE slot power LED */
371 led@0 {
379 led@1 {
453 led@0 {
461 led@1 {
490 led@0 {
498 led
[all...] |
| /freebsd-src/sys/contrib/device-tree/Bindings/pinctrl/ |
| H A D | marvell,armada-375-pinctrl.txt | 18 mpp2 2 gpio, dev(ad4), ptp(evreq), led(c0), audio(sdi)
19 mpp3 3 gpio, dev(ad5), ptp(trig), led(p3), audio(mclk)
22 mpp6 6 gpio, dev(ad0), led(p1), audio(lrclk)
23 mpp7 7 gpio, dev(ad1), ptp(clk), led(p2), audio(extclk)
26 mpp10 10 gpio, dram(vttctrl), led(c1), nand(re)
27 mpp11 11 gpio, dev(a0), led(c2), audio(sdo)
40 mpp24 24 gpio, led(p0), ge1(rxd0), sd(cmd), uart0(rts)
41 mpp25 25 gpio, led(p2), ge1(rxd1), sd(d0), uart0(cts)
44 mpp28 28 gpio, led(p3), ge1(txctl), sd(clk)
58 mpp42 42 gpio, spi1(cs2), led(c0)
[all …]
|
| /freebsd-src/sys/contrib/dev/iwlwifi/mvm/ |
| H A D | led.c | 30 IWL_WARN(mvm, "LED command failed: %d\n", err); in iwl_mvm_send_led_fw_cmd()
48 struct iwl_mvm *mvm = container_of(led_cdev, struct iwl_mvm, led); in iwl_led_brightness_set()
60 IWL_ERR(mvm, "Blink led mode not supported, used default\n"); in iwl_mvm_leds_init()
67 IWL_INFO(mvm, "Led disabled\n"); in iwl_mvm_leds_init()
73 mvm->led.name = kasprintf(GFP_KERNEL, "%s-led", in iwl_mvm_leds_init()
75 if (!mvm->led.name) in iwl_mvm_leds_init()
78 mvm->led.brightness_set = iwl_led_brightness_set; in iwl_mvm_leds_init()
79 mvm->led.max_brightness = 1; in iwl_mvm_leds_init()
82 mvm->led.default_trigger = in iwl_mvm_leds_init()
85 ret = led_classdev_register(mvm->trans->dev, &mvm->led); in iwl_mvm_leds_init()
[all …]
|
| /freebsd-src/sys/contrib/device-tree/src/mips/brcm/ |
| H A D | bcm63268-comtrend-vr-3032u.dts | 27 led@0 {
33 led@1 {
39 led@2 {
44 led@3 {
49 led@4 {
54 led@7 {
59 led@8 {
64 led@9 {
69 led@10 {
74 led@11 {
[all …]
|
| /freebsd-src/sys/contrib/device-tree/src/arm/st/ |
| H A D | stm32mp157c-lxa-tac-gen2.dts | 35 led-controller-1 {
38 multi-led {
43 led-red {
49 led-green {
55 led-blue {
63 led-controller-2 {
66 led-5 {
71 led-6 {
76 led-7 {
81 led
[all...] |