Searched +full:led +full:- +full:compatible (Results 1 – 25 of 116) sorted by relevance
12345
| /Documentation/devicetree/bindings/leds/ |
| D | register-bit-led.txt | 5 single LED. The register bit LEDs appear as children to the
6 syscon device, with the proper compatible string. For 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)
[all …]
|
| D | leds-pm8058.txt | 1 Qualcomm PM8058 LED driver
3 The Qualcomm PM8058 is a multi-functional device which contains
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
8 are more of a suggestion than a hard-wired usecase.
10 Hardware-wise the different LEDs support slightly different
12 do they support external triggers. They are just powerful LED
16 proper compatible string. For the PM8058 bindings see:
17 mfd/qcom-pm8xxx.txt.
[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-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-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.
25 compatible:
27 - national,lp5521
[all …]
|
| D | leds-spi-byte.txt | 1 * Single Byte SPI LED Device Driver.
4 - one LED is controlled by a single byte on MOSI
5 - the value of the byte gives the brightness between two values (lowest to
7 - no return value is necessary (no MISO signal)
10 therefore on the compatible string.
12 Depending on the compatible string some special functions (like hardware
15 The driver currently only supports one LED. The properties of the LED are
16 configured in a sub-node in the device node.
19 - compatible: should be one of
20 * "ubnt,acb-spi-led" microcontroller (SONiX 8F26E611LA) based device
[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
25 compatible:
[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.
17 compatible:
23 vcc-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.
18 compatible:
19 const: gpio-leds
[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 | rohm,bd71828-leds.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/rohm,bd71828-leds.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ROHM BD71828 Power Management Integrated Circuit LED driver
10 - Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
14 see Documentation/devicetree/bindings/mfd/rohm,bd71828-pmic.yaml.
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.
24 compatible:
[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 …]
|
| 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-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
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).
22 A discrete LED element connected to the device must be represented by a child
[all …]
|
| D | leds-powernv.txt | 2 -------------------------------------------------
5 - compatible : Should be "ibm,opal-v3-led".
6 - led-mode : Should be "lightpath" or "guidinglight".
9 form of a sub-node.
12 - led-types : Supported LED types (attention/identify/fault) provided
18 compatible = "ibm,opal-v3-led";
19 led-mode = "lightpath";
21 U78C9.001.RST0027-P1-C1 {
22 led-types = "identify", "fault";
|
| 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-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
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.
27 - reg : BCM6328 LED controller address and size.
[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-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-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-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/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/mfd/ |
| D | max77693.txt | 1 Maxim MAX77693 multi-function device
4 - PMIC,
5 - CHARGER,
6 - LED,
7 - MUIC,
8 - HAPTIC
14 - compatible : Must be "maxim,max77693".
15 - reg : Specifies the i2c slave address of PMIC block.
16 - interrupts : This i2c device has an IRQ line connected to the main SoC.
19 - regulators : The regulators of max77693 have to be instantiated under subnode
[all …]
|
| /Documentation/devicetree/bindings/iio/health/ |
| D | max30102.txt | 2 Maxim MAX30105 optical particle-sensing module
8 - compatible: must be "maxim,max30102" or "maxim,max30105"
9 - reg: the I2C address of the sensor
10 - interrupts: the sole interrupt generated by the device
12 Refer to interrupt-controller/interrupts.txt for generic
16 - maxim,red-led-current-microamp: configuration for red LED current
17 - maxim,ir-led-current-microamp: configuration for IR LED current
18 - maxim,green-led-current-microamp: configuration for green LED current
27 compatible = "maxim,max30102";
29 maxim,red-led-current-microamp = <7000>;
[all …]
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | led-backlight.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/leds/backlight/led-backlight.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: led-backlight bindings
10 - Lee Jones <lee.jones@linaro.org>
11 - Daniel Thompson <daniel.thompson@linaro.org>
12 - Jingoo Han <jingoohan1@gmail.com>
17 a LED driver.
20 compatible:
[all …]
|
12345