/openbmc/linux/arch/arm64/boot/dts/microchip/ |
H A D | sparx5_pcb134_board.dtsi | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT) 6 /dts-v1/; 10 gpio-restart { 11 compatible = "gpio-restart"; 12 gpios = <&gpio 37 GPIO_ACTIVE_LOW>; 17 compatible = "gpio-leds"; 20 gpios = <&sgpio_out0 8 0 GPIO_ACTIVE_LOW>; 24 gpios = <&sgpio_out0 8 1 GPIO_ACTIVE_LOW>; 28 gpios = <&sgpio_out0 9 0 GPIO_ACTIVE_LOW>; 32 gpios = <&sgpio_out0 9 1 GPIO_ACTIVE_LOW>; [all …]
|
/openbmc/linux/drivers/tty/serial/ |
H A D | serial_mctrl_gpio.c | 1 // SPDX-License-Identifier: GPL-2.0+ 46 * mctrl_gpio_set - set gpios according to mctrl state 47 * @gpios: gpios to set 50 * Set the gpios according to the mctrl state. 52 void mctrl_gpio_set(struct mctrl_gpios *gpios, unsigned int mctrl) in mctrl_gpio_set() argument 59 if (gpios == NULL) in mctrl_gpio_set() 63 if (gpios->gpio[i] && mctrl_gpio_flags_is_dir_out(i)) { in mctrl_gpio_set() 64 desc_array[count] = gpios->gpio[i]; in mctrl_gpio_set() 74 * mctrl_gpio_to_gpiod - obtain gpio_desc of modem line index 75 * @gpios: gpios to look into [all …]
|
/openbmc/linux/Documentation/driver-api/gpio/ |
H A D | legacy.rst | 13 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled 18 which GPIOs. Drivers can be written generically, so that board setup code 21 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every 22 non-dedicated pin can be configured as a GPIO; and most chips have at least 24 provide GPIOs; multifunction chips like power managers, and audio codecs 27 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS 30 The exact capabilities of GPIOs vary between systems. Common options: 32 - Output values are writable (high=1, low=0). Some chips also have 34 value might be driven ... supporting "wire-OR" and similar schemes 37 - Input values are likewise readable (1, 0). Some chips support readback [all …]
|
H A D | board.rst | 5 This document explains how GPIOs can be assigned to given devices and functions. 7 Note that it only applies to the new descriptor-based interface. For a 8 description of the deprecated integer-based GPIO interface please refer to 15 Kconfig. Then, how GPIOs are mapped depends on what the platform uses to 20 ----------- 21 GPIOs can easily be mapped to devices and functions in the device tree. The 22 exact way to do it depends on the GPIO controller providing the GPIOs, see the 25 GPIOs mappings are defined in the consumer device's node, in a property named 26 <function>-gpios, where <function> is the function the driver will request 32 led-gpios = <&gpio 15 GPIO_ACTIVE_HIGH>, /* red */ [all …]
|
H A D | consumer.rst | 6 it describes the new descriptor-based interface. For a description of the 7 deprecated integer-based GPIO interface please refer to legacy.rst. 10 Guidelines for GPIOs consumers 15 obtain and use GPIOs are available by including the following file:: 19 There are static inline stubs for all functions in the header file in the case 23 - Simple compile coverage with e.g. COMPILE_TEST - it does not matter that 27 - Truly optional GPIOLIB support - where the driver does not really make use 28 of the GPIOs on certain compile-time configurations for certain systems, but 29 will use it under other compile-time configurations. In this case the 33 All the functions that work with the descriptor-based GPIO interface are [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/power/supply/ |
H A D | gpio-charger.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/power/supply/gpio-charger.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: simple battery chargers only communicating through GPIOs 10 - Sebastian Reichel <sre@kernel.org> 14 autonomously, only providing some status GPIOs and possibly some 15 GPIOs for limited control over the charging process. 19 const: gpio-charger 21 charger-type: [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/usb/ |
H A D | brcm,usb-pinmap.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/usb/brcm,usb-pinmap.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Al Cooper <alcooperx@gmail.com> 15 - const: brcm,usb-pinmap 22 description: Interrupt for signals mirrored to out-gpios. 24 in-gpios: 29 brcm,in-functions: 30 $ref: /schemas/types.yaml#/definitions/string-array [all …]
|
/openbmc/linux/sound/soc/ |
H A D | soc-jack.c | 1 // SPDX-License-Identifier: GPL-2.0+ 3 // soc-jack.c -- ALSA SoC jack handling 21 * snd_soc_jack_report - Report the current status for a jack 40 if (!jack || !jack->jack) in snd_soc_jack_report() 44 dapm = &jack->card->dapm; in snd_soc_jack_report() 46 mutex_lock(&jack->mutex); in snd_soc_jack_report() 48 jack->status &= ~mask; in snd_soc_jack_report() 49 jack->status |= status & mask; in snd_soc_jack_report() 53 list_for_each_entry(pin, &jack->pins, list) { in snd_soc_jack_report() 54 int enable = pin->mask & jack->status; in snd_soc_jack_report() [all …]
|
/openbmc/u-boot/doc/device-tree-bindings/gpio/ |
H A D | gpio.txt | 4 1) gpios property 5 ----------------- 7 Nodes that makes use of GPIOs should specify them using one or more 8 properties, each containing a 'gpio-list': 10 gpio-list ::= <single-gpio> [gpio-list] 11 single-gpio ::= <gpio-phandle> <gpio-specifier> 12 gpio-phandle : phandle to gpio controller node 13 gpio-specifier : Array of #gpio-cells specifying specific gpio 16 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose 17 of this GPIO for the device. While a non-existent <name> is considered valid [all …]
|
/openbmc/skeleton/libopenbmc_intf/ |
H A D | gpio_configs.c | 6 * you may not use this file except in compliance with the License. 9 * http://www.apache.org/licenses/LICENSE-2.0 11 * Unless required by applicable law or agreed to in writing, software 29 * Loads the GPIO information into the gpios->power_gpio structure 32 * @param gpios - the structure where GpioConfigs.power_gpio will 33 * be filled in. 34 * @param gpio_configs - cJSON pointer to the GPIO JSON 36 void read_power_gpios(GpioConfigs* gpios, const cJSON* gpio_configs) in read_power_gpios() argument 44 /* PGOOD - required */ in read_power_gpios() 49 gpios->power_gpio.power_good_in.name = g_strdup(pgood->valuestring); in read_power_gpios() [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/gpio/ |
H A D | gpio-max3191x.txt | 4 - compatible: Must be one of: 11 - reg: Chip select number. 12 - gpio-controller: Marks the device node as a GPIO controller. 13 - #gpio-cells: Should be two. For consumer use see gpio.txt. 16 - #daisy-chained-devices: 17 Number of chips in the daisy-chain (default is 1). 18 - maxim,modesel-gpios: GPIO pins to configure modesel of each chip. 19 The number of GPIOs must equal "#daisy-chained-devices" 22 - maxim,fault-gpios: GPIO pins to read fault of each chip. 23 The number of GPIOs must equal "#daisy-chained-devices" [all …]
|
H A D | gpio.txt | 4 1) gpios property 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 9 for compatibility reasons (resolving to the "gpios" property), it is not allowed 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 15 cases should they contain more than one. If your device uses several GPIOs with 17 meaningful name. The only case where an array of GPIOs is accepted is when 18 several GPIOs serve the same function (e.g. a parallel data line). [all …]
|
/openbmc/u-boot/drivers/gpio/ |
H A D | Kconfig | 14 particular GPIOs that they provide. The uclass interface 15 is defined in include/asm-generic/gpio.h. 24 is a mechanism providing automatic GPIO request and config- 25 uration as part of the gpio-controller's driver probe function. 28 bool "Enable GPIO hog support in SPL" 32 Enable gpio hog support in SPL 34 is a mechanism providing automatic GPIO request and config- 35 uration as part of the gpio-controller's driver probe function. 64 lines. Each I/O line may be dedicated as a general-purpose 68 responsible for the general-purpose I/O. [all …]
|
/openbmc/linux/drivers/gpio/ |
H A D | gpiolib-of.c | 1 // SPDX-License-Identifier: GPL-2.0+ 5 * Copyright (c) 2007-2008 MontaVista Software, Inc. 26 #include "gpiolib-of.h" 29 * This is Linux-specific flags. By default controllers' and Linux' mapping 31 * Linux-specific in their .xlate callback. Though, 1:1 mapping is recommended. 44 * of_gpio_named_count() - Count GPIOs for a device 45 * @np: device node to count GPIOs for 48 * The function returns the count of GPIOs specified for a node. 50 * Number of gpios defined in property, 51 * -EINVAL for an incorrectly formed gpios property, or [all …]
|
H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 18 int "Maximum number of GPIOs for fast path" 47 this symbol, but new drivers should use the generic gpio-regmap 55 These checks help ensure that GPIOs have been properly initialized 57 non-sleeping contexts. They can make bitbanged serial protocols 66 Say Y here to add the legacy sysfs interface for GPIOs. 78 for GPIOs. The character device allows userspace to control GPIOs 106 # put drivers in the right section, in alphabetical order 118 Enables support for the idio-16 library functions. The idio-16 library 120 ACCES IDIO-16 family such as the 104-IDIO-16 and the PCI-IDIO-16. [all …]
|
/openbmc/u-boot/include/asm-generic/ |
H A D | gpio.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */ 15 * Generic GPIO API for U-Boot 17 * -- 20 * - gpio_request_by_name() 21 * - dm_gpio_get_value() etc. 24 * -- 26 * GPIOs are numbered from 0 to GPIO_COUNT-1 which value is defined 35 * In some cases the operation may fail, for example if the GPIO number 37 * being used by another function. In that case, functions may return 38 * an error value of -1. [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/auxdisplay/ |
H A D | hit,hd44780.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Geert Uytterhoeven <geert@linux-m68k.org> 15 interface, which can be used in either 4-bit or 8-bit mode. By using a 24 data-gpios: 26 GPIO pins connected to the data signal lines DB0-DB7 (8-bit mode) or 27 DB4-DB7 (4-bit mode) of the LCD Controller's bus interface. 29 - maxItems: 4 30 - maxItems: 8 [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/display/panel/ |
H A D | sharp,ls037v7dw01.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: SHARP LS037V7DW01 TFT-LCD panel 10 This panel can have zero to five GPIOs to configure to change configuration 12 configured with external pulls, all the GPIOs are considered optional with holes 13 in the array. 16 - Tony Lindgren <tony@atomide.com> 19 - $ref: panel-common.yaml# 26 enable-gpios: true [all …]
|
/openbmc/linux/arch/arm/boot/dts/allwinner/ |
H A D | sun4i-a10-inet9f-rev03.dts | 4 * This file is dual-licensed: you can use it either under the terms 14 * This file is distributed in the hope that it will be useful, 23 * files (the "Software"), to deal in the Software without 31 * included in all copies or substantial portions of the Software. 36 * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT 38 * WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING 39 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR 40 * OTHER DEALINGS IN THE SOFTWARE. 43 /dts-v1/; 44 #include "sun4i-a10.dtsi" [all …]
|
H A D | sun5i-a13-utoo-p66.dts | 4 * This file is dual-licensed: you can use it either under the terms 14 * This file is distributed in the hope that it will be useful, 23 * files (the "Software"), to deal in the Software without 31 * included in all copies or substantial portions of the Software. 36 * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT 38 * WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING 39 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR 40 * OTHER DEALINGS IN THE SOFTWARE. 43 /dts-v1/; 44 #include "sun5i-a13.dtsi" [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/fpga/ |
H A D | xlnx,fpga-slave-serial.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/fpga/xlnx,fpga-slave-serial.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Nava kishore Manne <nava.kishore.manne@amd.com> 13 Xilinx Spartan-6 and 7 Series FPGAs support a method of loading the bitstream 15 not technically SPI, and might require extra circuits in order to play nicely 21 https://www.xilinx.com/support/documentation/application_notes/xapp583-fpga-configuration.pdf 24 - $ref: /schemas/spi/spi-peripheral-props.yaml# 29 - xlnx,fpga-slave-serial [all …]
|
/openbmc/u-boot/arch/arm/dts/ |
H A D | sun4i-a10-inet9f-rev03.dts | 4 * This file is dual-licensed: you can use it either under the terms 14 * This file is distributed in the hope that it will be useful, 23 * files (the "Software"), to deal in the Software without 31 * included in all copies or substantial portions of the Software. 36 * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT 38 * WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING 39 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR 40 * OTHER DEALINGS IN THE SOFTWARE. 43 /dts-v1/; 44 #include "sun4i-a10.dtsi" [all …]
|
/openbmc/linux/arch/arm/boot/dts/marvell/ |
H A D | orion5x-linkstation-lschl.dts | 2 * Device Tree file for Buffalo Linkstation LS-CHLv3 5 * Copyright (C) 2015-2017 8 * This file is dual-licensed: you can use it either under the terms 18 * This file is distributed in the hope that it will be useful, 27 * files (the "Software"), to deal in the Software without 35 * included in all copies or substantial portions of the Software. 40 * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT 42 * WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING 43 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR 44 * OTHER DEALINGS IN THE SOFTWARE. [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/net/ |
H A D | broadcom-bluetooth.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/net/broadcom-bluetooth.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Linus Walleij <linus.walleij@linaro.org> 13 This binding describes Broadcom UART-attached bluetooth chips. 18 - brcm,bcm20702a1 19 - brcm,bcm4329-bt 20 - brcm,bcm4330-bt 21 - brcm,bcm4334-bt [all …]
|
/openbmc/linux/arch/arm/boot/dts/broadcom/ |
H A D | bcm4709-netgear-r8000.dts | 9 * copyright notice and this permission notice appear in all copies. 13 * AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, 15 * LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE 16 * OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR 20 /dts-v1/; 23 #include "bcm5301x-nand-cs0-bch8.dtsi" 40 compatible = "gpio-leds"; 42 led-power-white { 44 gpios = <&chipcommon 2 GPIO_ACTIVE_LOW>; 45 linux,default-trigger = "default-on"; [all …]
|