| /linux/Documentation/firmware-guide/acpi/dsd/ |
| H A 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
12 number of the LED output.
19 combination of the LED driver device reference and an integer argument,
20 referring to the "reg" property of the relevant LED, is used to identify
22 firmware and software, it uniquely identifies the LED driver outputs.
24 Under the LED driver device, The first hierarchical data extension package list
25 entry shall contain the string "led@" followed by the number of the LED,
26 followed by the referred object name. That object shall be named "LED" followed
27 by the number of the LED.
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-led-trigger-netdev | 13 Specifies the duration of the LED blink in milliseconds.
28 If set to 0 (default), the LED's normal state is off.
30 If set to 1, the LED's normal state reflects the link state
32 Setting this value also immediately changes the LED state.
42 If set to 0 (default), the LED will not blink on transmission.
44 If set to 1, the LED will blink for the milliseconds specified
57 If set to 0 (default), the LED will not blink on reception.
59 If set to 1, the LED will blink for the milliseconds specified
70 Communicate whether the LED trigger modes are offloaded to
73 If 0, the LED is using software fallback to blink.
[all …]
|
| H A D | sysfs-class-led-trigger-tty | 13 If set to 0, the LED will not blink on reception.
14 If set to 1 (default), the LED will blink on reception.
21 If set to 0, the LED will not blink on transmission.
22 If set to 1 (default), the LED will blink on transmission.
30 If the line state is detected, the LED is switched on.
31 If set to 0 (default), the LED will not evaluate CTS.
32 If set to 1, the LED will evaluate CTS.
40 If the line state is detected, the LED is switched on.
41 If set to 0 (default), the LED will not evaluate DSR.
42 If set to 1, the LED will evaluate DSR.
[all …]
|
| H A 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.
59 flash controller voltage to the flash LED
72 current in the LED power
77 a short or open circuit condition on the indicator LED
80 LED has been below the minimum limit specific to
88 the temperature of the LED has exceeded
|
| H A 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.
|
| H A D | sysfs-platform-oxp | 20 Some OneXPlayer devices (e.g., X1 series) feature a little LED
21 nested in the Turbo button. This LED is illuminated when the
23 is engaged, this LED is left dangling to its last state. This
24 attribute allows userspace to control the LED state manually
25 (either with 1 or 0). Only a subset of devices contain this LED.
|
| /linux/Documentation/leds/ |
| H A 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:
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
41 LED flash class device to wrap
[all …]
|
| H A D | ledtrig-usbport.rst | 2 USB port LED trigger
5 This LED trigger can be used for signalling to the user a presence of USB device
6 in a given port. It simply turns on LED when device appears and turns it off
14 LED.
18 1) Device with single USB LED and few physical ports
21 In such a case LED will be turned on as long as there is at least one connected
29 only one LED user will most likely want to assign ports from all 3 hubs.
37 This adds sysfs attributes to the LED that are documented in:
|
| H A 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
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
40 LED state changes are controlled using brightness which is a common led
47 registration, the LED state does not change, unless there is another trigger
[all …]
|
| H A D | leds-el15203000.rst | 10 Specify a hardware pattern for the EL15203000 LED.
30 Cascade mode for Pipe LED::
58 Inverted cascade mode for Pipe LED::
86 Bounce mode for Pipe LED::
114 Inverted bounce mode for Pipe LED::
|
| H A D | leds-mt6370-rgb.rst | 4 The device for Mediatek MT6370 RGB LED
10 The MT6370 integrates a four-channel RGB LED driver, designed to provide a
11 variety of lighting effect for mobile device applications. The RGB LED devices
12 includes a smart LED string controller and it can drive 3 channels of LEDs with
13 a sink current up to 24mA and a CHG_VIN power good indicator LED with sink
16 can increase or decrease the brightness of the RGB LED via an I2C interface.
24 Specify a hardware breath pattern for a MT6370 RGB LED.
|
| H A 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
8 happened, then the trigger turns the LED on and then 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
25 This adds sysfs attributes to the LED that are documented in:
|
| H A D | uleds.rst | 13 create a new LED class device, open /dev/uleds and write a uleds_user_dev
22 A new LED class device will be created with the name given. The name can be
23 any valid sysfs device node name, but consider using the LED class naming
31 The LED class device will be removed when the open file handle to /dev/uleds
34 Multiple LED class devices are created by opening additional file handles to
|
| H A D | leds-mlxcpld.rst | 5 Provide system LED support for the nex Mellanox systems:
56 - [0,0,0,0] = LED OFF
101 - [0,0,0,0] = LED OFF
109 Color mask for uid LED:
112 - [0,0,0,0] = LED OFF
|
| /linux/drivers/leds/trigger/ |
| H A D | Kconfig | 3 bool "LED Trigger support"
13 tristate "LED Timer Trigger"
16 via sysfs. Some LED hardware can be programmed to start
17 blinking the LED without any further software interaction.
23 tristate "LED One-shot Trigger"
28 or on dense events, where this blinks the LED at constant rate if
36 bool "LED Disk Trigger"
43 bool "LED MTD (NAND/NOR) Trigger"
50 tristate "LED Heartbeat Trigger"
58 tristate "LED backlight Trigger"
[all …]
|
| /linux/drivers/leds/ |
| H A D | TODO | 9 * Review atomicity requirements in LED subsystem
16 * LED names are still a mess
19 userland. Nudge authors into creating common LED names for common
22 ? Perhaps check for known LED names during boot, and warn if there are
27 The number of drivers is getting big, and driver for on/off LED on a
28 i/o port is really quite different from camera flash LED, which is
29 really different from driver for RGB color LED that can run its own
35 Green-Magenta-Ultraviolet LED, but so far all the LEDs we support are
38 Multicolor is not a good fit for RGB LED. It does not really know
39 about LED color. In particular, there's no way to make LED "white".
[all …]
|
| /linux/Documentation/devicetree/bindings/leds/ |
| H A 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.
|
| H A 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.
|
| H A D | leds-el15203000.txt | 1 Crane Merchandising System - EL15203000 LED driver
4 This LED Board (aka RED LEDs board) is widely used in
9 Vending area LED encoded with symbol 'V' (hex code 0x56).
12 Screen light tube LED which surrounds vending machine screen and
15 Water Pipe LED encoded with symbol 'P' (hex code 0x50) and
16 actually consists of 5 LEDs that exposed by protocol like one LED.
31 Optional LED sub-node properties:
|
| H A D | leds-trigger-pattern.txt | 1 * Pattern format for LED pattern trigger
4 The LED is expected to traverse the series and each brightness value for the
19 It will make the LED go gradually from zero-intensity to max (255) intensity in
22 LED brightness
31 2. To make the LED go instantly from one brightness value to another, we should
39 It will make the LED stay off for one second, then stay at max brightness for
42 LED brightness
|
| H A 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
26 LED sub-node properties:
|
| 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
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:
|
| H A D | leds-lm3601x.txt | 1 * Texas Instruments - lm3601x Single-LED Flash Driver
3 The LM3601X are ultra-small LED flash drivers that
16 1 - Indicates a Torch (white LED) mode
18 Required properties for flash LED child nodes:
|
| /linux/drivers/platform/x86/intel/atomisp2/ |
| H A D | Kconfig | 10 tristate "Intel AtomISP v2 camera LED driver"
17 camera's have a LED which is controlled through a GPIO.
19 Some of these devices have a firmware issue where the LED gets turned
20 on at boot. This driver will turn the LED off at boot and also allows
21 controlling the LED (repurposing it) through the sysfs LED interface.
23 Which GPIO is attached to the LED is usually not described in the
|
| /linux/Documentation/networking/device_drivers/fddi/ |
| H A D | skfp.rst | 143 The functionality of the LED's on the FDDI network adapters was
145 LED works as a ring operational indicator. An active yellow LED
146 indicates that the ring is down. The green LED on the adapter now
147 works as a link indicator where an active GREEN LED indicates that
151 yellow LED was off while the green LED(s) showed the connection
152 status of the adapter. During a ring down the green LED was off and
153 the yellow LED was on.
209 - New SMT module included, changing LED functionality
|