Searched refs:LED (Results 1 – 25 of 341) sorted by relevance
12345678910>>...14
| /linux-6.1.9/drivers/leds/ |
| D | Kconfig | 10 bool "LED Support"
12 Say Y to enable Linux LED support. This allows control of supported
18 tristate "LED Class Support"
20 This option enables the LED sysfs class in /sys/class/leds. You'll
24 tristate "LED Flash Class Support"
27 This option enables the flash LED sysfs class in /sys/class/leds.
28 It wraps LED Class and adds flash LEDs specific sysfs attributes
30 for the flash related features of a LED device. It can be built
34 tristate "LED Multicolor Class Support"
37 This option enables the multicolor LED sysfs class in /sys/class/leds.
[all …]
|
| 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-6.1.9/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.
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
34 LED function. Use one of the LED_FUNCTION_* prefixed definitions
[all …]
|
| 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 LED active low.
87 description: Makes this LED hardware controlled.
96 where LED signals 0 to 3 may be muxed to LEDs 0 to 3, and signals 4 to
98 LED, and one LED can have more than one source signal.
[all …]
|
| 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
33 Properties for a single LED.
37 description: Index of the LED.
39 - 0 # LED output ISINK1
40 - 1 # LED output ISINK2
41 - 2 # LED output ISINK3
42 - 3 # LED output ISINKML
43 - 4 # LED output FLASH1
[all …]
|
| D | leds-lp55xx.yaml | 7 title: TI/National Semiconductor LP55xx and LP8501 LED Drivers
15 LED Drivers.
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
91 - 2 # LED output D3
92 - 3 # LED output D4
[all …]
|
| 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-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
28 For multicolor LED support this property should be defined as either
|
| 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-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.
|
| 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
|
| 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-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:
|
| 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-6.1.9/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
12 number of the LED output.
24 combination of the LED driver device reference and an integer argument,
25 referring to the "reg" property of the relevant LED, is used to identify
27 firmware and software, it uniquely identifies the LED driver outputs.
29 Under the LED driver device, The first hierarchical data extension package list
30 entry shall contain the string "led@" followed by the number of the LED,
31 followed by the referred object name. That object shall be named "LED" followed
32 by the number of the LED.
[all …]
|
| /linux-6.1.9/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:
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 …]
|
| 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
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
23 You can change the brightness value of a LED independently of the timer
41 LED Device Naming
[all …]
|
| 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 …]
|
| 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:
|
| 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 …]
|
| /linux-6.1.9/drivers/leds/flash/ |
| 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"
28 This option enables support for Kinetic KTD2692 LED flash connected
34 tristate "LED support for LM3601x Chips"
42 tristate "LED support for MAX77693 Flash"
52 tristate "LED Support for Mediatek MT6360 PMIC"
59 This option enables support for dual Flash LED drivers found on
61 Independent current sources supply for each flash LED support torch
[all …]
|
| /linux-6.1.9/drivers/leds/trigger/ |
| 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-6.1.9/Documentation/userspace-api/media/v4l/ |
| 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
48 LED flash may be used as torch in conjunction with another use case
61 Defines the mode of the flash LED, the high-power white LED attached
84 Defines the source of the flash LED strobe.
121 Intensity of the flash strobe when the flash LED is in flash mode
[all …]
|
| /linux-6.1.9/Documentation/ABI/testing/ |
| 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
|
| 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
|
12345678910>>...14