| /Documentation/devicetree/bindings/leds/ |
| 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 device binding.
25 led-sources:
27 List of device current outputs the LED is connected to. The outputs are
28 identified by the numbers that must be defined in the LED device binding
[all …]
|
| D | leds-lp55xx.yaml | 7 title: TI/National Semiconductor LP55xx and LP8501 LED Drivers
15 LED Drivers.
68 "(^led@[0-9a-f]$|led)":
72 led-cur:
75 Current setting at each LED channel (mA x10, 0 if LED is not connected)
81 description: Maximun current at each LED channel.
85 Output channel for the LED. This is zero based channel identifier and
87 reg value to output to LED output number
89 - 0 # LED output D1
90 - 1 # LED output D2
[all …]
|
| 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 …]
|
| 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 …]
|
| 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 …]
|
| 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
15 - compatible : Must be "mediatek,mt6323-led"
19 Each led is represented as a child node of the mediatek,mt6323-led that
20 describes the initial behavior for each LED physically and currently only four
21 LED child nodes can be supported.
23 Required properties for the LED child node:
24 - reg : LED channel number (0..3)
26 Optional properties for the LED child node:
39 compatible = "mediatek,mt6323-led";
[all …]
|
| 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]$':
65 This property denotes the LED module number(s) that is used on the
66 for the child node. The LED modules can either be used stand alone
70 "(^led-[0-9a-f]$|led)":
89 led-controller@14 {
[all …]
|
| D | leds-ktd2692.txt | 1 * Kinetic Technologies - KTD2692 Flash LED Driver
6 The ExpressWire interface through CTRL pin can control LED on/off and
11 LED current will be ramped up to the flash-mode current level.
19 - vin-supply : "vin" LED supply (2.7V to 5.5V).
22 A discrete LED element connected to the device must be represented by a child
25 Required properties for flash LED child nodes:
27 - led-max-microamp : Minimum Threshold for Timer protection
29 - flash-max-microamp : Flash LED maximum current
31 - flash-max-timeout-us : Flash LED maximum timeout.
33 Optional properties for flash LED child nodes:
[all …]
|
| D | leds-aw2013.yaml | 7 title: AWINIC AW2013 3-channel LED Driver
13 The AW2013 is a 3-channel LED driver with I2C interface. It can control
14 LED brightness with PWM output.
33 "^led@[0-2]$":
39 description: Index of the LED.
60 led-controller@45 {
68 led@0 {
70 led-max-microamp = <5000>;
75 led@1 {
77 led-max-microamp = <5000>;
[all …]
|
| D | leds-gpio.yaml | 14 Each LED is represented as a sub-node of the gpio-leds device. Each
15 node's name represents the name of the corresponding LED.
22 # The first form is preferred, but fall back to just 'led' anywhere in the
24 "(^led-[0-9a-f]$|led)":
35 The suspend state can be retained.Such as charge-led gpio.
40 Retain the state of the LED on shutdown. Useful in BMC systems, for
57 led-0 {
63 led-1 {
65 /* Keep LED on if BIOS detected hardware fault */
73 led-0 {
[all …]
|
| 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 …]
|
| 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 …]
|
| D | leds-sc27xx-bltc.txt | 4 red LED, green LED and blue LED. Each LED can work at normal
14 - reg: Port this LED is connected to.
23 led-controller@200 {
29 led@0 {
34 led@1 {
39 led@2 {
|
| D | leds-lt3593.txt | 1 Bindings for Linear Technologies LT3593 LED controller
8 The hardware supports only one LED. The properties of this LED are
14 - label: A label for the LED. If none is given, the LED will be
16 - linux,default-trigger: The default trigger for the LED.
18 - default-state: The initial state of the LED.
28 led-controller {
32 led {
|
| D | leds-spi-byte.txt | 1 * Single Byte SPI LED Device Driver.
4 - one LED is controlled by a single byte on MOSI
15 The driver currently only supports one LED. The properties of the LED are
20 * "ubnt,acb-spi-led" microcontroller (SONiX 8F26E611LA) based device
26 LED sub-node properties:
35 led-controller@0 {
36 compatible = "ubnt,acb-spi-led";
40 led {
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-led-flash | 1 What: /sys/class/leds/<led>/flash_brightness
6 Set the brightness of this LED in the flash strobe mode, in
7 microamperes. The file is created only for the flash LED devices
11 /sys/class/leds/<led>/max_flash_brightness.
13 What: /sys/class/leds/<led>/max_flash_brightness
18 Maximum brightness level for this LED in the flash strobe mode,
21 What: /sys/class/leds/<led>/flash_timeout
28 of the strobe. The file is created only for the flash LED
31 What: /sys/class/leds/<led>/max_flash_timeout
36 Maximum flash timeout for this LED, in microseconds.
[all …]
|
| D | sysfs-class-led | 1 What: /sys/class/leds/<led>/brightness
6 Set the brightness of the LED.
15 each color LED intensity is set to.
17 The percentage is calculated for each grouped LED via
26 /sys/class/leds/<led>/max_brightness.
35 What: /sys/class/leds/<led>/max_brightness
40 Maximum brightness level for this LED, default is 255 (LED_FULL).
42 If the LED does not support different brightness levels, this
45 What: /sys/class/leds/<led>/brightness_hw_changed
49 Last hardware set brightness level for this LED. Some LEDs
[all …]
|
| D | sysfs-class-led-trigger-netdev | 1 What: /sys/class/leds/<led>/device_name
8 What: /sys/class/leds/<led>/interval
13 Specifies the duration of the LED blink in milliseconds.
16 What: /sys/class/leds/<led>/link
23 If set to 0 (default), the LED's normal state is off.
25 If set to 1, the LED's normal state reflects the link state
27 Setting this value also immediately changes the LED state.
30 What: /sys/class/leds/<led>/tx
37 If set to 0 (default), the LED will not blink on transmission.
39 If set to 1, the LED will blink for the milliseconds specified
[all …]
|
| /Documentation/leds/ |
| D | leds-class-flash.rst | 2 Flash LED handling under Linux
5 Some LED devices provide two modes - torch and flash. In the LED subsystem
6 those modes are supported by LED class (see Documentation/leds/leds-class.rst)
7 and LED Flash class respectively. The torch mode related features are enabled
12 must be defined in the kernel config. A LED Flash class driver must be
13 registered in the LED subsystem with led_classdev_flash_register function.
15 Following sysfs attributes are exposed for controlling flash LED devices:
16 (see Documentation/ABI/testing/sysfs-class-led-flash)
29 A LED subsystem driver can be controlled also from the level of VideoForLinux2
39 of_node of the LED, may be NULL if the same as device's
[all …]
|
| D | ledtrig-oneshot.rst | 2 One-shot LED Trigger
5 This is a LED trigger useful for signaling the user of an event where there are
6 no clear trap points to put standard led-on and led-off settings. Using this
8 happened, than the trigger turns the LED on and than keeps it off for a
16 A one-shot LED only stays in a constant state when there are no events. An
17 additional "invert" property specifies if the LED has to stay off (normal) or
20 The trigger can be activated from user space on led class devices as shown
25 This adds sysfs attributes to the LED that are documented in:
26 Documentation/ABI/testing/sysfs-class-led-trigger-oneshot
30 echo oneshot > trigger # set trigger for this led
[all …]
|
| D | leds-class.rst | 2 LED handling under Linux
5 In its simplest form, the LED class just allows control of LEDs from
7 LED is defined in max_brightness file. The brightness file will set the brightness
8 of the LED (taking a value 0-max_brightness). Most LEDs don't have hardware
11 The class also introduces the optional concept of an LED trigger. A trigger
12 is a kernel based source of led events. Triggers can either be simple or
15 nand-disk and sharpsl-charge triggers. With led triggers disabled, the code
18 Complex triggers while available to all LEDs have LED specific
19 parameters and work on a per LED basis. The timer trigger is an example.
20 The timer trigger will periodically change the LED brightness between
[all …]
|
| D | ledtrig-transient.rst | 2 LED Transient Trigger
8 to be off. The delay_on value specifies the time period an LED should stay
9 in on state, followed by a delay_off value that specifies how long the LED
24 When an led class device driver registers itself, it can specify all leds
26 routine for the default trigger gets called. During registration of an led
27 class device, the LED state does not change.
30 trigger will be called, and LED state is changed to LED_OFF.
32 Driver suspend changes the LED state to LED_OFF and resume doesn't change
34 suspend and resume actions and the currently enabled trigger. LED state
37 being able to actually change the LED state. Once driver is resumed, triggers
[all …]
|
| /Documentation/firmware-guide/acpi/dsd/ |
| D | leds.rst | 9 device node, the LED driver chip. The "reg" property in the LED specific nodes
10 tells the numerical ID of each individual LED output to which the LEDs are
11 connected. [3] The hierarchical data nodes are named "led@X", where X is the
12 number of the LED output.
23 combination of the LED driver device reference and an integer argument,
24 referring to the "reg" property of the relevant LED, is used to identify
26 firmware and software, it uniquely identifies the LED driver outputs.
28 Under the LED driver device, The first hierarchical data extension package list
29 entry shall contain the string "led@" followed by the number of the LED,
30 followed by the referred object name. That object shall be named "LED" followed
[all …]
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | adp1653.txt | 1 * Analog Devices ADP1653 flash LED driver
11 There are two LED outputs available - flash and indicator. One LED is
14 Required properties of the LED child node:
15 - led-max-microamp : see Documentation/devicetree/bindings/leds/common.txt
17 Required properties of the flash LED child node:
21 - led-max-microamp : see Documentation/devicetree/bindings/leds/common.txt
25 adp1653: led-controller@30 {
33 led-max-microamp = <50000>;
36 led-max-microamp = <17500>;
|
| /Documentation/devicetree/bindings/pinctrl/ |
| 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 …]
|