Searched +full:led +full:- (Results 1 – 25 of 284) sorted by relevance
12345678910>>...12
| /Documentation/devicetree/bindings/leds/ |
| D | common.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jacek Anaszewski <jacek.anaszewski@gmail.com> 11 - Pavel Machek <pavel@ucw.cz> 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 [all …]
|
| D | leds-mt6360.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/leds-mt6360.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: LED driver for MT6360 PMIC from MediaTek Integrated. 10 - Gene Chen <gene_chen@richtek.com> 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 20 const: mediatek,mt6360-led 22 "#address-cells": [all …]
|
| D | qcom,spmi-flash-led.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/qcom,spmi-flash-led.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Flash LED device inside Qualcomm Technologies, Inc. PMICs 10 - Fenglin Wu <quic_fenglinw@quicinc.com> 13 Flash LED controller is present inside some Qualcomm Technologies, Inc. PMICs. 14 The flash LED module can have different number of LED channels supported 24 - enum: 25 - qcom,pm6150l-flash-led [all …]
|
| D | leds-lp55xx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/leds-lp55xx.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: TI/National Semiconductor LP55xx and LP8501 LED Drivers 10 - Jacek Anaszewski <jacek.anaszewski@gmail.com> 11 - Pavel Machek <pavel@ucw.cz> 15 LED Drivers. 27 - national,lp5521 28 - national,lp5523 [all …]
|
| 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 5 PMIC controller that is being defined as one kind of Muti-Function Device (MFD) 15 - compatible : Must be one of 16 - "mediatek,mt6323-led" 17 - "mediatek,mt6331-led" 18 - "mediatek,mt6332-led" 19 - address-cells : Must be 1 20 - size-cells : Must be 0 22 Each led is represented as a child node of the mediatek,mt6323-led that [all …]
|
| D | leds-cpcap.txt | 2 ------------------------ 5 chip see Documentation/devicetree/bindings/mfd/motorola-cpcap.txt. 8 - compatible: should be one of 9 * "motorola,cpcap-led-mdl" (Main Display Lighting) 10 * "motorola,cpcap-led-kl" (Keyboard Lighting) 11 * "motorola,cpcap-led-adl" (Aux Display Lighting) 12 * "motorola,cpcap-led-red" (Red Triode) 13 * "motorola,cpcap-led-green" (Green Triode) 14 * "motorola,cpcap-led-blue" (Blue Triode) 15 * "motorola,cpcap-led-cf" (Camera Flash) [all …]
|
| D | leds-lp50xx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/leds-lp50xx.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: LED driver for LP50XX RGB LED from Texas Instruments. 10 - Andrew Davis <afd@ti.com> 13 The LP50XX is multi-channel, I2C RGB LED Drivers that can group RGB LEDs into 14 a LED group or control them individually. 16 The difference in these RGB LED drivers is the number of supported RGB 27 - ti,lp5009 [all …]
|
| D | awinic,aw200xx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: AWINIC AW200XX LED 10 - Martin Kurbanov <mmkurbanov@sberdevices.ru> 13 It is a matrix LED driver programmed via an I2C interface. Devices have 16 - AW20036 (3x12) 36 LEDs 17 - AW20054 (6x9) 54 LEDs 18 - AW20072 (6x12) 72 LEDs 19 - AW20108 (9x12) 108 LEDs [all …]
|
| D | qcom,pm8058-led.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/leds/qcom,pm8058-led.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm PM8058 PMIC LED 10 - Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> 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 15 because sometimes these LED drivers are used for wildly different things than 17 hard-wired usecase. [all …]
|
| D | leds-gpio.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only 3 --- 4 $id: http://devicetree.org/schemas/leds/leds-gpio.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jacek Anaszewski <jacek.anaszewski@gmail.com> 11 - Pavel Machek <pavel@ucw.cz> 14 Each LED is represented as a sub-node of the gpio-leds device. Each 15 node's name represents the name of the corresponding LED. 19 const: gpio-leds 22 # The first form is preferred, but fall back to just 'led' anywhere in the [all …]
|
| D | leds-lgm.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/leds-lgm.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Intel Lightning Mountain (LGM) SoC LED Serial Shift Output (SSO) Controller driver 10 - Zhu, Yi Xin <Yixin.zhu@intel.com> 11 - Amireddy Mallikarjuna reddy <mallikarjunax.reddy@intel.com> 15 const: intel,lgm-ssoled 23 clock-names: 25 - const: sso [all …]
|
| D | leds-lm3532.txt | 1 * Texas Instruments - lm3532 White LED driver with ambient light sensing 4 The LM3532 provides the 3 high-voltage, low-side current sinks. The device is 5 programmable over an I2C-compatible interface and has independent 7 method allows for different LED currents in each current sink thus allowing 11 each with 32 internal voltage setting resistors, 8-bit logarithmic and linear 16 - compatible : "ti,lm3532" 17 - reg : I2C slave address 18 - #address-cells : 1 19 - #size-cells : 0 22 - enable-gpios : gpio pin to enable (active high)/disable the device. [all …]
|
| D | leds-aw2013.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/leds-aw2013.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: AWINIC AW2013 3-channel LED Driver 10 - Nikita Travkin <nikitos.tr@gmail.com> 13 The AW2013 is a 3-channel LED driver with I2C interface. It can control 14 LED brightness with PWM output. 25 description: Open-drain, low active interrupt pin "INTN". 26 Used to report completion of operations (power up, LED breath effects). [all …]
|
| D | leds-lt3593.txt | 1 Bindings for Linear Technologies LT3593 LED controller 4 - compatible: Should be "lltc,lt3593". 5 - lltc,ctrl-gpios: A handle to the GPIO that is connected to the 'CTRL' 8 The hardware supports only one LED. The properties of this LED are 9 configured in a sub-node in the device node. 11 Optional sub-node properties: 12 - function: See Documentation/devicetree/bindings/leds/common.txt 13 - color: See Documentation/devicetree/bindings/leds/common.txt 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. [all …]
|
| /Documentation/ABI/testing/ |
| 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 13 Specifies the duration of the LED blink in milliseconds. 21 What: /sys/class/leds/<led>/link 24 Contact: linux-leds@vger.kernel.org 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. [all …]
|
| D | sysfs-class-led-flash | 1 What: /sys/class/leds/<led>/flash_brightness 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 11 /sys/class/leds/<led>/max_flash_brightness. 13 What: /sys/class/leds/<led>/max_flash_brightness 18 Maximum brightness level for this LED in the flash strobe mode, 21 What: /sys/class/leds/<led>/flash_timeout 28 of the strobe. The file is created only for the flash LED 31 What: /sys/class/leds/<led>/max_flash_timeout 36 Maximum flash timeout for this LED, in microseconds. [all …]
|
| D | sysfs-class-led | 1 What: /sys/class/leds/<led>/brightness 6 Set the brightness of the LED. 9 just be turned on for non-zero brightness settings. 15 each color LED intensity is set to. 17 The percentage is calculated for each grouped LED via 23 Documentation/leds/leds-class-multicolor.rst. 26 /sys/class/leds/<led>/max_brightness. 30 Writing non-zero to this file while trigger is active changes the 35 What: /sys/class/leds/<led>/max_brightness 40 Maximum brightness level for this LED, default is 255 (LED_FULL). [all …]
|
| D | sysfs-class-led-trigger-tty | 4 Contact: linux-leds@vger.kernel.org 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. [all …]
|
| /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: 16 (see Documentation/ABI/testing/sysfs-class-led-flash) 18 - flash_brightness 19 - max_flash_brightness [all …]
|
| 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 6 no clear trap points to put standard led-on and led-off settings. Using this 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 20 The trigger can be activated from user space on led class devices as shown 25 This adds sysfs attributes to the LED that are documented in: 26 Documentation/ABI/testing/sysfs-class-led-trigger-oneshot 28 Example use-case: network devices, initialization:: [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 9 brightness support so will just be turned on for non-zero brightness settings. 11 The class also introduces the optional concept of an LED trigger. A trigger 12 is a kernel based source of led events. Triggers can either be simple or 14 existing subsystems with minimal additional code. Examples are the disk-activity, 15 nand-disk and sharpsl-charge triggers. With led triggers disabled, the code 18 Complex triggers while available to all LEDs have LED specific [all …]
|
| 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 24 When an led class device driver registers itself, it can specify all leds 26 routine for the default trigger gets called. During registration of an 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 [all …]
|
| /Documentation/firmware-guide/acpi/dsd/ |
| D | leds.rst | 1 .. SPDX-License-Identifier: GPL-2.0 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 11 connected. [leds] The hierarchical data nodes are named "led@X", where X is the 12 number of the LED output. 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 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. [all …]
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | adp1653.txt | 1 * Analog Devices ADP1653 flash LED driver 5 - compatible: Must contain "adi,adp1653" 7 - reg: I2C slave address 9 - enable-gpios: Specifier of the GPIO connected to EN pin 11 There are two LED outputs available - flash and indicator. One LED is 14 Required properties of the LED child node: 15 - led-max-microamp : see Documentation/devicetree/bindings/leds/common.txt 17 Required properties of the flash LED child node: 19 - flash-max-microamp : see Documentation/devicetree/bindings/leds/common.txt 20 - flash-timeout-us : see Documentation/devicetree/bindings/leds/common.txt [all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | marvell,armada-375-pinctrl.txt | 3 Please refer to marvell,mvebu-pinctrl.txt in this directory for common binding 7 - compatible: "marvell,88f6720-pinctrl" 8 - reg: register specifier of MPP registers 18 mpp2 2 gpio, dev(ad4), ptp(evreq), led(c0), audio(sdi) 19 mpp3 3 gpio, dev(ad5), ptp(trig), led(p3), audio(mclk) 22 mpp6 6 gpio, dev(ad0), led(p1), audio(lrclk) 23 mpp7 7 gpio, dev(ad1), ptp(clk), led(p2), audio(extclk) 26 mpp10 10 gpio, dram(vttctrl), led(c1), nand(re) 27 mpp11 11 gpio, dev(a0), led(c2), audio(sdo) 40 mpp24 24 gpio, led(p0), ge1(rxd0), sd(cmd), uart0(rts) [all …]
|
12345678910>>...12