| /openbmc/linux/arch/arm/boot/dts/nuvoton/ |
| H A D | nuvoton-npcm750-runbmc-olympus.dts | 1 // SPDX-License-Identifier: GPL-2.0
5 /dts-v1/;
6 #include "nuvoton-npcm750.dtsi"
7 #include "nuvoton-npcm750-runbmc-olympus-pincfg.dtsi"
9 #include <dt-bindings/i2c/i2c.h>
10 #include <dt-bindings/gpio/gpio.h>
43 stdout-path = &serial3;
50 iio-hwmon {
51 compatible = "iio-hwmon";
52 io-channels = <&adc 0>, <&adc 1>, <&adc 2>, <&adc 3>,
[all …]
|
| /openbmc/linux/arch/arm64/boot/dts/hisilicon/ |
| H A D | hi3670-hikey970.dts | 1 // SPDX-License-Identifier: GPL-2.0
10 /dts-v1/;
11 #include <dt-bindings/gpio/gpio.h>
14 #include "hikey970-pinctrl.dtsi"
15 #include "hikey970-pmic.dtsi"
19 compatible = "hisilicon,hi3670-hikey970", "hisilicon,hi3670";
34 stdout-path = "serial6:115200n8";
43 wlan_en: wlan-en-1-8v {
44 compatible = "regulator-fixed";
45 regulator-name = "wlan-en-regulator";
[all …]
|
| H A D | hi3660-hikey960.dts | 1 // SPDX-License-Identifier: GPL-2.0
9 /dts-v1/;
12 #include "hikey960-pinctrl.dtsi"
13 #include <dt-bindings/gpio/gpio.h>
14 #include <dt-bindings/input/input.h>
15 #include <dt-bindings/interrupt-controller/irq.h>
16 #include <dt-bindings/usb/pd.h>
20 compatible = "hisilicon,hi3660-hikey960", "hisilicon,hi3660";
35 stdout-path = "serial6:115200n8";
44 reserved-memory {
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/gpio/ |
| H A D | gpio-mmio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/gpio/gpio-mmio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic MMIO GPIO
10 - Linus Walleij <linus.walleij@linaro.org>
11 - Bartosz Golaszewski <brgl@bgdev.pl>
14 Some simple GPIO controllers may consist of a single data register or a pair
15 of set/clear-bit registers. Such controllers are common for glue logic in
16 FPGAs or ASICs. Commonly, these controllers are accessed over memory-mapped
[all …]
|
| H A D | gpio-zynq.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/gpio/gpio-zynq.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Xilinx Zynq GPIO controller
10 - Michal Simek <michal.simek@amd.com>
15 - xlnx,zynq-gpio-1.0
16 - xlnx,zynqmp-gpio-1.0
17 - xlnx,versal-gpio-1.0
18 - xlnx,pmc-gpio-1.0
[all …]
|
| H A D | gpio.txt | 1 Specifying GPIO information for devices
5 -----------------
7 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
8 of this GPIO for the device. While a non-existent <name> is considered valid
10 for new bindings. Also, GPIO properties named "[<name>-]gpio" are valid and old
14 GPIO properties can contain one or more GPIO phandles, but only in exceptional
18 several GPIOs serve the same function (e.g. a parallel data line).
23 The following example could be used to describe GPIO pins used as device enable
24 and bit-banged data signals:
27 gpio-controller;
[all …]
|
| /openbmc/linux/Documentation/admin-guide/gpio/ |
| H A D | gpio-sim.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
3 Configfs GPIO Simulator
6 The configfs GPIO Simulator (gpio-sim) provides a way to create simulated GPIO
8 using the standard GPIO character device interface as well as manipulated
12 ------------------------
14 The gpio-sim module registers a configfs subsystem called ``'gpio-sim'``. For
21 **Group:** ``/config/gpio-sim``
23 This is the top directory of the gpio-sim configfs tree.
25 **Group:** ``/config/gpio-sim/gpio-device``
27 **Attribute:** ``/config/gpio-sim/gpio-device/dev_name``
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/input/ |
| H A D | gpio-mouse.txt | 1 Device-Tree bindings for GPIO attached mice
3 This simply uses standard GPIO handles to define a simple mouse connected
4 to 5-7 GPIO lines.
7 - compatible: must be "gpio-mouse"
8 - scan-interval-ms: The scanning interval in milliseconds
9 - up-gpios: GPIO line phandle to the line indicating "up"
10 - down-gpios: GPIO line phandle to the line indicating "down"
11 - left-gpios: GPIO line phandle to the line indicating "left"
12 - right-gpios: GPIO line phandle to the line indicating "right"
15 - button-left-gpios: GPIO line handle to the left mouse button
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/media/cec/ |
| H A D | cec-gpio.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/media/cec/cec-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: HDMI CEC GPIO
10 - Hans Verkuil <hverkuil-cisco@xs4all.nl>
13 The HDMI CEC GPIO module supports CEC implementations where the CEC line is
14 hooked up to a pull-up GPIO line and - optionally - the HPD line is hooked up
15 to another GPIO line.
17 Please note:: the maximum voltage for the CEC line is 3.63V, for the HPD and
[all …]
|
| /openbmc/u-boot/drivers/gpio/ |
| H A D | mpc83xx_gpio.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * Freescale MPC83xx GPIO handling.
8 #include <asm/gpio.h>
36 int gpio_request(unsigned gpio, const char *label) in gpio_request() argument
38 if (gpio >= MAX_NUM_GPIOS) in gpio_request()
39 return -1; in gpio_request()
44 int gpio_free(unsigned gpio) in gpio_free() argument
50 /* set GPIO pin 'gpio' as an input */
51 int gpio_direction_input(unsigned gpio) in gpio_direction_input() argument
55 unsigned int line; in gpio_direction_input() local
[all …]
|
| /openbmc/phosphor-gpio-monitor/ |
| H A D | README.md | 1 # GPIO Monitoring
5 ### `phosphor-gpio-monitor`
7 This daemon accepts a command line parameter for monitoring single gpio line and
8 take action if requested. This implementation uses GPIO keys and only supports
9 monitoring single GPIO line, for multiple lines, user has to run this daemon
10 seperately for each gpio line.
12 ### `phosphor-multi-gpio-monitor`
14 This daemon accepts command line parameter as a well-defined GPIO configuration
16 defined in config based on gpio state change. It uses libgpiod library.
20 New implementation (phosphor-multi-gpio-monitor) provides multiple gpio line
[all …]
|
| H A D | gpioMonMain.cpp | 8 * http://www.apache.org/licenses/LICENSE-2.0
22 #include <phosphor-logging/lg2.hpp>
28 namespace gpio namespace
46 CLI::App app{"Monitor GPIO line for requested state change"}; in main()
51 app.add_option("-c,--config", gpioFileName, "Name of config json file") in main()
52 ->required() in main()
53 ->check(CLI::ExistingFile); in main()
65 /* Get list of gpio config details from json file */ in main()
69 lg2::error("GPIO monitor config file not found: {FILE}", "FILE", in main()
71 return -1; in main()
[all …]
|
| H A D | gpioMon.hpp | 13 namespace gpio namespace
17 * @brief Responsible for catching GPIO state change
32 * @param[in] line - GPIO line from libgpiod
33 * @param[in] config - configuration of line with event
34 * @param[in] io - io service
35 * @param[in] target - systemd unit to be started on GPIO
37 * @param[in] targets - systemd units to be started on GPIO
39 * @param[in] lineMsg - GPIO line message to be used for log
40 * @param[in] continueRun - Whether to continue after event occur
42 GpioMonitor(gpiod_line* line, gpiod_line_request_config& config, in GpioMonitor() argument
[all …]
|
| /openbmc/linux/Documentation/driver-api/gpio/ |
| H A D | driver.rst | 2 GPIO Driver Interface
5 This document serves as a guide for writers of GPIO chip drivers.
7 Each GPIO controller driver needs to include the following header, which defines
8 the structures used to define a GPIO driver::
10 #include <linux/gpio/driver.h>
16 A GPIO chip handles one or more GPIO lines. To be considered a GPIO chip, the
18 line is not general purpose, it is not GPIO and should not be handled by a
19 GPIO chip. The use case is the indicative: certain lines in a system may be
20 called GPIO but serve a very particular purpose thus not meeting the criteria
21 of a general purpose I/O. On the other hand a LED driver line may be used as a
[all …]
|
| 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/arch/arm/boot/dts/aspeed/ |
| H A D | aspeed-bmc-opp-palmetto.dts | 1 // SPDX-License-Identifier: GPL-2.0+
2 /dts-v1/;
4 #include "aspeed-g4.dtsi"
5 #include <dt-bindings/gpio/aspeed-gpio.h>
9 compatible = "tyan,palmetto-bmc", "aspeed,ast2400";
12 stdout-path = &uart5;
20 reserved-memory {
21 #address-cells = <1>;
22 #size-cells = <1>;
26 no-map;
[all …]
|
| H A D | aspeed-bmc-lenovo-hr855xg2.dts | 1 // SPDX-License-Identifier: GPL-2.0+
5 * Copyright (C) 2019-present Lenovo
8 /dts-v1/;
10 #include "aspeed-g5.dtsi"
11 #include <dt-bindings/gpio/aspeed-gpio.h>
15 compatible = "lenovo,hr855xg2-bmc", "aspeed,ast2500";
29 stdout-path = &uart5;
38 reserved-memory {
39 #address-cells = <1>;
40 #size-cells = <1>;
[all …]
|
| H A D | aspeed-bmc-lenovo-hr630.dts | 1 // SPDX-License-Identifier: GPL-2.0+
5 * Copyright (C) 2019-present Lenovo
8 /dts-v1/;
10 #include "aspeed-g5.dtsi"
11 #include <dt-bindings/gpio/aspeed-gpio.h>
15 compatible = "lenovo,hr630-bmc", "aspeed,ast2500";
29 stdout-path = &uart5;
38 reserved-memory {
39 #address-cells = <1>;
40 #size-cells = <1>;
[all …]
|
| /openbmc/linux/drivers/gpu/drm/nouveau/nvkm/subdev/gpio/ |
| H A D | base.c | 29 nvkm_gpio_drive(struct nvkm_gpio *gpio, int idx, int line, int dir, int out) in nvkm_gpio_drive() argument
31 return gpio->func->drive(gpio, line, dir, out); in nvkm_gpio_drive()
35 nvkm_gpio_sense(struct nvkm_gpio *gpio, int idx, int line) in nvkm_gpio_sense() argument
37 return gpio->func->sense(gpio, line); in nvkm_gpio_sense()
41 nvkm_gpio_reset(struct nvkm_gpio *gpio, u8 func) in nvkm_gpio_reset() argument
43 if (gpio->func->reset) in nvkm_gpio_reset()
44 gpio->func->reset(gpio, func); in nvkm_gpio_reset()
48 nvkm_gpio_find(struct nvkm_gpio *gpio, int idx, u8 tag, u8 line, in nvkm_gpio_find() argument
51 struct nvkm_device *device = gpio->subdev.device; in nvkm_gpio_find()
52 struct nvkm_bios *bios = device->bios; in nvkm_gpio_find()
[all …]
|
| H A D | nv10.c | 29 nv10_gpio_sense(struct nvkm_gpio *gpio, int line) in nv10_gpio_sense() argument
31 struct nvkm_device *device = gpio->subdev.device; in nv10_gpio_sense()
32 if (line < 2) { in nv10_gpio_sense()
33 line = line * 16; in nv10_gpio_sense()
34 line = nvkm_rd32(device, 0x600818) >> line; in nv10_gpio_sense()
35 return !!(line & 0x0100); in nv10_gpio_sense()
37 if (line < 10) { in nv10_gpio_sense()
38 line = (line - 2) * 4; in nv10_gpio_sense()
39 line = nvkm_rd32(device, 0x60081c) >> line; in nv10_gpio_sense()
40 return !!(line & 0x04); in nv10_gpio_sense()
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | qcom,pmic-gpio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/qcom,pmic-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm PMIC GPIO block
10 - Bjorn Andersson <bjorn.andersson@linaro.org>
13 This binding describes the GPIO block(s) found in the 8xxx series of
19 - enum:
20 - qcom,pm2250-gpio
21 - qcom,pm660-gpio
[all …]
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | gpio.h | 1 /* SPDX-License-Identifier: GPL-2.0-only WITH Linux-syscall-note */
3 * <linux/gpio.h> - userspace ABI for the GPIO character devices
21 * Must be a multiple of 8 to ensure 32/64-bit alignment of structs.
26 * struct gpiochip_info - Information about a certain GPIO chip
27 * @name: the Linux kernel name of this GPIO chip
28 * @label: a functional name for this GPIO chip, such as a product
30 * @lines: number of GPIO lines on this chip
41 * Must be no greater than 64, as bitmaps are restricted here to 64-bits
42 * for simplicity, and a multiple of 2 to ensure 32/64-bit alignment of
48 * The maximum number of configuration attributes associated with a line
[all …]
|
| /openbmc/linux/arch/arm64/boot/dts/mediatek/ |
| H A D | pumpkin-common.dtsi | 1 // SPDX-License-Identifier: GPL-2.0
7 #include <dt-bindings/gpio/gpio.h>
16 stdout-path = "serial0:921600n8";
21 compatible = "linaro,optee-tz";
26 gpio-keys {
27 compatible = "gpio-keys";
28 pinctrl-names = "default";
29 pinctrl-0 = <&gpio_keys_default>;
31 key-volume-up {
35 wakeup-source;
[all …]
|
| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A D | gpio-properties.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 _DSD Device Properties Related to GPIO
10 the corresponding GPIO, which is pretty error prone (it depends on
31 ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
34 Package () { "reset-gpios", Package () { ^BTH, 1, 1, 0 } },
35 Package () { "shutdown-gpios", Package () { ^BTH, 0, 0, 0 } },
40 The format of the supported GPIO property is::
52 If 1, the GPIO is marked as active_low.
56 it to 1 marks the GPIO as active low.
61 In our Bluetooth example the "reset-gpios" refers to the second GpioIo()
[all …]
|
| /openbmc/phosphor-gpio-monitor/multi-presence/ |
| H A D | main.cpp | 9 * http://www.apache.org/licenses/LICENSE-2.0
23 #include <phosphor-logging/lg2.hpp>
29 namespace gpio namespace
37 /**< Enable pull-up. */
39 /**< Enable pull-down. */
48 CLI::App app{"Monitor gpio presence status"}; in main()
53 app.add_option("-c,--config", gpioFileName, "Name of config json file") in main()
54 ->required() in main()
55 ->check(CLI::ExistingFile); in main()
67 /* Get list of gpio config details from json file */ in main()
[all …]
|