Home
last modified time | relevance | path

Searched +full:gpio +full:- +full:leds (Results 1 – 25 of 80) sorted by relevance

1234

/Documentation/devicetree/bindings/leds/
Dleds-ns2.txt1 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 …]
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#
7 title: LEDs connected to GPIO lines
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
19 const: gpio-leds
24 "(^led-[0-9a-f]$|led)":
[all …]
Dleds-group-multicolor.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-group-multicolor.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Multi-color LED built with monochromatic LEDs
10 - Jean-Jacques Hiblot <jjhiblot@traphandler.com>
13 This driver combines several monochromatic LEDs into one multi-color
18 const: leds-group-multicolor
20 leds:
22 An aray of monochromatic leds
[all …]
Dleds-pca955x.txt1 * NXP - pca955x LED driver
4 to control LEDs can be used as general purpose I/Os. The GPIO pins can
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 …]
Dleds-netxbig.txt1 Binding for the CPLD LEDs (GPIO extension bus) found on some LaCie/Seagate
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.
[all …]
Dnxp,pca953x.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/nxp,pca953x.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Riku Voipio <riku.voipio@iki.fi>
13 The PCA9532 family is SMBus I/O expander optimized for dimming LEDs.
17 https://www.nxp.com/docs/en/data-sheet/PCA9532.pdf
22 - nxp,pca9530
23 - nxp,pca9531
24 - nxp,pca9532
[all …]
Dleds-lt3593.txt4 - compatible: Should be "lltc,lt3593".
5 - lltc,ctrl-gpios: A handle to the GPIO that is connected to the 'CTRL'
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.
17 See Documentation/devicetree/bindings/leds/common.txt
18 - default-state: The initial state of the LED.
[all …]
Dleds-lgm.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-lgm.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Zhu, Yi Xin <Yixin.zhu@intel.com>
11 - Amireddy Mallikarjuna reddy <mallikarjunax.reddy@intel.com>
15 const: intel,lgm-ssoled
23 clock-names:
25 - const: sso
26 - const: fpid
[all …]
Dawinic,aw200xx.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/awinic,aw200xx.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Martin Kurbanov <mmkurbanov@sberdevices.ru>
14 a set of individually controlled leds and support 3 pattern controllers
16 - AW20036 (3x12) 36 LEDs
17 - AW20054 (6x9) 54 LEDs
18 - AW20072 (6x12) 72 LEDs
19 - AW20108 (9x12) 108 LEDs
[all …]
Dleds-bcm6358.txt1 LEDs connected to Broadcom BCM6358 controller
4 In these SoCs there are Serial LEDs (LEDs connected to a 74x164 controller),
5 which can either be controlled by software (exporting the 74x164 as spi-gpio.
6 See Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml), or
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.
[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#
7 title: LEDs connected to Broadcom BCM6328 controller
10 - Álvaro Fernández Rojas <noltari@gmail.com>
14 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
15 However, on some devices there are Serial LEDs (LEDs connected to a 74x164
17 as spi-gpio. See
18 Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml), or by hardware
[all …]
Dkinetic,ktd2692.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/kinetic,ktd2692.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Markuss Broks <markuss.broks@gmail.com>
13 KTD2692 is the ideal power solution for high-power flash LEDs.
14 It uses ExpressWire single-wire programming for maximum flexibility.
21 LED current will be ramped up to the flash-mode current level.
27 ctrl-gpios:
29 description: Specifier of the GPIO connected to CTRL pin.
[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#
10 - Andrew Davis <afd@ti.com>
13 The LP50XX is multi-channel, I2C RGB LED Drivers that can group RGB LEDs into
27 - ti,lp5009
28 - ti,lp5012
29 - ti,lp5018
30 - ti,lp5024
[all …]
Dleds-sgm3140.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-sgm3140.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Luca Weiss <luca@z3ntu.xyz>
13 The SGM3140 is a current-regulated charge pump which can regulate two current
17 http://www.sg-micro.com/uploads/soft/20190626/1561535688.pdf
22 - ocs,ocp8110
23 - richtek,rt5033-led
24 - sgmicro,sgm3140
[all …]
Dleds-lp8860.txt1 * Texas Instruments - lp8860 4-Channel LED Driver
3 The LP8860-Q1 is an high-efficiency LED
4 driver with boost controller. It has 4 high-precision
9 - compatible :
11 - reg : I2C slave address
12 - #address-cells : 1
13 - #size-cells : 0
16 - enable-gpios : gpio pin to enable (active high)/disable the device.
17 - vled-supply : LED supply
20 - reg : 0
[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:
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
22 - label : see ../leds/common.txt
[all …]
Dmax77650.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: MAX77650 ultra low-power PMIC from Maxim Integrated.
10 - Bartosz Golaszewski <bgolaszewski@baylibre.com>
13 MAX77650 is an ultra-low power PMIC providing battery charging and power
14 supply for low-power IoT and wearable applications.
16 The GPIO-controller module is represented as part of the top-level PMIC
17 node. The device exposes a single GPIO line.
19 For device-tree bindings of other sub-modules (regulator, power supply,
[all …]
Drohm,bd71828-pmic.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mfd/rohm,bd71828-pmic.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <mazziesaccount@gmail.com>
13 BD71828GW is a single-chip power management IC for battery-powered portable
15 single-cell linear charger. Also included is a Coulomb counter, a real-time
21 - const: rohm,bd71828
23 - items:
24 - const: rohm,bd71879
[all …]
/Documentation/devicetree/bindings/gpio/
Dgpio-lp3943.txt1 TI/National Semiconductor LP3943 GPIO controller
4 - compatible: "ti,lp3943-gpio"
5 - gpio-controller: Marks the device node as a GPIO controller.
6 - #gpio-cells: Should be 2. See gpio.txt in this directory for a
10 Simple LED controls with LP3943 GPIO controller
17 gpioex: gpio {
18 compatible = "ti,lp3943-gpio";
19 gpio-controller;
20 #gpio-cells = <2>;
25 leds {
[all …]
Dgpio-twl4030.txt1 twl4030 GPIO controller bindings
4 - compatible:
5 - "ti,twl4030-gpio" for twl4030 GPIO controller
6 - #gpio-cells : Should be two.
7 - first cell is the pin number
8 - second cell is used to specify optional parameters (unused)
9 - gpio-controller : Marks the device node as a GPIO controller.
10 - #interrupt-cells : Should be 2.
11 - interrupt-controller: Mark the device node as an interrupt controller
12 The first cell is the GPIO number.
[all …]
/Documentation/driver-api/gpio/
Ddrivers-on-gpio.rst2 Subsystem drivers using GPIO
5 Note that standard kernel drivers exist for common GPIO tasks and will provide
6 the right in-kernel and userspace APIs/ABIs for the job, and that these
10 - leds-gpio: drivers/leds/leds-gpio.c will handle LEDs connected to GPIO
13 - ledtrig-gpio: drivers/leds/trigger/ledtrig-gpio.c will provide a LED trigger,
14 i.e. a LED will turn on/off in response to a GPIO line going high or low
15 (and that LED may in turn use the leds-gpio as per above).
17 - gpio-keys: drivers/input/keyboard/gpio_keys.c is used when your GPIO line
20 - gpio-keys-polled: drivers/input/keyboard/gpio_keys_polled.c is used when your
21 GPIO line cannot generate interrupts, so it needs to be periodically polled
[all …]
/Documentation/devicetree/bindings/net/
Dqcom,qca807x.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Christian Marangi <ansuelsmth@gmail.com>
11 - Robert Marko <robert.marko@sartura.hr>
15 IEEE 802.3 clause 22 compliant 10BASE-Te, 100BASE-TX and
16 1000BASE-T PHY-s.
21 Both models have a combo port that supports 1000BASE-X and
22 100BASE-FX fiber.
25 output only pins that natively drive LED-s for up to 2 attached
[all …]
Dqca,qca808x.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Christian Marangi <ansuelsmth@gmail.com>
13 QCA808X PHYs can have up to 3 LEDs attached.
14 All 3 LEDs are disabled by default.
15 2 LEDs have dedicated pins with the 3rd LED having the
16 double function of Interrupt LEDs/GPIO or additional LED.
21 - $ref: ethernet-phy.yaml#
26 - ethernet-phy-id004d.d101
[all …]
/Documentation/ABI/testing/
Dsysfs-class-led1 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
35 What: /sys/class/leds/<led>/max_brightness
45 What: /sys/class/leds/<led>/brightness_hw_changed
[all …]
/Documentation/devicetree/bindings/media/i2c/
Dadp1653.txt5 - 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
15 - led-max-microamp : see Documentation/devicetree/bindings/leds/common.txt
19 - flash-max-microamp : see Documentation/devicetree/bindings/leds/common.txt
20 - flash-timeout-us : see Documentation/devicetree/bindings/leds/common.txt
21 - led-max-microamp : see Documentation/devicetree/bindings/leds/common.txt
25 adp1653: led-controller@30 {
28 enable-gpios = <&gpio3 24 GPIO_ACTIVE_HIGH>; /* 88 */
[all …]

1234