Home
last modified time | relevance | path

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

12345678910>>...42

/linux/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-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 …]
/linux/arch/x86/platform/geode/
H A Dgeode-common.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Shared helpers to register GPIO-connected buttons and LEDs
8 #include <linux/gpio/machine.h>
9 #include <linux/gpio/property.h>
11 #include <linux/leds.h>
15 #include "geode-common.h"
18 .name = "cs5535-gpio",
22 PROPERTY_ENTRY_U32("poll-interval", 20),
27 .name = "geode-gpio-keys",
32 { /* Placeholder for GPIO property */ },
[all …]
/linux/drivers/leds/
H A Dleds-gpio.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * LEDs driver for GPIOs
12 #include <linux/gpio.h>
13 #include <linux/gpio/consumer.h>
14 #include <linux/leds.h>
49 if (led_dat->blinking) { in gpio_led_set()
50 led_dat->platform_gpio_blink_set(led_dat->gpiod, level, in gpio_led_set()
52 led_dat->blinking = 0; in gpio_led_set()
54 if (led_dat->can_sleep) in gpio_led_set()
55 gpiod_set_value_cansleep(led_dat->gpiod, level); in gpio_led_set()
[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>
43 struct pca9532_led leds[16]; member
48 struct gpio_chip gpio; 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.
[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
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 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-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 …]
/linux/arch/arm/boot/dts/qcom/
H A Dqcom-ipq8064-rb3011.dts1 // SPDX-License-Identifier: GPL-2.0
2 #include "qcom-ipq8064.dtsi"
3 #include <dt-bindings/input/input.h>
4 #include <dt-bindings/leds/common.h>
7 model = "MikroTik RB3011UiAS-RM";
14 mdio-gpio0 = &mdio0;
15 mdio-gpio1 = &mdio1;
20 stdout-path = "serial0:115200n8";
23 gpio-keys {
24 compatible = "gpio-keys";
[all …]
/linux/arch/arm/boot/dts/marvell/
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 …]
H A Dmvebu-linkstation-gpio-simple.dtsi2 * 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
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";
57 linux,input-type = <5>;
60 power-auto-switch {
[all …]
/linux/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 …]
/linux/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 …]
/linux/arch/arm64/boot/dts/marvell/
H A Dcn9130-cf-base.dts1 // SPDX-License-Identifier: GPL-2.0+
3 * Copyright (C) 2024 Josua Mayer <josua@solid-run.com>
9 /dts-v1/;
11 #include <dt-bindings/input/input.h>
12 #include <dt-bindings/leds/common.h>
15 #include "cn9130-sr-som.dtsi"
16 #include "cn9130-cf.dtsi"
20 compatible = "solidrun,cn9130-clearfog-base",
21 "solidrun,cn9130-sr-som", "marvell,cn9130";
23 gpio-keys {
[all …]
/linux/arch/arm64/boot/dts/qcom/
H A Dipq5332-rdp-common.dtsi1 // SPDX-License-Identifier: BSD-3-Clause
5 * Copyright (c) 2022-2023 Qualcomm Innovation Center, Inc. All rights reserved.
8 /dts-v1/;
10 #include <dt-bindings/gpio/gpio.h>
11 #include <dt-bindings/input/input.h>
12 #include <dt-bindings/leds/common.h>
21 stdout-path = "serial0";
24 gpio-keys {
25 compatible = "gpio-keys";
26 pinctrl-0 = <&gpio_keys_default>;
[all …]
H A Dmsm8916-ufi.dtsi1 // SPDX-License-Identifier: GPL-2.0-only
3 #include "msm8916-pm8916.dtsi"
5 #include <dt-bindings/gpio/gpio.h>
6 #include <dt-bindings/leds/common.h>
9 chassis-type = "embedded";
17 stdout-path = "serial0";
20 gpio-keys {
21 compatible = "gpio-keys";
23 pinctrl-0 = <&button_default>;
24 pinctrl-names = "default";
[all …]
/linux/drivers/platform/x86/intel/atomisp2/
H A Dled.c1 // SPDX-License-Identifier: GPL-2.0+
3 * Driver for controlling LEDs for cameras connected to the Intel atomisp2
4 * The main purpose of this driver is to turn off LEDs which are on at boot.
10 #include <linux/gpio/consumer.h>
11 #include <linux/gpio/machine.h>
12 #include <linux/leds.h>
18 /* This must be leds-gpio as the leds-gpio driver binds to the name */
19 #define DEV_NAME "leds-gpio"
30 .leds = atomisp2_leds,
85 return -ENODEV; in atomisp2_led_init()
[all …]
/linux/arch/powerpc/platforms/44x/
H A Dwarp.c1 // SPDX-License-Identifier: GPL-2.0-or-later
5 * Copyright (c) 2008-2009 PIKA Technologies
13 #include <linux/leds.h>
19 #include <linux/gpio/consumer.h>
62 np = of_find_compatible_node(NULL, NULL, "pika,fpga-sd"); in warp_post_info()
64 return -ENOENT; in warp_post_info()
69 return -ENOENT; in warp_post_info()
106 .leds = warp_gpio_led_pins,
111 .name = "leds-gpio",
112 .id = -1,
[all …]
/linux/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 …]
/linux/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 <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 …]
/linux/drivers/mfd/
H A Dlp3943.c1 // SPDX-License-Identifier: GPL-2.0-only
11 * It can be used for a GPIO expander and PWM generators.
16 * LP3943 MFD ---- GPIO expander leds-gpio eg) HW enable pin
18 * --- PWM generator leds-pwm eg) PWM input
21 * And each output pin can be used as a GPIO as well.
23 * LEDs can be controlled with legacy leds-gpio(static brightness) or
24 * leds-pwm drivers(dynamic brightness control).
25 * Alternatively, it can be used for generic GPIO and PWM controller.
26 * For example, a GPIO is HW enable pin of a device.
31 #include <linux/gpio.h>
[all …]
/linux/Documentation/devicetree/bindings/net/
H A 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 …]

12345678910>>...42