Searched refs:LED (Results 1 – 25 of 240) sorted by relevance
12345678910
| /Linux-v4.19/Documentation/devicetree/bindings/leds/ |
| D | common.txt | 3 LED and flash LED devices provide the same basic functionality as current
4 regulators, but extended with LED and flash LED specific features like
7 Many LED devices expose more than one current output that can be connected
8 to one or more discrete LED component. Since the arrangement of connections
9 can influence the way of the LED device initialization, the LED components
10 have to be tightly coupled with the LED device binding. They are represented
11 by child nodes of the parent LED device binding.
14 - led-sources : List of device current outputs the LED is connected to. The
16 in the LED device binding documentation.
17 - label : The label for this LED. If omitted, the label is taken from the node
[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-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:
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:
|
| 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
12 - label: A label for the LED. If none is given, the LED will be
14 - linux,default-trigger: The default trigger for the LED.
16 - default-state: The initial state of the LED.
|
| D | leds-ns2.txt | 1 Binding for dual-GPIO LED found on Network Space v2 (and parents).
6 Each LED is represented as a sub-node of the ns2-leds device.
9 - cmd-gpio: Command LED GPIO. See OF device-tree GPIO specification.
10 - slow-gpio: Slow LED GPIO. See OF device-tree GPIO specification.
11 - modes-map: A mapping between LED modes (off, on or SATA activity blinking) and
16 - label: Name for this LED. If omitted, the label is taken from the node name.
17 - linux,default-trigger: Trigger assigned to the LED.
|
| 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
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:
|
| 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:
27 "qcom,pm8058-keypad-led" (for the "keypad" LED at 0x48)
|
| D | leds-pwm.txt | 1 LED connected to PWM
6 Each LED is represented as a sub-node of the pwm-leds device. Each
7 node's name represents the name of the corresponding LED.
9 LED sub-node properties:
15 - max-brightness : Maximum brightness possible for the LED
16 - active-low : (optional) For PWMs where the LED is wired to supply
32 /* provides one PWM (id 0 for Charing indicator LED) */
|
| 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.
|
| D | leds-gpio.txt | 6 Each LED is represented as a sub-node of the gpio-leds device. Each
7 node's name represents the name of the corresponding LED.
9 LED sub-node properties:
10 - gpios : Should specify the LED's GPIO, see "gpios property" in
17 - default-state: (optional) The initial state of the LED.
21 - retain-state-shutdown: (optional) Retain the state of the LED on shutdown.
41 /* Keep LED on if BIOS detected hardware fault */
|
| 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:
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
|
| D | leds-is31fl32xx.txt | 1 Binding for ISSI IS31FL32xx and Si-En SN32xx LED Drivers
3 The IS31FL32xx/SN32xx family of LED drivers are I2C devices with multiple
5 Each LED is represented as a sub-node of the device.
19 LED sub-node properties:
20 - reg : LED channel number (1..N)
|
| D | leds-lm3692x.txt | 1 * Texas Instruments - LM3692x Highly Efficient White LED Driver
4 white-LED driver designed for LCD display backlighting.
7 LED strings it supports. The LM36922 supports two strings while the LM36923
20 - vled-supply : LED supply
23 - reg : 0 - Will enable all LED sync paths
|
| /Linux-v4.19/drivers/leds/ |
| D | Kconfig | 9 bool "LED Support"
11 Say Y to enable Linux LED support. This allows control of supported
17 tristate "LED Class Support"
23 tristate "LED Flash Class Support"
27 It wrapps LED Class and adds flash LEDs specific sysfs attributes
29 for the flash related features of a LED device. It can be built
33 bool "LED Class brightness_hw_changed attribute support"
41 comment "LED drivers"
44 tristate "LED Support for Marvell 88PM860x PMIC"
48 This option enables support for on-chip LED drivers found on Marvell
[all …]
|
| /Linux-v4.19/Documentation/leds/ |
| D | leds-class-flash.txt | 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.txt)
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:
28 A LED subsystem driver can be controlled also from the level of VideoForLinux2
35 - of_node : of_node of the LED, may be NULL if the same as device's
36 - fled_cdev : LED flash class device to wrap
[all …]
|
| D | leds-class.txt | 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
18 Complex triggers whilst 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
23 You can change the brightness value of a LED independently of the timer
41 LED Device Naming
[all …]
|
| D | ledtrig-usbport.txt | 1 USB port LED trigger
4 This LED trigger can be used for signalling to the user a presence of USB device
5 in a given port. It simply turns on LED when device appears and turns it off
13 LED. This can be useful in two cases:
15 1) Device with single USB LED and few physical ports
17 In such a case LED will be turned on as long as there is at least one connected
24 only one LED user will most likely want to assign ports from all 3 hubs.
32 This adds sysfs attributes to the LED that are documented in:
|
| D | ledtrig-transient.txt | 1 LED Transient Trigger
7 to be off. The delay_on value specifies the time period an LED should stay
8 in on state, followed by a delay_off value that specifies how long the LED
32 class device, the LED state does not change.
35 trigger will be called, and LED state is changed to LED_OFF.
37 Driver suspend changes the LED state to LED_OFF and resume doesn't change
39 suspend and resume actions and the currently enabled trigger. LED state
42 being able to actually change the LED state. Once driver is resumed, triggers
45 LED state changes are controlled using brightness which is a common led
52 registration, the LED state does not change, unless there is another trigger
[all …]
|
| D | 00-INDEX | 4 - Driver for BlinkM LED-devices.
6 - documents LED handling under Linux.
8 - documents flash LED handling under Linux.
26 - One-shot LED trigger for both sporadic and dense events.
28 - LED Transient Trigger, one shot timer activation.
|
| /Linux-v4.19/drivers/leds/trigger/ |
| D | Kconfig | 2 bool "LED Trigger support"
12 tristate "LED Timer Trigger"
15 via sysfs. Some LED hardware can be programmed to start
16 blinking the LED without any further software interaction.
22 tristate "LED One-shot Trigger"
27 or on dense events, where this blinks the LED at constant rate if
35 bool "LED Disk Trigger"
42 bool "LED MTD (NAND/NOR) Trigger"
49 tristate "LED Heartbeat Trigger"
57 tristate "LED backlight Trigger"
[all …]
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-class-led-trigger-netdev | 13 Specifies the duration of the LED blink in milliseconds.
22 If set to 0 (default), the LED's normal state is off.
23 If set to 1, the LED's normal state reflects the link state
25 Setting this value also immediately changes the LED state.
33 If set to 0 (default), the LED will not blink on transmission.
34 If set to 1, the LED will blink for the milliseconds specified
43 If set to 0 (default), the LED will not blink on reception.
44 If set to 1, the LED will blink for the milliseconds specified
|
| D | sysfs-class-led-flash | 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
18 Maximum brightness level for this LED in the flash strobe mode,
28 of the strobe. The file is created only for the flash LED
36 Maximum flash timeout for this LED, in microseconds.
58 * led-over-voltage - flash controller voltage to the flash LED
67 * led-power-supply-over-current - current in the LED power
71 a short or open circuit condition on the indicator LED
73 LED has been below the minimum limit specific to
79 * led-over-temperature - the temperature of the LED has exceeded
|
| D | sysfs-class-led | 6 Set the brightness of the LED. Most LEDs don't
21 Maximum brightness level for this LED, default is 255 (LED_FULL).
23 If the LED does not support different brightness levels, this
30 Last hardware set brightness level for this LED. Some LEDs
48 Set the trigger for this LED. A trigger is a kernel based source
49 of LED events.
60 Invert the LED on/off state. This parameter is specific to
62 it is useful when driving a LED which is intended to indicate
|
| D | sysfs-class-led-trigger-oneshot | 6 Specifies for how many milliseconds the LED has to stay at
15 Specifies for how many milliseconds the LED has to stay at
25 delay_on ms, then blink off for delay_off ms, leaving the LED
27 blink on for delay_on ms, leaving the LED normally on.
28 Setting this value also immediately changes the LED state.
|
| /Linux-v4.19/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:
17 Required properties of the flash LED child node:
|
12345678910
