/openbmc/u-boot/doc/device-tree-bindings/leds/ |
H A D | leds-gpio.txt | 1 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 D | leds-bcm6328.txt | 1 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 …]
|
/openbmc/linux/drivers/leds/simple/ |
H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 8 This option enables support for the LEDs of several Industrial PCs 12 will be called simatic-ipc-leds. 15 tristate "LED driver for Siemens Simatic IPCs based on Intel Apollo Lake GPIO" 21 This option enables support for the LEDs of several Industrial PCs 22 from Siemens based on Apollo Lake GPIO i.e. IPC127E. 25 will be called simatic-ipc-leds-gpio-apollolake. 28 tristate "LED driver for Siemens Simatic IPCs based on Nuvoton GPIO" 34 This option enables support for the LEDs of several Industrial PCs 35 from Siemens based on Nuvoton GPIO i.e. IPC227G. [all …]
|
H A D | Makefile | 1 # SPDX-License-Identifier: GPL-2.0 2 obj-$(CONFIG_LEDS_SIEMENS_SIMATIC_IPC) += simatic-ipc-leds.o 3 obj-$(CONFIG_LEDS_SIEMENS_SIMATIC_IPC_APOLLOLAKE) += simatic-ipc-leds-gpio-core.o simatic-ipc-leds-… 4 obj-$(CONFIG_LEDS_SIEMENS_SIMATIC_IPC_F7188X) += simatic-ipc-leds-gpio-core.o simatic-ipc-leds-gpi… 5 obj-$(CONFIG_LEDS_SIEMENS_SIMATIC_IPC_ELKHARTLAKE) += simatic-ipc-leds-gpio-core.o simatic-ipc-leds…
|
H A D | simatic-ipc-leds-gpio-f7188x.c | 1 // SPDX-License-Identifier: GPL-2.0 3 * Siemens SIMATIC IPC driver for GPIO based LEDs 11 #include <linux/gpio/machine.h> 12 #include <linux/gpio/consumer.h> 13 #include <linux/leds.h> 16 #include <linux/platform_data/x86/simatic-ipc-base.h> 18 #include "simatic-ipc-leds-gpio.h" 21 .dev_id = "leds-gpio", 23 GPIO_LOOKUP_IDX("gpio-f7188x-2", 0, NULL, 0, GPIO_ACTIVE_LOW), 24 GPIO_LOOKUP_IDX("gpio-f7188x-2", 1, NULL, 1, GPIO_ACTIVE_LOW), [all …]
|
H A D | simatic-ipc-leds-gpio-elkhartlake.c | 1 // SPDX-License-Identifier: GPL-2.0 3 * Siemens SIMATIC IPC driver for GPIO based LEDs 11 #include <linux/gpio/machine.h> 12 #include <linux/gpio/consumer.h> 13 #include <linux/leds.h> 16 #include <linux/platform_data/x86/simatic-ipc-base.h> 18 #include "simatic-ipc-leds-gpio.h" 21 .dev_id = "leds-gpio", 56 MODULE_SOFTDEP("pre: simatic-ipc-leds-gpio-core platform:elkhartlake-pinctrl");
|
H A D | simatic-ipc-leds-gpio-core.c | 1 // SPDX-License-Identifier: GPL-2.0 3 * Siemens SIMATIC IPC driver for GPIO based LEDs 11 #include <linux/gpio/machine.h> 12 #include <linux/gpio/consumer.h> 13 #include <linux/leds.h> 16 #include <linux/platform_data/x86/simatic-ipc-base.h> 18 #include "simatic-ipc-leds-gpio.h" 23 { .name = "red:" LED_FUNCTION_STATUS "-1" }, 24 { .name = "green:" LED_FUNCTION_STATUS "-1" }, 25 { .name = "red:" LED_FUNCTION_STATUS "-2" }, [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/leds/ |
H A D | leds-gpio.yaml | 1 # 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 D | leds-ns2.txt | 1 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 D | leds-group-multicolor.yaml | 1 # 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 …]
|
H A D | leds-pca955x.txt | 1 * 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 …]
|
H A D | leds-netxbig.txt | 1 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 …]
|
/openbmc/linux/arch/x86/platform/geode/ |
H A D | geos.c | 1 // 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> 23 #include <linux/gpio/machine.h> 31 .gpio = 3, 47 .name = "gpio-keys-polled", 57 .default_trigger = "default-on", [all …]
|
H A D | alix.c | 1 // SPDX-License-Identifier: GPL-2.0-only 4 * At the moment this means setup of GPIO control of LEDs 9 * and Philip Prindeville <philipp@redfish-solutions.com> 11 * TODO: There are large similarities with leds-net5501.c 13 * In the future leds-net5501.c should be migrated over to platform 21 #include <linux/leds.h> 25 #include <linux/gpio/machine.h> 47 .gpio = 24, 63 .name = "gpio-keys-polled", 73 .default_trigger = "default-on", [all …]
|
/openbmc/u-boot/arch/mips/mach-bmips/ |
H A D | Kconfig | 137 ethernet ports, 2 USB ports, 1 UART, GPIO buttons and LEDs, and 141 bool "Comtrend AR-5315u" 145 Comtrend AR-5315u boards have a BCM6318 SoC with 64 MB of RAM and 16 148 ethernet ports, 1 USB port, 1 UART, GPIO buttons and LEDs, and 152 bool "Comtrend AR-5387un" 156 Comtrend AR-5387un boards have a BCM6328 SoC with 64 MB of RAM and 16 159 ethernet ports, 1 USB port, 1 UART, GPIO buttons and LEDs, and 163 bool "Comtrend CT-5361" 167 Comtrend CT-5361 boards have a BCM6348 SoC with 16 MB of RAM and 4 MB 170 ethernet ports, 1 USB port, 1 UART, GPIO buttons and LEDs, and a [all …]
|
/openbmc/linux/drivers/leds/ |
H A D | leds-gpio.c | 1 // 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> 20 #include "leds.h" 47 if (led_dat->blinking) { in gpio_led_set() 48 led_dat->platform_gpio_blink_set(led_dat->gpiod, level, in gpio_led_set() 50 led_dat->blinking = 0; in gpio_led_set() 52 if (led_dat->can_sleep) in gpio_led_set() [all …]
|
H A D | Kconfig | 1 # 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 Y. 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 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> 19 #include <linux/gpio/driver.h> 40 struct pca9532_led leds[16]; member 45 struct gpio_chip gpio; member 101 .name = "leds-pca953x", 109 /* We have two pwm/blinkers, but 16 possible leds to drive. Additionally, 112 * leds that are not ON/OFF. [all …]
|
H A D | leds-gpio-register.c | 1 // 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 16 * Makes a copy of pdata and pdata->leds and registers a new leds-gpio device 17 * with the result. This allows to have pdata and pdata-leds in .init.rodata 29 if (!pdata->num_leds) in gpio_led_register_device() 30 return ERR_PTR(-EINVAL); in gpio_led_register_device() 32 _pdata.leds = kmemdup(pdata->leds, in gpio_led_register_device() 33 pdata->num_leds * sizeof(*pdata->leds), GFP_KERNEL); in gpio_led_register_device() [all …]
|
H A D | leds-netxbig.c | 1 // 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 …]
|
/openbmc/u-boot/arch/arm/dts/ |
H A D | kirkwood-d2net.dts | 1 // 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 …]
|
/openbmc/linux/arch/arm/boot/dts/marvell/ |
H A D | kirkwood-d2net.dts | 1 // 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 D | armada-370-seagate-nas-4bay.dts | 1 // 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 …]
|
/openbmc/linux/Documentation/driver-api/gpio/ |
H A D | drivers-on-gpio.rst | 2 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 …]
|
/openbmc/linux/drivers/platform/x86/ |
H A D | pcengines-apuv2.c | 1 // 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 …]
|