Searched full:leds (Results 1 – 25 of 215) sorted by relevance
123456789
| /Documentation/leds/ |
| D | index.rst | 4 LEDs title 10 leds-class 11 leds-class-flash 12 leds-class-multicolor 19 leds-blinkm 20 leds-cht-wcove 21 leds-el15203000 22 leds-lm3556 23 leds-lp3944 24 leds-lp5521 [all …]
|
| D | leds-lm3556.rst | 26 LM3556 Flash can be controlled through /sys/class/leds/flash/brightness file 35 #echo 0 > /sys/class/leds/flash/brightness 39 #echo 1 > /sys/class/leds/flash/brightness 45 #echo 16 > /sys/class/leds/flash/brightness 54 LM3556 torch can be controlled through /sys/class/leds/torch/brightness file. 62 #echo 0 > /sys/class/leds/torch/brightness 66 #echo 1 > /sys/class/leds/torch/brightness 72 #echo 8 > /sys/class/leds/torch/brightness 77 Indicator pattern can be set through /sys/class/leds/indicator/pattern file, 90 #echo 0 > /sys/class/leds/indicator/pattern [all …]
|
| D | well-known-leds.txt | 5 directories in /sys/class/leds. It would be nice if userland would 17 Notice there's a list of functions in include/dt-bindings/leds/common.h . 21 Game controllers may feature LEDs to indicate a player number. This is commonly 23 The "player LEDs" are then programmed with a pattern to indicate a particular 24 player. For example, a game controller with 4 LEDs, may be programmed with "x---" 26 Input drivers can utilize the LED class to expose the individual player LEDs 40 Set of common keyboard LEDs, going back to PC AT or so. 57 LEDs on notebook body, indicating that sound input / output is muted. 69 Good: "platform:*:charging" (allwinner sun50i, leds-cht-wcove) 83 * Ethernet LEDs [all …]
|
| D | leds-class.rst | 5 In its simplest form, the LED class just allows control of LEDs from 6 userspace. LEDs appear in /sys/class/leds/. The maximum brightness of the 8 of the LED (taking a value 0-max_brightness). Most LEDs don't have hardware 18 Complex triggers while available to all LEDs have LED specific 22 be specified via /sys/class/leds/<device>/delay_{on,off} in milliseconds. 28 is chosen (via /sys/class/leds/<device>/trigger). Trigger specific 29 parameters can appear in /sys/class/leds/<device> once a given trigger is 36 The underlying design philosophy is simplicity. LEDs are simple devices 53 retrieved using get_led_device_info.sh script from tools/leds; generally 54 this section is expected mostly for LEDs that are somehow associated with [all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-hid-srws1 | 1 What: /sys/class/leds/SRWS1::<serial>::RPM1 2 What: /sys/class/leds/SRWS1::<serial>::RPM2 3 What: /sys/class/leds/SRWS1::<serial>::RPM3 4 What: /sys/class/leds/SRWS1::<serial>::RPM4 5 What: /sys/class/leds/SRWS1::<serial>::RPM5 6 What: /sys/class/leds/SRWS1::<serial>::RPM6 7 What: /sys/class/leds/SRWS1::<serial>::RPM7 8 What: /sys/class/leds/SRWS1::<serial>::RPM8 9 What: /sys/class/leds/SRWS1::<serial>::RPM9 10 What: /sys/class/leds/SRWS1::<serial>::RPM10 [all …]
|
| D | sysfs-class-led-trigger-netdev | 1 What: /sys/class/leds/<led>/device_name 4 Contact: linux-leds@vger.kernel.org 8 What: /sys/class/leds/<led>/interval 11 Contact: linux-leds@vger.kernel.org 21 What: /sys/class/leds/<led>/link 24 Contact: linux-leds@vger.kernel.org 35 What: /sys/class/leds/<led>/tx 38 Contact: linux-leds@vger.kernel.org 50 What: /sys/class/leds/<led>/rx 53 Contact: linux-leds@vger.kernel.org [all …]
|
| D | sysfs-class-led | 1 What: /sys/class/leds/<led>/brightness 8 Most LEDs don't have hardware brightness support, so will 13 For multicolor LEDs, writing to this file will update all 14 LEDs within the group to a calculated percentage of what 23 Documentation/leds/leds-class-multicolor.rst. 26 /sys/class/leds/<led>/max_brightness. 35 What: /sys/class/leds/<led>/max_brightness 45 What: /sys/class/leds/<led>/brightness_hw_changed 49 Last hardware set brightness level for this LED. Some LEDs 50 may be changed autonomously by hardware/firmware. Only LEDs [all …]
|
| D | sysfs-class-led-multicolor | 2 What: /sys/class/leds/<led>/multi_index 12 Documentation/leds/leds-class-multicolor.rst. 14 What: /sys/class/leds/<led>/multi_intensity 21 not exceed /sys/class/leds/<led>/max_brightness. 24 Documentation/leds/leds-class-multicolor.rst.
|
| D | sysfs-class-led-trigger-oneshot | 1 What: /sys/class/leds/<led>/delay_on 4 Contact: linux-leds@vger.kernel.org 10 What: /sys/class/leds/<led>/delay_off 13 Contact: linux-leds@vger.kernel.org 19 What: /sys/class/leds/<led>/invert 22 Contact: linux-leds@vger.kernel.org 30 What: /sys/class/leds/<led>/shot 33 Contact: linux-leds@vger.kernel.org
|
| D | sysfs-class-led-trigger-pattern | 1 What: /sys/class/leds/<led>/pattern 13 Documentation/devicetree/bindings/leds/leds-trigger-pattern.txt 15 What: /sys/class/leds/<led>/hr_pattern 22 Unlike the /sys/class/leds/<led>/pattern, this attribute runs 25 What: /sys/class/leds/<led>/hw_pattern 37 file at Documentation/leds/. 39 What: /sys/class/leds/<led>/repeat 49 It should be noticed that some leds, like EL15203000 may
|
| D | sysfs-class-leds-gt683r | 1 What: /sys/class/leds/<led>/gt683r/mode 6 Set the mode of LEDs. You should notice that changing the mode 16 Normal: LEDs are fully on when enabled 17 Audio: LEDs brightness depends on sound level 18 Breathing: LEDs brightness varies at human breathing rate
|
| D | sysfs-class-led-trigger-tty | 1 What: /sys/class/leds/<tty_led>/ttyname 4 Contact: linux-leds@vger.kernel.org 8 What: /sys/class/leds/<tty_led>/rx 16 What: /sys/class/leds/<tty_led>/tx 24 What: /sys/class/leds/<tty_led>/cts 34 What: /sys/class/leds/<tty_led>/dsr 44 What: /sys/class/leds/<tty_led>/dcd 54 What: /sys/class/leds/<tty_led>/rng
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-bcm63138.yaml | 4 $id: http://devicetree.org/schemas/leds/leds-bcm63138.yaml# 7 title: Broadcom's BCM63138 LEDs controller 13 This LEDs controller was first used on BCM63138 and later reused on BCM4908, 16 It supports up to 32 LEDs that can be connected parallelly or serially. It 19 Binding serially connected LEDs isn't documented yet. 26 - brcm,bcm4908-leds 27 - brcm,bcm6848-leds 28 - brcm,bcm6858-leds 29 - brcm,bcm63148-leds 30 - brcm,bcm63381-leds [all …]
|
| D | leds-group-multicolor.yaml | 4 $id: http://devicetree.org/schemas/leds/leds-group-multicolor.yaml# 7 title: Multi-color LED built with monochromatic LEDs 13 This driver combines several monochromatic LEDs into one multi-color 18 const: leds-group-multicolor 20 leds: 22 An aray of monochromatic leds 26 - leds 29 - $ref: leds-class-multicolor.yaml# 36 #include <dt-bindings/leds/common.h> 38 monochromatic-leds { [all …]
|
| D | cznic,turris-omnia-leds.yaml | 4 $id: http://devicetree.org/schemas/leds/cznic,turris-omnia-leds.yaml# 7 title: CZ.NIC's Turris Omnia LEDs driver 13 This module adds support for the RGB LEDs found on the front panel of the 14 Turris Omnia router. There are 12 RGB LEDs that are controlled by a 20 const: cznic,turris-omnia-leds 35 $ref: leds-class-multicolor.yaml# 41 supports RGB LEDs. 48 This property identifies one of the LEDs on the front panel of the 59 #include <dt-bindings/leds/common.h> 66 compatible = "cznic,turris-omnia-leds"; [all …]
|
| D | leds-bcm6328.yaml | 4 $id: http://devicetree.org/schemas/leds/leds-bcm6328.yaml# 7 title: LEDs connected to Broadcom BCM6328 controller 14 In these SoCs it's possible to control LEDs both as GPIOs or by hardware. 15 However, on some devices there are Serial LEDs (LEDs connected to a 74x164 20 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and 21 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware 28 registers you have some limited control over rerouting the LEDs (as 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. 38 const: brcm,bcm6328-leds [all …]
|
| D | leds-gpio.yaml | 4 $id: http://devicetree.org/schemas/leds/leds-gpio.yaml# 7 title: LEDs connected to GPIO lines 14 Each LED is represented as a sub-node of the gpio-leds device. Each 19 const: gpio-leds 53 #include <dt-bindings/leds/common.h> 55 leds { 56 compatible = "gpio-leds"; 72 compatible = "gpio-leds";
|
| D | leds-pwm-multicolor.yaml | 4 $id: http://devicetree.org/schemas/leds/leds-pwm-multicolor.yaml# 7 title: Multi-color LEDs connected to PWM 13 This driver combines several monochrome PWM LEDs into one multi-color 18 const: pwm-leds-multicolor 22 $ref: leds-class-multicolor.yaml# 59 #include <dt-bindings/leds/common.h> 62 compatible = "pwm-leds-multicolor";
|
| D | leds-pwm.yaml | 4 $id: http://devicetree.org/schemas/leds/leds-pwm.yaml# 7 title: LEDs connected to PWM 13 Each LED is represented as a sub-node of the pwm-leds device. Each 18 const: pwm-leds 46 #include <dt-bindings/leds/common.h> 49 compatible = "pwm-leds";
|
| D | qcom,pm8058-led.yaml | 4 $id: http://devicetree.org/schemas/leds/qcom,pm8058-led.yaml# 13 The Qualcomm PM8058 contains an LED block for up to six LEDs:: three normal 14 LEDs, two "flash" LEDs and one "keypad backlight" LED. The names are quoted 19 Hardware-wise the different LEDs support slightly different output currents. 20 The "flash" LEDs do not need to charge nor do they support external triggers. 44 #include <dt-bindings/leds/common.h>
|
| D | leds-bcm6358.txt | 1 LEDs connected to Broadcom BCM6358 controller 4 In these SoCs there are Serial LEDs (LEDs connected to a 74x164 controller), 10 - compatible : should be "brcm,bcm6358-leds". 21 Each LED is represented as a sub-node of the brcm,bcm6358-leds device. 24 - reg : LED pin number (only LEDs 0 to 31 are valid). 27 - label : see Documentation/devicetree/bindings/leds/common.txt 29 Documentation/devicetree/bindings/leds/common.txt 31 Documentation/devicetree/bindings/leds/common.txt 36 compatible = "brcm,bcm6358-leds"; 65 compatible = "brcm,bcm6358-leds";
|
| D | leds-ns2.txt | 4 - compatible: "lacie,ns2-leds". 6 Each LED is represented as a sub-node of the ns2-leds device. 21 #include <dt-bindings/leds/leds-ns2.h> 23 ns2-leds { 24 compatible = "lacie,ns2-leds";
|
| D | leds-el15203000.txt | 4 This LED Board (aka RED LEDs board) is widely used in 6 The board manages 3 LEDs and supports predefined blinking patterns 7 for specific leds. 16 actually consists of 5 LEDs that exposed by protocol like one LED. 33 see Documentation/devicetree/bindings/leds/common.txt 35 see Documentation/devicetree/bindings/leds/common.txt 40 #include <dt-bindings/leds/common.h>
|
| /Documentation/firmware-guide/acpi/dsd/ |
| D | leds.rst | 5 Describing and referring to LEDs in ACPI 8 Individual LEDs are described by hierarchical data extension [5] nodes under the 10 tells the numerical ID of each individual LED output to which the LEDs are 11 connected. [leds] The hierarchical data nodes are named "led@X", where X is the 14 Referring to LEDs in Device tree is documented in [video-interfaces], in 15 "flash-leds" property documentation. In short, LEDs are directly referred to by 21 individual LEDs. The value of the "reg" property is a contract between the 32 An ASL example of a camera sensor device and a LED driver device for two LEDs is 33 show below. Objects not relevant for LEDs or the references to them have been 71 "flash-leds", [all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | qca,qca808x.yaml | 13 QCA808X PHYs can have up to 3 LEDs attached. 14 All 3 LEDs are disabled by default. 15 2 LEDs have dedicated pins with the 3rd LED having the 16 double function of Interrupt LEDs/GPIO or additional LED. 32 #include <dt-bindings/leds/common.h> 42 leds {
|
123456789