Searched +full:led +full:- +full:red (Results 1 – 25 of 38) sorted by relevance
12
| /Documentation/devicetree/bindings/leds/ |
| 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-bcm6358.txt | 5 which can either be controlled by software (exporting the 74x164 as spi-gpio.
10 - compatible : should be "brcm,bcm6358-leds".
11 - #address-cells : must be 1.
12 - #size-cells : must be 0.
13 - reg : BCM6358 LED controller address and size.
16 - brcm,clk-div : SCK signal divider. Possible values are 1, 2, 4 and 8.
18 - brcm,clk-dat-low : Boolean, makes clock and data signals active low.
21 Each LED is represented as a sub-node of the brcm,bcm6358-leds device.
23 LED sub-node required properties:
24 - reg : LED pin number (only LEDs 0 to 31 are valid).
[all …]
|
| D | leds-netxbig.txt | 5 - compatible: "lacie,netxbig-leds".
6 - gpio-ext: Phandle for the gpio-ext bus.
9 - timers: Timer array. Each timer entry is represented by three integers:
10 Mode (gpio-ext bus), delay_on and delay_off.
12 Each LED is represented as a sub-node of the netxbig-leds device.
14 Required sub-node properties:
15 - mode-addr: Mode register address on gpio-ext bus.
16 - mode-val: Mode to value mapping. Each entry is represented by two integers:
17 A mode and the corresponding value on the gpio-ext bus.
18 - bright-addr: Brightness register address on gpio-ext bus.
[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-pwm-multicolor.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-pwm-multicolor.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Multi-color LEDs connected to PWM
10 - Sven Schwermer <sven.schwermer@disruptive-technologies.com>
13 This driver combines several monochrome PWM LEDs into one multi-color
14 LED using the multicolor LED class.
18 const: pwm-leds-multicolor
20 multi-led:
[all …]
|
| D | sprd,sc2731-bltc.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/sprd,sc2731-bltc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Orson Zhai <orsonzhai@gmail.com>
11 - Baolin Wang <baolin.wang7@gmail.com>
12 - Chunyan Zhang <zhang.lyra@gmail.com>
16 red LED, green LED and blue LED. Each LED can work at normal PWM mode
21 const: sprd,sc2731-bltc
26 '#address-cells':
[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 …]
|
| D | nxp,pca953x.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: NXP PCA9532 LED Dimmer
10 - Riku Voipio <riku.voipio@iki.fi>
17 https://www.nxp.com/docs/en/data-sheet/PCA9532.pdf
22 - nxp,pca9530
23 - nxp,pca9531
24 - nxp,pca9532
25 - nxp,pca9533
[all …]
|
| D | leds-pca955x.txt | 1 * NXP - pca955x LED driver
3 The PCA955x family of chips are I2C LED blinkers whose pins not used
5 be input or output, and output pins can also be pulse-width controlled.
8 - compatible : should be one of :
14 - #address-cells: must be 1
15 - #size-cells: must be 0
16 - reg: I2C slave address. depends on the model.
19 - gpio-controller: allows pins to be used as GPIOs.
20 - #gpio-cells: must be 2.
21 - gpio-line-names: define the names of the GPIO lines
[all …]
|
| D | ti,tca6507.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TCA6507 LED and GPIO controller
10 - NeilBrown <neilb@suse.de>
13 The TCA6507 is a programmable LED controller connected via I2C that can drive
25 "#address-cells":
28 "#size-cells":
31 gpio-controller: true
33 "#gpio-cells":
[all …]
|
| D | nxp,pca963x.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: NXP PCA963x LED controllers
10 - Laurent Pinchart <laurent.pinchart@ideasonboard.com>
13 The NXP PCA963x are I2C-controlled LED drivers optimized for
14 Red/Green/Blue/Amber (RGBA) color mixing applications. Each LED is
19 - https://www.nxp.com/docs/en/data-sheet/PCA9632.pdf
20 - https://www.nxp.com/docs/en/data-sheet/PCA9633.pdf
21 - https://www.nxp.com/docs/en/data-sheet/PCA9634.pdf
[all …]
|
| D | leds-bcm6328.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-bcm6328.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Álvaro Fernández Rojas <noltari@gmail.com>
17 as spi-gpio. See
21 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
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
[all …]
|
| /Documentation/leds/ |
| D | leds-mlxcpld.rst | 5 Provide system LED support for the nex Mellanox systems:
10 -----------
14 - mlxcpld:fan1:green
15 - mlxcpld:fan1:red
16 - mlxcpld:fan2:green
17 - mlxcpld:fan2:red
18 - mlxcpld:fan3:green
19 - mlxcpld:fan3:red
20 - mlxcpld:fan4:green
21 - mlxcpld:fan4:red
[all …]
|
| D | leds-class-multicolor.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Multicolor LED handling under Linux
17 array. These files are children under the LED parent node created by the
18 led_class framework. The led_class framework is documented in led-class.rst
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.
34 root:/sys/class/leds/multicolor:status# ls -lR
35 -rw-r--r-- 1 root root 4096 Oct 19 16:16 brightness
36 -r--r--r-- 1 root root 4096 Oct 19 16:16 max_brightness
37 -r--r--r-- 1 root root 4096 Oct 19 16:16 multi_index
[all …]
|
| D | leds-blinkm.rst | 5 The leds-blinkm driver supports the devices of the BlinkM family.
7 They are RGB-LED modules driven by a (AT)tiny microcontroller and
10 daisy-chain up to 127 BlinkMs on an I2C bus.
16 The interface this driver provides is 3-fold:
18 a) LED multicolor class interface for use with triggers
23 blinkm-<i2c-bus-nr>-<i2c-device-nr>:rgb:indicator
25 $ ls -h /sys/class/leds/blinkm-1-9:rgb:indicator
40 b) LED class interface for use with triggers
45 blinkm-<i2c-bus-nr>-<i2c-device-nr>-<color>
47 $ ls -h /sys/class/leds/blinkm-6-*
[all …]
|
| D | leds-lp55xx.rst | 8 -----------
13 Create LED class devices for multiple output channels
14 Device attributes for user-space interface
15 Program memory for running LED patterns
28 control multi output LED channels such as led current, channel index.
32 For example, LP5521 has maximum 3 LED channels.
50 - Maximum number of channels
51 - Reset command, chip enable command
52 - Chip specific initialization
53 - Brightness control register access
[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 | leds-lp5521.rst | 5 * National Semiconductor LP5521 led driver chip
10 Contact: Samu Onkalo (samu.p.onkalo-at-nokia.com)
13 -----------
16 the led class control interface. Channels have generic names:
22 LP5521 has the internal program memory for running various LED patterns.
23 There are two ways to run LED patterns.
25 1) Legacy interface - enginex_mode and enginex_load
35 Example (start to blink the channel 2 led)::
46 2) Firmware interface - LP55xx common interface
48 For the details, please refer to 'firmware' section in leds-lp55xx.txt
[all …]
|
| /Documentation/devicetree/bindings/iio/health/ |
| D | maxim,max30102.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Maxim MAX30101/2 heart rate and pulse oximeter and MAX30105 particle-sensor
10 - Matt Ranostay <matt.ranostay@konsulko.com>
15 - enum:
16 - maxim,max30102
17 - maxim,max30105
18 - items:
19 - const: maxim,max30101
[all …]
|
| D | maxim,max30100.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matt Ranostay <matt.ranostay@konsulko.com>
23 maxim,led-current-microamp:
27 LED current whilst the engine is running. First indexed value is
28 the configuration for the RED LED, and second value is for the IR LED.
33 - compatible
34 - reg
35 - interrupts
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | mc13xxx.txt | 4 - compatible : Should be "fsl,mc13783" or "fsl,mc13892"
7 - fsl,mc13xxx-uses-adc : Indicate the ADC is being used
8 - fsl,mc13xxx-uses-codec : Indicate the Audio Codec is being used
9 - fsl,mc13xxx-uses-rtc : Indicate the RTC is being used
10 - fsl,mc13xxx-uses-touch : Indicate the touchscreen controller is being used
12 Sub-nodes:
13 - codec: Contain the Audio Codec node.
14 - adc-port: Contain PMIC SSI port number used for ADC.
15 - dac-port: Contain PMIC SSI port number used for DAC.
16 - leds : Contain the led nodes and initial register values in property
[all …]
|
| /Documentation/driver-api/gpio/ |
| D | board.rst | 14 -----------
20 <function>-gpios, where <function> is the function the driver will request
26 led-gpios = <&gpio 15 GPIO_ACTIVE_HIGH>, /* red */
30 power-gpios = <&gpio 1 GPIO_ACTIVE_LOW>;
33 Properties named <function>-gpio are also considered valid and old bindings use
38 "led" function, and GPIO 1 as the "power" GPIO::
40 struct gpio_desc *red, *green, *blue, *power;
42 red = gpiod_get_index(dev, "led", 0, GPIOD_OUT_HIGH);
43 green = gpiod_get_index(dev, "led", 1, GPIOD_OUT_HIGH);
44 blue = gpiod_get_index(dev, "led", 2, GPIOD_OUT_HIGH);
[all …]
|
| /Documentation/devicetree/bindings/auxdisplay/ |
| D | holtek,ht16k33.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: Holtek HT16K33 RAM mapping 16*8 LED controller with keyscan
10 - Robin van der Gracht <robin@protonic.nl>
13 - $ref: /schemas/input/matrix-keymap.yaml#
18 - items:
19 - enum:
20 - adafruit,3108 # 0.56" 4-Digit 7-Segment FeatherWing Display (Red)
21 - adafruit,3130 # 0.54" Quad Alphanumeric FeatherWing Display (Red)
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-chromeos-driver-cros-ec-lightbar | 1 What: /sys/class/chromeos/<ec-device-name>/lightbar/brightness
9 What: /sys/class/chromeos/<ec-device-name>/lightbar/interval_msec
26 What: /sys/class/chromeos/<ec-device-name>/lightbar/led_rgb
30 This allows you to control each LED segment. If the
38 indicating LED, RED, GREEN, BLUE. The LED number is 0 to 3
40 to the same value at once. The RED, GREEN, and BLUE
45 What: /sys/class/chromeos/<ec-device-name>/lightbar/program
51 What: /sys/class/chromeos/<ec-device-name>/lightbar/sequence
55 The Pixel lightbar has a number of built-in sequences
62 What: /sys/class/chromeos/<ec-device-name>/lightbar/userspace_control
[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 …]
|
12