Home
last modified time | relevance | path

Searched +full:led +full:- +full:s (Results 1 – 25 of 110) sorted by relevance

12345

/Documentation/ABI/testing/
Dsysfs-class-led-trigger-netdev1 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 …]
Dsysfs-class-led-driver-lm35331 What: /sys/class/leds/<led>/als_channel
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
33 3 1.049 s
34 4 2.097 s
35 5 4.194 s
36 6 8.389 s
[all …]
/Documentation/devicetree/bindings/leds/
Dcommon.yaml1 # 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 …]
Dleds-trigger-pattern.txt1 * Pattern format for LED pattern trigger
4 The LED is expected to traverse the series and each brightness value for the
19 It will make the LED go gradually from zero-intensity to max (255) intensity in
22 LED brightness
24 255-| / \ / \ /
28 0-| / \/ \/
29 +---0----1----2----3----4----5----6------------> time (s)
31 2. To make the LED go instantly from one brightness value to another, we should
32 use zero-time lengths (the brightness must be same as the previous tuple's). So
39 It will make the LED stay off for one second, then stay at max brightness for
[all …]
Dleds-gpio.yaml1 # 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 …]
Dleds-pwm.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-pwm.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Pavel Machek <pavel@ucw.cz>
13 Each LED is represented as a sub-node of the pwm-leds device. Each
14 node's name represents the name of the corresponding LED.
18 const: pwm-leds
21 "^led(-[0-9a-f]+)?$":
30 pwm-names: true
[all …]
Dleds-el15203000.txt1 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
13 encoded with symbol 'S' (hex code 0x53). Supports blinking breathing pattern.
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
[all …]
Dleds-lp50xx.yaml1 # 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 …]
Dcznic,turris-omnia-leds.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/cznic,turris-omnia-leds.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: CZ.NIC's Turris Omnia LEDs driver
10 - Marek Behún <kabel@kernel.org>
15 microcontroller that communicates via the I2C bus. Each LED is described
20 const: cznic,turris-omnia-leds
26 "#address-cells":
29 "#size-cells":
[all …]
Dleds-lp55xx.yaml1 # 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 …]
Dleds-bcm63138.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-bcm63138.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Broadcom's BCM63138 LEDs controller
10 - Rafał Miłecki <rafal@milecki.pl>
24 - items:
25 - enum:
26 - brcm,bcm4908-leds
27 - brcm,bcm6848-leds
[all …]
Dleds-bcm6328.yaml1 # 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>
14 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
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
[all …]
/Documentation/leds/
Dleds-class-flash.rst2 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 …]
Dleds-lp3944.rst5 * National Semiconductor LP3944 Fun-light Chip
21 -----------
24 is used as a led controller.
29 - period:
30 from 0s to 1.6s
31 - duty cycle:
32 percentage of the period the led is on, from 0 to 100
34 Setting a led in DIM0 or DIM1 mode makes it blink according to the pattern.
42 -----
47 according to include/linux/leds-lp3944.h, set the i2c board info::
Dwell-known-leds.txt1 -*- org -*-
4 userland. LED devices have one problem there, and that is naming of
6 just know right "name" for given LED function, but situation got more
17 Notice there's a list of functions in include/dt-bindings/leds/common.h .
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
31 Good: "input*:*:player-{1,2,3,4,5}
38 Legacy: "shift-key-light" (Motorola Droid 4, capslock)
47 Legacy: "button-backlight" (Motorola Droid 4)
[all …]
/Documentation/devicetree/bindings/mfd/
Dtps6105x.txt3 The TP61050/TPS61052 is a high-power "white LED driver". The
4 device provides LED, GPIO and regulator functionalities.
7 - compatible: "ti,tps61050" or "ti,tps61052"
8 - reg: Specifies the I2C slave address
10 Optional sub-node:
12 This subnode selects the chip's operational mode.
15 - regulator: presence of this sub-node puts the chip in regulator mode.
18 - led: presence of this sub-node puts the chip in led mode.
20 - function : see ../leds/common.txt
21 - color : see ../leds/common.txt
[all …]
Dti-lmu.txt6 ------ ---------------------------------
9 LM3633 Backlight, LED and fault monitor
14 - compatible: Should be one of:
20 - reg: I2C slave address.
28 - enable-gpios: A GPIO specifier for hardware enable pin.
29 - ramp-up-us: Current ramping from one brightness level to
31 Range from 2048 us - 117.44 s
32 - ramp-down-us: Current ramping from one brightness level to
34 Range from 2048 us - 117.44 s
35 - ti,brightness-resolution - This determines whether to use 8 bit brightness
[all …]
Dmfd.txt1 Multi-Function Devices (MFD)
4 more than one non-unique yet varying hardware functionality.
8 - A mixed signal ASIC on an external bus, sometimes a PMIC (Power Management
10 silicon) that handles analog drivers for things like audio amplifiers, LED
14 - A range of memory registers containing "miscellaneous system registers" also
20 - compatible : "simple-mfd" - this signifies that the operating system
23 Similarly to how "simple-bus" indicates when to see subnodes as children for
24 a simple memory-mapped bus.
29 - ranges: Describes the address mapping relationship to the parent. Should set
30 the child's base address to 0, the physical address within parent's address
[all …]
/Documentation/networking/device_drivers/fddi/
Dskfp.rst1 .. SPDX-License-Identifier: GPL-2.0
6 SysKonnect driver - SKFP
9 |copy| Copyright 1998-2000 SysKonnect,
11 skfp.txt created 11-May-2000
53 - SK-5521 (SK-NET FDDI-UP)
54 - SK-5522 (SK-NET FDDI-UP DAS)
55 - SK-5541 (SK-NET FDDI-FP)
56 - SK-5543 (SK-NET FDDI-LP)
57 - SK-5544 (SK-NET FDDI-LP DAS)
58 - SK-5821 (SK-NET FDDI-UP64)
[all …]
/Documentation/driver-api/gpio/
Dboard.rst14 -----------
19 GPIOs mappings are defined in the consumer device's node, in a property named
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::
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/leds/backlight/
Dti,lm3509.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI LM3509 High Efficiency Boost for White LED's and/or OLED Displays
10 - Patrick Gansterer <paroga@paroga.com>
23 "#address-cells":
26 "#size-cells":
29 reset-gpios:
32 ti,brightness-rate-of-change-us:
36 ti,oled-mode:
[all …]
/Documentation/devicetree/bindings/pinctrl/
Dbrcm,nsp-gpio.txt4 - compatible:
5 Must be "brcm,nsp-gpio-a"
7 - reg:
11 - #gpio-cells:
13 controller's pin space) and the second cell is used for the following:
16 - gpio-controller:
19 - ngpios:
23 - interrupts:
26 - interrupt-controller:
29 - gpio-ranges:
[all …]
Dbrcm,bcm6328-pinctrl.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/brcm,bcm6328-pinctrl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Álvaro Fernández Rojas <noltari@gmail.com>
11 - Jonas Gorski <jonas.gorski@gmail.com>
14 Bindings for Broadcom's BCM6328 memory-mapped pin controller.
18 const: brcm,bcm6328-pinctrl
24 '-pins$':
26 $ref: pinmux-node.yaml#
[all …]
Dbrcm,bcm6358-pinctrl.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/brcm,bcm6358-pinctrl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Álvaro Fernández Rojas <noltari@gmail.com>
11 - Jonas Gorski <jonas.gorski@gmail.com>
14 Bindings for Broadcom's BCM6358 memory-mapped pin controller.
18 const: brcm,bcm6358-pinctrl
24 '-pins$':
26 $ref: pinmux-node.yaml#
[all …]
/Documentation/devicetree/bindings/input/
Dmicrochip,cap11xx.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The Microchip CAP1xxx Family of RightTouchTM multiple-channel capacitive
11 touch controllers and LED drivers. The device communication via I2C only.
14 - Rob Herring <robh@kernel.org>
19 - microchip,cap1106
20 - microchip,cap1126
21 - microchip,cap1188
22 - microchip,cap1203
[all …]

12345