| /linux/drivers/leds/ |
| A D | Kconfig | 10 bool "LED Support"
67 LED driver.
102 LED driver.
213 white LED.
261 LED.
359 tristate "LED Support for TI LP3952 2 channel LED driver"
395 tristate "LED Support for N.S. LP5521 LED driver chip"
416 tristate "LED Support for TI LP5562 LED driver chip"
426 tristate "LED Support for TI LP8501 LED driver chip"
570 tristate "LED driver for BD2802 RGB LED"
[all …]
|
| 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
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
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".
41 Userspace is interested in knowing "this LED can produce arbitrary
58 an utility to perform LED control?
[all …]
|
| /linux/Documentation/devicetree/bindings/leds/ |
| 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
20 can influence the way of the LED device initialization, the LED components
22 by child nodes of the parent LED device binding.
64 The initial state of the LED. If the LED is already on or off and the
79 the LED.
90 # LED indicates disk activity
95 # LED flashes at a fixed, configurable rate
147 In many cases LED can be related to more than one device (e.g. one USB LED
154 # Required properties for flash LED child nodes:
[all …]
|
| A D | leds-bcm6328.txt | 13 BCM6328 LED controller has a HWDIS register, which controls whether a LED
43 LED sub-node required properties:
46 LED sub-node optional properties:
63 4 to 7. A signal can be muxed to more than one LED, and one LED can
69 4 to 7. A signal can be muxed to more than one LED, and one LED can
219 /* EPHY0 link routed to EPHY0 LED */
225 /* EPHY1 link routed to EPHY1 LED */
231 /* EPHY2 link routed to EPHY2 LED */
237 /* EPHY3 link routed to EPHY3 LED */
293 /* EPHY3 link routed to EPHY0 LED */
[all …]
|
| A D | leds-lp55xx.yaml | 15 LED Drivers.
75 Current setting at each LED channel (mA x10, 0 if LED is not connected)
89 - 0 # LED output D1
90 - 1 # LED output D2
91 - 2 # LED output D3
92 - 3 # LED output D4
93 - 4 # LED output D5
94 - 5 # LED output D6
95 - 6 # LED output D7
96 - 7 # LED output D8
[all …]
|
| A 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:
|
| 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.
|
| 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
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:
|
| 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:
27 "qcom,pm8058-keypad-led" (for the "keypad" LED at 0x48)
|
| A D | leds-class-multicolor.yaml | 7 title: Common properties for the multicolor LED class.
14 either integrated multi-color LED elements (like RGB, RGBW, RGBWA-UV
15 etc.) or standalone LEDs, to achieve logically grouped multi-color LED
17 monochrome LED bindings.
19 LED class. Common LED nodes and properties are inherited from the common.yaml
29 For multicolor LED support this property should be defined as either
|
| 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.
|
| A D | rohm,bd71828-leds.yaml | 7 title: ROHM BD71828 Power Management Integrated Circuit LED driver
16 The LED controller is represented as a sub-node of the PMIC node on the device
19 The device has two LED outputs referred as GRNLED and AMBLED in data-sheet.
31 Properties for a single LED.
36 description: LED identification string
43 Purpose of LED as defined in dt-bindings/leds/common.h
47 LED colour as defined in dt-bindings/leds/common.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:
|
| 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
|
| /linux/Documentation/firmware-guide/acpi/dsd/ |
| 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.
26 firmware and software, it uniquely identifies the LED driver outputs.
31 by the number of the LED.
40 Device (LED)
76 Package () { ^LED, "led@0", ^LED, "led@1" },
85 LED LED driver device
86 LED0 First LED
87 LED1 Second LED
[all …]
|
| /linux/Documentation/leds/ |
| 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
12 must be defined in the kernel config. A LED Flash class driver must be
39 of_node of the LED, may be NULL if the same as device's
41 LED flash class device to wrap
43 LED flash class device representing indicator LED associated with
49 defines the source of the flash LED strobe -
57 LED current scale.
64 bitmask of flash faults that the LED flash class
68 constraints for the LED in TORCH mode
[all …]
|
| A D | leds-class.rst | 2 LED handling under Linux
5 In its simplest form, the LED class just allows control of LEDs from
18 Complex triggers while available to all LEDs have LED specific
20 The timer trigger will periodically change the LED brightness between
41 LED Device Naming
73 automatically by the LED core upon LED class device registration.
86 Examples of proper LED names:
122 LED subsystem core exposes following API for setting brightness:
135 LED registration API
154 support this feature, a LED driver can optionally implement the
[all …]
|
| A D | leds-class-multicolor.rst | 4 Multicolor LED handling under Linux
17 array. These files are children under the LED parent node created by the
21 Each colored LED will be indexed under the multi_* files. The order of the
30 order for the color LED intensities to be updated.
42 The brightness level for each LED is calculated based on the color LED
50 for each LED that are necessary to achieve a certain color output from a
51 multicolor LED group.
68 The user can control the brightness of that multicolor LED group by writing the
70 may want to dim the LED color group to half. The user would write a value of
71 128 to the global brightness file then the values written to each LED will be
[all …]
|
| A D | ledtrig-transient.rst | 2 LED Transient Trigger
27 class device, the LED state does not change.
30 trigger will be called, and LED state is changed to LED_OFF.
48 active, in which case LED state changes to LED_OFF.
50 During trigger unregistration, LED state gets changed to LED_OFF.
57 state, the LED state changes to LED_OFF.
105 Please note that current LED state is not checked prior to
108 default states it defines for the LED in its brightness_set()
110 interfaces to control the LED state.
156 - Use of LED by user space app as activity indicator.
[all …]
|
| 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:
|
| /linux/drivers/leds/flash/ |
| A D | Kconfig | 6 tristate "LED support for the AAT1290"
15 tristate "AS3645A and LM3555 LED flash controllers support"
19 Enable LED flash class support for AS3645A LED flash
24 tristate "LED support for Kinetic KTD2692 flash LED controller"
34 tristate "LED support for LM3601x Chips"
42 tristate "LED support for MAX77693 Flash"
52 tristate "LED support for RT4505 flashlight controller"
57 This option enables support for the RT4505 flash LED controller.
63 tristate "LED support for Richtek RT8515 flash/torch LED"
74 tristate "LED support for the SGM3140"
[all …]
|
| /linux/drivers/leds/trigger/ |
| A D | Kconfig | 3 bool "LED Trigger support"
13 tristate "LED Timer Trigger"
23 tristate "LED One-shot Trigger"
36 bool "LED Disk Trigger"
50 tristate "LED Heartbeat Trigger"
66 bool "LED CPU Trigger"
76 tristate "LED activity Trigger"
84 tristate "LED GPIO Trigger"
119 bool "LED Panic Trigger"
128 tristate "LED Netdev Trigger"
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| A D | ext-ctrls-flash.rst | 13 The interface can support both LED and xenon flash devices. As of
23 Unsynchronised LED flash (software strobe)
26 Unsynchronised LED flash is controlled directly by the host as the
34 Synchronised LED flash (hardware strobe)
37 The synchronised LED flash is pre-programmed by the host (power and
45 LED flash as torch
61 Defines the mode of the flash LED, the high-power white LED attached
84 Defines the source of the flash LED strobe.
126 Intensity of the flash LED in torch mode
132 Intensity of the indicator LED. The indicator LED may be fully
[all …]
|
| /linux/Documentation/ABI/testing/ |
| A D | sysfs-class-led-trigger-netdev | 13 Specifies the duration of the LED blink in milliseconds.
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.
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
49 If set to 0 (default), the LED will not blink on reception.
51 If set to 1, the LED will blink for the milliseconds specified
|
| A D | sysfs-class-led | 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
40 Maximum brightness level for this LED, default is 255 (LED_FULL).
42 If the LED does not support different brightness levels, this
49 Last hardware set brightness level for this LED. Some LEDs
67 Set the trigger for this LED. A trigger is a kernel based source
68 of LED events.
80 Invert the LED on/off state. This parameter is specific to
82 it is useful when driving a LED which is intended to indicate
|