Home
last modified time | relevance | path

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

12345678910>>...41

/OK3568_Linux_fs/u-boot/doc/device-tree-bindings/leds/
H A Dleds-gpio.txt1 LEDs connected to GPIO lines
4 - compatible : should be "gpio-leds".
6 Each LED is represented as a sub-node of the gpio-leds device. Each
9 LED sub-node properties:
10 - gpios : Should specify the LED's GPIO, see "gpios property" in
11 Documentation/devicetree/bindings/gpio/gpio.txt. Active low LEDs should be
12 indicated using flags in the GPIO specifier.
13 - label : (optional)
14 see Documentation/devicetree/bindings/leds/common.txt
15 - linux,default-trigger : (optional)
[all …]
H A Dleds-bcm6328.txt1 LEDs connected to Broadcom BCM6328 controller
4 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
5 However, on some devices there are Serial LEDs (LEDs connected to a 74x164
7 as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
9 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
14 - compatible : should be "brcm,bcm6328-leds".
15 - #address-cells : must be 1.
16 - #size-cells : must be 0.
17 - reg : BCM6328 LED controller address and size.
[all …]
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/leds/
H A 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 …]
H A 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 …]
H A 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 …]
/OK3568_Linux_fs/kernel/drivers/leds/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
13 LEDs from both userspace and optionally, by kernel events (triggers).
20 This option enables the LED sysfs class in /sys/class/leds. You'll
21 need this to do anything useful with LEDs. If unsure, say N.
27 This option enables the flash LED sysfs class in /sys/class/leds.
28 It wraps LED Class and adds flash LEDs specific sysfs attributes
37 This option enables the multicolor LED sysfs class in /sys/class/leds.
40 for multicolor LEDs that are grouped together. This class is not
41 intended for single color LEDs. It can be built as a module.
48 for LED sysfs class devices under /sys/class/leds.
[all …]
H A Dleds-pca955x.c1 // 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 Dleds-pca9532.c1 // 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>
19 #include <linux/gpio/driver.h>
41 struct pca9532_led leds[16]; member
46 struct gpio_chip gpio; member
103 .name = "leds-pca953x",
111 /* We have two pwm/blinkers, but 16 possible leds to drive. Additionally,
114 * leds that are not ON/OFF.
[all …]
H A Dleds-gpio.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * LEDs driver for GPIOs
10 #include <linux/gpio.h>
11 #include <linux/gpio/consumer.h>
13 #include <linux/leds.h>
45 if (led_dat->blinking) { in gpio_led_set()
46 led_dat->platform_gpio_blink_set(led_dat->gpiod, level, in gpio_led_set()
48 led_dat->blinking = 0; in gpio_led_set()
50 if (led_dat->can_sleep) in gpio_led_set()
51 gpiod_set_value_cansleep(led_dat->gpiod, level); in gpio_led_set()
[all …]
H A Dleds-netxbig.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * leds-netxbig.c - Driver for the 2Big and 5Big Network series LEDs
15 #include <linux/gpio/consumer.h>
16 #include <linux/leds.h>
58 struct netxbig_led *leds; member
63 * GPIO extension bus.
72 for (pin = 0; pin < gpio_ext->num_addr; pin++) in gpio_ext_set_addr()
73 gpiod_set_value(gpio_ext->addr[pin], (addr >> pin) & 1); in gpio_ext_set_addr()
80 for (pin = 0; pin < gpio_ext->num_data; pin++) in gpio_ext_set_data()
81 gpiod_set_value(gpio_ext->data[pin], (data >> pin) & 1); in gpio_ext_set_data()
[all …]
H A Dleds-tca6507.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * leds-tca6507
9 * blink or double-blink.
11 * This driver can configure each line either as a 'GPIO' which is
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,
[all …]
H A Dleds-gpio-register.c1 // SPDX-License-Identifier: GPL-2.0-only
4 * Uwe Kleine-Koenig <u.kleine-koenig@pengutronix.de>
7 #include <linux/leds.h>
12 * gpio_led_register_device - register a gpio-led device
15 * Makes a copy of pdata and pdata->leds and registers a new leds-gpio device
16 * with the result. This allows to have pdata and pdata-leds in .init.rodata
28 if (!pdata->num_leds) in gpio_led_register_device()
29 return ERR_PTR(-EINVAL); in gpio_led_register_device()
31 _pdata.leds = kmemdup(pdata->leds, in gpio_led_register_device()
32 pdata->num_leds * sizeof(*pdata->leds), GFP_KERNEL); in gpio_led_register_device()
[all …]
/OK3568_Linux_fs/kernel/arch/x86/platform/geode/
H A Dgeos.c1 // SPDX-License-Identifier: GPL-2.0-only
4 * At the moment this means setup of GPIO control of LEDs.
8 * and Philip Prindeville <philipp@redfish-solutions.com>
10 * TODO: There are large similarities with leds-net5501.c
12 * In the future leds-net5501.c should be migrated over to platform
19 #include <linux/leds.h>
30 .gpio = 3,
46 .name = "gpio-keys-polled",
56 .gpio = 6,
57 .default_trigger = "default-on",
[all …]
/OK3568_Linux_fs/kernel/arch/mips/bcm63xx/boards/
H A Dboard_bcm963xx.c1 // SPDX-License-Identifier: GPL-2.0-only
56 .leds = {
59 .gpio = 37,
60 .default_trigger= "default-on",
83 .leds = {
85 .name = "96328avng::ppp-fail",
86 .gpio = 2,
91 .gpio = 4,
93 .default_trigger = "default-on",
96 .name = "96328avng::power-fail",
[all …]
/OK3568_Linux_fs/kernel/Documentation/driver-api/gpio/
H A 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 …]
/OK3568_Linux_fs/u-boot/drivers/led/
H A DKconfig7 Many boards have LEDs which can be used to signal status or alerts.
8 U-Boot provides a uclass API to implement this feature. LED drivers
9 can provide access to board-specific LEDs. Use of the device tree
16 This option enables support for LEDs connected to the BCM6328
18 HW blinking is supported and up to 24 LEDs can be controlled.
19 All LEDs can blink at the same time but the delay is shared, which
27 This option enables support for LEDs connected to the BCM6358
29 HW has no blinking capabilities and up to 32 LEDs can be controlled.
35 Some drivers can support automatic blinking of LEDs with a given
45 If this is acceptable and you have a need to use LEDs in SPL,
[all …]
/OK3568_Linux_fs/kernel/drivers/platform/x86/
H A Dpcengines-apuv2.c1 // SPDX-License-Identifier: GPL-2.0+
4 * PC-Engines APUv2/APUv3 board platform driver
5 * for GPIO buttons and LEDs
16 #include <linux/leds.h>
20 #include <linux/gpio/machine.h>
22 #include <linux/platform_data/gpio/gpio-amd-fch.h>
25 * NOTE: this driver only supports APUv2/3 - not APUv1, as this one
38 /* Order in which the GPIO lines are defined in the register list */
47 /* GPIO device */
60 [APU2_GPIO_LINE_LED1] = "front-led1",
[all …]
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/media/i2c/
H A Dsgm3784.txt4 - compatible: Must contain "sgmicro,gsm3784"
5 - reg: I2C slave address
6 - enable-gpios: Specifier of the GPIO connected to EN pin
7 - strobe-gpio: Specifier of the GPIO connected to STROBE pin
8 - torch-gpio: Specifier of the GPIO connected to GPIO pin,
13 node - see Documentation/devicetree/bindings/leds/common.txt.
16 - led-max-microamp : see Documentation/devicetree/bindings/leds/common.txt
17 - flash-max-microamp : see Documentation/devicetree/bindings/leds/common.txt
18 - flash-max-timeout-us : see Documentation/devicetree/bindings/leds/common.txt
21 - rockchip,camera-module-index : indicate which camera the flash belongs to.
[all …]
/OK3568_Linux_fs/kernel/drivers/leds/trigger/
H A DKconfig1 # 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
39 This allows LEDs to be controlled by disk activity.
46 This allows LEDs to be controlled by MTD activity.
52 This allows LEDs to be controlled by a CPU load average.
[all …]
/OK3568_Linux_fs/kernel/arch/arm/boot/dts/
H A Dkirkwood-d2net.dts1 // SPDX-License-Identifier: GPL-2.0
9 /dts-v1/;
11 #include <dt-bindings/leds/leds-ns2.h>
12 #include "kirkwood-netxbig.dtsi"
16 compatible = "lacie,d2net_v2", "lacie,netxbig", "marvell,kirkwood-88f6281", "marvell,kirkwood";
23 ns2-leds {
24 compatible = "lacie,ns2-leds";
26 blue-sata {
28 slow-gpio = <&gpio0 29 GPIO_ACTIVE_HIGH>;
29 cmd-gpio = <&gpio0 30 GPIO_ACTIVE_HIGH>;
[all …]
H A Darmada-370-seagate-nas-4bay.dts1 // SPDX-License-Identifier: GPL-2.0
3 * Device Tree file for Seagate NAS 4-Bay (Armada 370 SoC).
13 * Product name : Seagate NAS 4-Bay
14 * Code name (board/PCB) : Dart 4-Bay
19 /dts-v1/;
20 #include "armada-370-seagate-nas-xbay.dtsi"
21 #include <dt-bindings/leds/leds-ns2.h>
24 model = "Seagate NAS 4-Bay (Dart, SRPD40)";
25 compatible = "seagate,dart-4", "marvell,armada370", "marvell,armada-370-xp";
28 internal-regs {
[all …]
H A Dkirkwood-synology.dtsi1 // SPDX-License-Identifier: GPL-2.0
12 pinctrl: pin-controller@10000 {
13 pmx_alarmled_12: pmx-alarmled-12 {
15 marvell,function = "gpio";
18 pmx_fanctrl_15: pmx-fanctrl-15 {
20 marvell,function = "gpio";
23 pmx_fanctrl_16: pmx-fanctrl-16 {
25 marvell,function = "gpio";
28 pmx_fanctrl_17: pmx-fanctrl-17 {
30 marvell,function = "gpio";
[all …]
/OK3568_Linux_fs/u-boot/arch/mips/mach-bmips/
H A DKconfig88 bool "Comtrend AR-5387un"
92 Comtrend AR-5387un boards have a BCM6328 SoC with 64 MB of RAM and 16
95 ethernet ports, 1 USB port, 1 UART, GPIO buttons and LEDs, and
99 bool "Comtrend CT-5361"
103 Comtrend CT-5361 boards have a BCM6348 SoC with 16 MB of RAM and 4 MB
106 ethernet ports, 1 USB port, 1 UART, GPIO buttons and LEDs, and a
110 bool "Comtrend VR-3032u board"
114 Comtrend VR-3032u boards have a BCM63268 SoC with 64 MB of RAM and
117 ethernet ports, 1 USB port, 1 UART, GPIO buttons and LEDs,
128 ethernet ports, 3 USB ports, 1 UART, GPIO buttons and LEDs, and
[all …]
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/mfd/
H A 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 <matti.vaittinen@fi.rohmeurope.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
30 gpio-controller: true
32 "#gpio-cells":
36 flags. See ../gpio/gpio.txt for more information.
[all …]
H A 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 …]

12345678910>>...41