| /linux/Documentation/leds/ |
| H A 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
9 brightness support so will just be turned on for non-zero brightness settings.
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
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
[all …]
|
| H A D | well-known-leds.txt | 1 -*- org -*-
5 directories in /sys/class/leds. It would be nice if userland would
10 use one of the "good" names from this list, and you should extend the
14 wants to use particular feature, you should probe for good name, first,
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---"
25 to indicate player 1, "-x--" to indicate player 2 etcetera where "x" means on.
26 Input drivers can utilize the LED class to expose the individual player LEDs
[all …]
|
| H A D | leds-lp5523.rst | 9 Contact: Samu Onkalo (samu.p.onkalo-at-nokia.com)
12 -----------
13 LP5523 can drive up to 9 channels. Leds can be controlled directly via
15 The name of each channel is configurable in the platform data - name and label.
20 To make specific channel name, then use 'name' platform data.
22 - /sys/class/leds/R1 (name: 'R1')
23 - /sys/class/leds/B1 (name: 'B1')
25 b) Use the 'label' with no 'name' field
27 For one device name with channel number, then use 'label'.
28 - /sys/class/leds/RGB:channelN (label: 'RGB', N: 0 ~ 8)
[all …]
|
| H A D | leds-blinkm.rst | 2 Leds BlinkM driver
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>
[all …]
|
| H A D | leds-qcom-lpg.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 -----------
14 To facilitate the various use cases, the LPG channels can be exposed as
15 individual LEDs, grouped together as RGB LEDs or otherwise be accessed as PWM
25 range within the table to use, the rate and if the pattern should repeat.
30 /sys/class/leds/<led>/hw_pattern
31 --------------------------------
35 The pattern is a series of brightness and hold-time pairs, with the hold-time
39 transitions expected by the leds-trigger-pattern format, each entry in the
40 pattern must be followed a zero-length entry of the same brightness.
[all …]
|
| /linux/drivers/leds/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
19 LEDs from both userspace and optionally, by kernel events (triggers).
26 This option enables the LED sysfs class in /sys/class/leds. You'll
27 need this to do anything useful with LEDs. If unsure, say Y.
33 This option enables the flash LED sysfs class in /sys/class/leds.
34 It wraps LED Class and adds flash LEDs specific sysfs attributes
43 This option enables the multicolor LED sysfs class in /sys/class/leds.
46 for multicolor LEDs that are grouped together. This class is not
47 intended for single color LEDs. It can be built as a module.
54 for LED sysfs class devices under /sys/class/leds.
[all …]
|
| H A D | TODO | 1 -*- org -*-
3 * On/off LEDs should have max_brightness of 1
12 semantics is sometimes non-intuitive. (For example blink callback may
18 No two LEDs have same name, so the names are probably unusable for the
23 LEDs not on the list?
32 * Figure out what to do with RGB leds
35 Green-Magenta-Ultraviolet LED, but so far all the LEDs we support are
36 RGB, and not even RGB-White or RGB-Yellow variants emerged.
42 color", which not all multicolor LEDs can.
44 Proposal: let's add "rgb" to led_colors in drivers/leds/led-core.c,
[all …]
|
| H A D | leds-turris-omnia.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * CZ.NIC's Turris Omnia LEDs driver
9 #include <linux/led-class-multicolor.h>
13 #include <linux/turris-omnia-mcu-interface.h>
22 * struct omnia_led - per-LED part of driver private data structure
23 * @mc_cdev: multi-color LED class device
24 * @subled_info: per-channel information
25 * @cached_channels: cached values of per-channel brightness that was sent to the MCU
41 * struct omnia_leds - driver private data structure
47 * @leds: flexible array of per-LED data
[all …]
|
| H A D | leds-pca9532.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * pca9532.c - 16-bit Led dimmer
14 #include <linux/leds.h>
18 #include <linux/leds-pca9532.h>
43 struct pca9532_led leds[16]; member
108 .name = "leds-pca953x",
116 /* We have two pwm/blinkers, but 16 possible leds to drive. Additionally,
119 * leds that are not ON/OFF.
126 for (i = 0; i < data->chip_info->num_leds; i++) { in pca9532_calcpwm()
127 if (data->leds[i].type == PCA9532_TYPE_LED && in pca9532_calcpwm()
[all …]
|
| H A D | leds-blinkm.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * leds-blinkm.c
4 * (c) Jan-Simon Möller (dl9pf@gmx.de)
17 #include <linux/leds.h>
19 #include <linux/led-class-multicolor.h>
24 /* Addresses to scan - BlinkM is on 0x09 by default*/
30 /* Contains structs for both the color-separated sysfs classes, and the new multicolor class */
53 /* next values to use for transfer */
57 /* internal use */
69 u8 fade_speed; /* fade speed 1 - 255 */
[all …]
|
| H A D | leds-pca955x.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright 2007-2008 Extreme Engineering Solutions, Inc.
5 * Author: Nate Case <ncase@xes-inc.com>
11 * Device Description 7-bit slave address
12 * ------ ----------- -------------------
13 * PCA9550 2-bit driver 0x60 .. 0x61
14 * PCA9551 8-bit driver 0x60 .. 0x67
15 * PCA9552 16-bit driver 0x60 .. 0x67
16 * PCA9553/01 4-bit driver 0x62
17 * PCA9553/02 4-bit driver 0x63
[all …]
|
| H A D | leds-tca6507.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * leds-tca6507
9 * blink or double-blink.
12 * out-only (pull-up resistor required) or as an LED with variable
13 * brightness and hardware-assisted blinking.
21 * with separate time for rise, on, fall, off and second-off. Thus if
22 * 3 or more different non-trivial rates are required, software must
25 * support double-blink so 'second-off' always matches 'off'.
42 * delays in the ranges: 56-72, 112-144, 168-216, 224-27504,
43 * 28560-36720.
[all …]
|
| /linux/drivers/net/wireless/ath/carl9170/ |
| H A D | led.c | 25 * Copyright (c) 2007-2008 Atheros Communications, Inc.
27 * Permission to use, copy, modify, and/or distribute this software for any
35 * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
37 * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
52 /* disable LEDs */ in carl9170_led_init()
76 mutex_lock(&ar->mutex); in carl9170_led_update()
78 if (ar->leds[i].registered) { in carl9170_led_update()
79 if (ar->leds[i].last_state || in carl9170_led_update()
80 ar->leds[i].toggled) { in carl9170_led_update()
82 if (ar->leds[i].toggled) in carl9170_led_update()
[all …]
|
| /linux/include/linux/platform_data/ |
| H A D | adp8860.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
6 * Copyright 2009-2010 Analog Devices Inc.
12 #include <linux/leds.h>
21 * LEDs subdevice platform data
103 u8 bl_fade_in; /* Backlight Fade-In Timer */
104 u8 bl_fade_out; /* Backlight Fade-Out Timer */
105 u8 bl_fade_law; /* fade-on/fade-off transfer characteristic */
110 u8 l1_daylight_max; /* use BL_CUR_mA(I) 0 <= I <= 30 mA */
111 u8 l1_daylight_dim; /* typ = 0, use BL_CUR_mA(I) 0 <= I <= 30 mA */
112 u8 l2_office_max; /* use BL_CUR_mA(I) 0 <= I <= 30 mA */
[all …]
|
| H A D | adp8870.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
6 * Copyright 2009-2010 Analog Devices Inc.
18 * LEDs subdevice platform data
111 u8 bl_fade_in; /* Backlight Fade-In Timer */
112 u8 bl_fade_out; /* Backlight Fade-Out Timer */
113 u8 bl_fade_law; /* fade-on/fade-off transfer characteristic */
118 u8 l1_daylight_max; /* use BL_CUR_mA(I) 0 <= I <= 30 mA */
119 u8 l1_daylight_dim; /* typ = 0, use BL_CUR_mA(I) 0 <= I <= 30 mA */
120 u8 l2_bright_max; /* use BL_CUR_mA(I) 0 <= I <= 30 mA */
121 u8 l2_bright_dim; /* typ = 0, use BL_CUR_mA(I) 0 <= I <= 30 mA */
[all …]
|
| /linux/include/linux/ |
| H A D | leds-regulator.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * leds-regulator.h - platform data structure for regulator driven LEDs.
12 * Use "vled" as supply id when declaring the regulator consumer:
15 * { .dev_name = "leds-regulator.0", .supply = "vled" },
18 * If you have several regulator driven LEDs, you can append a numerical id to
19 * .dev_name as done above, and use the same id when declaring the platform
27 * .name = "leds-regulator",
35 #include <linux/leds.h>
|
| /linux/Documentation/devicetree/bindings/leds/ |
| H A D | common.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/leds/common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Common leds properties
10 - Jacek Anaszewski <jacek.anaszewski@gmail.com>
11 - Pavel Machek <pavel@ucw.cz>
25 led-sources:
30 $ref: /schemas/types.yaml#/definitions/uint32-array
34 LED function. Use one of the LED_FUNCTION_* prefixed definitions
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-led | 1 What: /sys/class/leds/<led>/brightness
8 Most LEDs don't have hardware brightness support, so will
9 just be turned on for non-zero brightness settings.
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.
30 Writing non-zero to this file while trigger is active changes the
31 top brightness trigger is going to use.
35 What: /sys/class/leds/<led>/max_brightness
[all …]
|
| H A D | sysfs-class-led-driver-lm3533 | 1 What: /sys/class/leds/<led>/als_channel
6 Set the ALS output channel to use as input in
7 ALS-current-control mode (1, 2), where:
14 What: /sys/class/leds/<led>/als_en
19 Enable ALS-current-control mode (0, 1).
21 What: /sys/class/leds/<led>/falltime
22 What: /sys/class/leds/<led>/risetime
40 What: /sys/class/leds/<led>/id
47 What: /sys/class/leds/<led>/linear
52 Set the brightness-mapping mode (0, 1), where:
[all …]
|
| /linux/arch/arm/boot/dts/marvell/ |
| H A D | mvebu-linkstation-gpio-simple.dtsi | 2 * Device Tree common file for gpio-{keys,leds} on Buffalo Linkstation
7 * This file is dual-licensed: you can use it either under the terms
27 * restriction, including without limitation the rights to use,
42 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
46 #include <dt-bindings/input/input.h>
50 compatible = "gpio-keys";
51 pinctrl-0 = <&pmx_power_switch>;
52 pinctrl-names = "default";
54 power-on-switch {
55 label = "Power-on Switch";
[all …]
|
| H A D | orion5x-lswsgl.dts | 3 * Copyright (C) 2014 Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
4 * Based on the board file arch/arm/mach-orion5x/lsmini-setup.c,
7 * This file is dual-licensed: you can use it either under the terms
27 * restriction, including without limitation the rights to use,
42 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
46 /dts-v1/;
48 #include <dt-bindings/gpio/gpio.h>
49 #include <dt-bindings/input/input.h>
50 #include <dt-bindings/interrupt-controller/irq.h>
51 #include "orion5x-mv88f5182.dtsi"
[all …]
|
| H A D | orion5x-linkstation-lschl.dts | 2 * Device Tree file for Buffalo Linkstation LS-CHLv3
5 * Copyright (C) 2015-2017
8 * This file is dual-licensed: you can use it either under the terms
28 * restriction, including without limitation the rights to use,
43 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
47 /dts-v1/;
49 #include "orion5x-linkstation.dtsi"
50 #include "mvebu-linkstation-gpio-simple.dtsi"
51 #include "mvebu-linkstation-fan.dtsi"
52 #include <dt-bindings/gpio/gpio.h>
[all …]
|
| /linux/drivers/leds/trigger/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
6 This option enables trigger support for the leds class.
7 These triggers allow kernel events to drive the LEDs and can
15 This allows LEDs to be controlled by a programmable timer
18 For more details read Documentation/leds/leds-class.rst.
23 tristate "LED One-shot Trigger"
25 This allows LEDs to blink in one-shot pulses with parameters
31 It also shows how to use the led_blink_set_oneshot() function.
39 This allows LEDs to be controlled by disk activity.
46 This allows LEDs to be controlled by MTD activity.
[all …]
|
| /linux/drivers/leds/blink/ |
| H A D | leds-bcm63138.c | 1 // SPDX-License-Identifier: GPL-2.0-only
9 #include <linux/leds.h>
20 #define BCM63138_LED_MASK ((1 << BCM63138_LED_BITS) - 1) /* 0xf */
40 #define BCM63138_POWER_LUT_BASE0 0x34 /* -> b0 */
59 struct bcm63138_leds *leds; member
69 static void bcm63138_leds_write(struct bcm63138_leds *leds, unsigned int reg, in bcm63138_leds_write() argument
72 writel(data, leds->base + reg); in bcm63138_leds_write()
75 static unsigned long bcm63138_leds_read(struct bcm63138_leds *leds, in bcm63138_leds_read() argument
78 return readl(leds->base + reg); in bcm63138_leds_read()
81 static void bcm63138_leds_update_bits(struct bcm63138_leds *leds, in bcm63138_leds_update_bits() argument
[all …]
|
| /linux/arch/arm/boot/dts/allwinner/ |
| H A D | sun8i-v3s-licheepi-zero-dock.dts | 4 * This file is dual-licensed: you can use it either under the terms
24 * restriction, including without limitation the rights to use,
39 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
43 #include "sun8i-v3s-licheepi-zero.dts"
45 #include <dt-bindings/input/input.h>
49 compatible = "licheepi,licheepi-zero-dock", "licheepi,licheepi-zero",
50 "allwinner,sun8i-v3s";
56 leds {
57 /* The LEDs use PG0~2 pins, which conflict with MMC1 */
63 allwinner,leds-active-low;
[all …]
|