Searched +full:led +full:- +full:1 (Results 1 – 25 of 171) sorted by relevance
1234567
/Documentation/devicetree/bindings/leds/ |
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 | 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-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 - Dan Murphy <dmurphy@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 | 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 "mediatek,mt6323-led" 16 - address-cells : Must be 1 17 - size-cells : Must be 0 19 Each led is represented as a child node of the mediatek,mt6323-led that 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: [all …]
|
D | leds-bcm6328.txt | 7 as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or 10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware 13 BCM6328 LED controller has a HWDIS register, which controls whether a LED 15 with 0 meaning hardware control enabled and 1 hardware control disabled. This 16 is usually 1:1 for hardware to LED signals, but through the activity/link 18 explained later in brcm,link-signal-sources). Even if a LED is hardware 21 reason, hardware controlled LEDs aren't registered as LED class devices. 24 - compatible : should be "brcm,bcm6328-leds". 25 - #address-cells : must be 1. 26 - #size-cells : must be 0. [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. 21 maxItems: 1 23 vcc-supply: [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 13 1000:1 dimming ratio with programmable fade in and fade out settings. 16 - compatible : "ti,lm3532" 17 - reg : I2C slave address 18 - #address-cells : 1 19 - #size-cells : 0 [all …]
|
D | leds-lm3697.txt | 1 * Texas Instruments - LM3697 Highly Efficient White LED Driver 3 The LM3697 11-bit LED driver provides high- 4 performance backlight dimming for 1, 2, or 3 series 5 LED strings while delivering up to 90% efficiency. 10 - compatible: 12 - reg : I2C slave address 13 - #address-cells : 1 14 - #size-cells : 0 17 - enable-gpios : GPIO pin to enable/disable the device 18 - vled-supply : LED supply [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-is31fl319x.txt | 1 LEDs connected to is31fl319x LED controller chip 4 - compatible : Should be any of 10 "si-en,sn3199". 11 - #address-cells: Must be 1. 12 - #size-cells: Must be 0. 13 - reg: 0x64, 0x65, 0x66, or 0x67. 16 - audio-gain-db : audio gain selection for external analog modulation input. 17 Valid values: 0 - 21, step by 3 (rounded down) 19 - shutdown-gpios : Specifier of the GPIO connected to SDB pin of the chip. 21 Each led is represented as a sub-node of the issi,is31fl319x device. [all …]
|
D | leds-sc27xx-bltc.txt | 4 red LED, green LED and blue LED. Each LED can work at normal 8 - compatible: Should be "sprd,sc2731-bltc". 9 - #address-cells: Must be 1. 10 - #size-cells: Must be 0. 11 - reg: Specify the controller address. 14 - reg: Port this LED is connected to. 17 - function: See Documentation/devicetree/bindings/leds/common.txt. 18 - color: See Documentation/devicetree/bindings/leds/common.txt. 19 - label: See Documentation/devicetree/bindings/leds/common.txt (deprecated). 23 led-controller@200 { [all …]
|
D | leds-is31fl32xx.txt | 1 Binding for ISSI IS31FL32xx and Si-En SN32xx LED Drivers 3 The IS31FL32xx/SN32xx family of LED drivers are I2C devices with multiple 4 constant-current channels, each with independent 256-level PWM control. 5 Each LED is represented as a sub-node of the device. 8 - compatible: one of 13 si-en,sn3218 14 si-en,sn3216 15 - reg: I2C slave address 16 - address-cells : must be 1 17 - size-cells : must be 0 [all …]
|
D | leds-ktd2692.txt | 1 * Kinetic Technologies - KTD2692 Flash LED Driver 3 KTD2692 is the ideal power solution for high-power flash LEDs. 4 It uses ExpressWire single-wire programming for maximum flexibility. 6 The ExpressWire interface through CTRL pin can control LED on/off and 7 enable/disable the IC, Movie(max 1/3 of Flash current) / Flash mode current, 11 LED current will be ramped up to the flash-mode current level. 14 - compatible : Should be "kinetic,ktd2692". 15 - ctrl-gpios : Specifier of the GPIO connected to CTRL pin. 16 - aux-gpios : Specifier of the GPIO connected to AUX pin. 19 - vin-supply : "vin" LED supply (2.7V to 5.5V). [all …]
|
D | register-bit-led.txt | 5 single LED. The register bit LEDs appear as children to the 10 Each LED is represented as a sub-node of the syscon device. Each 11 node's name represents the name of the corresponding LED. 13 LED sub-node properties: 16 - compatible : must be "register-bit-led" 17 - offset : register offset to the register controlling this LED 18 - mask : bit mask for the bit controlling this LED in the register 22 - label : (optional) 24 - linux,default-trigger : (optional) 26 - default-state: (optional) The initial state of the LED [all …]
|
D | leds-cr0014114.txt | 1 Crane Merchandising System - cr0014114 LED driver 2 ------------------------------------------------- 4 This LED Board is widely used in vending machines produced 8 - compatible: "crane,cr0014114" 10 Property rules described in Documentation/devicetree/bindings/spi/spi-bus.txt 11 apply. In particular, "reg" and "spi-max-frequency" properties must be given. 13 LED sub-node properties: 14 - function : 16 - color : 18 - label : [all …]
|
D | leds-an30259a.txt | 1 * Panasonic AN30259A 3-channel LED driver 3 The AN30259A is a LED controller capable of driving three LEDs independently. It supports 7 - compatible: Must be "panasonic,an30259a". 8 - reg: I2C slave address. 9 - #address-cells: Must be 1. 10 - #size-cells: Must be 0. 12 Each LED is represented as a sub-node of the panasonic,an30259a node. 14 Required sub-node properties: 15 - reg: Pin that the LED is connected to. Must be 1, 2, or 3. 17 Optional sub-node properties: [all …]
|
D | leds-ns2.txt | 1 Binding for dual-GPIO LED found on Network Space v2 (and parents). 4 - compatible: "lacie,ns2-leds". 6 Each LED is represented as a sub-node of the ns2-leds device. 8 Required sub-node properties: 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 12 the corresponding cmd-gpio/slow-gpio values. All the GPIO values combinations 15 Optional sub-node properties: 16 - label: Name for this LED. If omitted, the label is taken from the node name. [all …]
|
D | leds-lm3601x.txt | 1 * Texas Instruments - lm3601x Single-LED Flash Driver 3 The LM3601X are ultra-small LED flash drivers that 7 - compatible : Can be one of the following 10 - reg : I2C slave address 11 - #address-cells : 1 12 - #size-cells : 0 15 - reg : 0 - Indicates a IR mode 16 1 - Indicates a Torch (white LED) mode 18 Required properties for flash LED child nodes: 20 - flash-max-microamp : Range from 11mA - 1.5A [all …]
|
D | leds-el15203000.txt | 1 Crane Merchandising System - EL15203000 LED driver 2 -------------------------------------------------- 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. 18 - cascade pattern 19 - inversed cascade pattern 20 - bounce pattern [all …]
|
/Documentation/leds/ |
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, than the trigger turns the LED on and than 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 | 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 …]
|
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 11 echoing "1" to a chosen port. 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 28 port may be handled by ohci-platform, ehci-platform and xhci-hcd. If there is 29 only one LED user will most likely want to assign ports from all 3 hubs. 32 This trigger can be activated from user space on led class devices as shown [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. [3] 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 [4], in "flash-leds" property 17 While Device tree allows referring to any node in the tree[1], in ACPI 19 mechanism on ACPI is not possible. A mechanism to refer to non-device ACPI nodes 23 combination of the LED driver device reference and an integer argument, 24 referring to the "reg" property of the relevant LED, is used to identify [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. 16 What: /sys/class/leds/<led>/link 19 Contact: linux-leds@vger.kernel.org 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. [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 …]
|
1234567