| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/fpga/ |
| 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
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
31 spi-cpha: true
[all …]
|
| D | lattice,sysconfig.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vladimir Georgiev <v.georgiev@metrotek.ru>
17 Programming of ECP5 is done by writing uncompressed bitstream image in .bit
23 - lattice,sysconfig-ecp5
28 program-gpios:
34 init-gpios:
40 done-gpios:
42 A GPIO line connected to DONE (active high) pin of the device.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/fpga/ |
| D | xilinx-slave-serial.txt | 3 Xilinx Spartan-6 and 7 Series FPGAs support a method of loading the
9 - https://www.xilinx.com/support/documentation/user_guides/ug380.pdf
10 - https://www.xilinx.com/support/documentation/user_guides/ug470_7Series_Config.pdf
11 - https://www.xilinx.com/support/documentation/application_notes/xapp583-fpga-configuration.pdf
14 - compatible: should contain "xlnx,fpga-slave-serial"
15 - reg: spi chip select of the FPGA
16 - prog_b-gpios: config pin (referred to as PROGRAM_B in the manual)
17 - done-gpios: config status pin (referred to as DONE in the manual)
20 - init-b-gpios: initialization status and configuration error pin
25 fpga-region0 {
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/i2c/ |
| D | i2c-arb-gpio-challenge.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-arb-gpio-challenge.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: GPIO-based I2C Arbitration Using a Challenge & Response Mechanism
10 - Doug Anderson <dianders@chromium.org>
11 - Peter Rosin <peda@axentia.se>
17 In many cases using GPIOs to arbitrate is not needed and a design can use the
18 standard I2C multi-master rules. Using GPIOs is generally useful in the case
30 others can see. These are all active low with pull-ups enabled. We'll
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/gpio/ |
| 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 gpio-legacy.txt.
10 Guidelines for GPIOs consumers
15 obtain and use GPIOs are available by including the following file:
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
40 Obtaining and Disposing GPIOs
[all …]
|
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/ |
| D | i2c-arb-gpio-challenge.txt | 1 GPIO-based I2C Arbitration Using a Challenge & Response Mechanism
6 In many cases using GPIOs to arbitrate is not needed and a design can use
7 the standard I2C multi-master rules. Using GPIOs is generally useful in
21 others can see. These are all active low with pull-ups enabled. We'll
24 - OUR_CLAIM: output from us signaling to other hosts that we want the bus
25 - THEIR_CLAIMS: output from others signaling that they want the bus
29 done with an example.
36 done.
43 - compatible: i2c-arb-gpio-challenge
44 - our-claim-gpio: The GPIO that we use to claim the bus.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/gpio/ |
| 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::
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
40 Obtaining and Disposing GPIOs
[all …]
|
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/ |
| D | gpio-properties.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 allows names to be given to GPIOs (and other things as well) returned
13 With _DSD we can now query GPIOs using a name instead of an integer
16 // Bluetooth device with reset and shutdown GPIOs
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 }},
61 In our Bluetooth example the "reset-gpios" refers to the second GpioIo()
75 assuming non-active (Polarity = !Pull Bias)
77 Down High as low, assuming non-active
[all …]
|
| /kernel/linux/linux-6.6/arch/powerpc/boot/dts/ |
| D | ac14xx.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later
14 #address-cells = <1>;
15 #size-cells = <1>;
26 timebase-frequency = <40000000>; /* 40 MHz (csb/4) */
27 bus-frequency = <160000000>; /* 160 MHz csb bus */
28 clock-frequency = <400000000>; /* 400 MHz ppc core */
49 compatible = "cfi-flash";
51 #address-cells = <1>;
52 #size-cells = <1>;
53 bank-width = <2>;
[all …]
|
| /kernel/linux/linux-5.10/arch/powerpc/boot/dts/ |
| D | ac14xx.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later
14 #address-cells = <1>;
15 #size-cells = <1>;
26 timebase-frequency = <40000000>; /* 40 MHz (csb/4) */
27 bus-frequency = <160000000>; /* 160 MHz csb bus */
28 clock-frequency = <400000000>; /* 400 MHz ppc core */
49 compatible = "cfi-flash";
51 #address-cells = <1>;
52 #size-cells = <1>;
53 bank-width = <2>;
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/touchscreen/ |
| D | chipone_icn8318.txt | 4 - compatible : "chipone,icn8318"
5 - reg : I2C slave address of the chip (0x40)
6 - interrupts : interrupt specification for the icn8318 interrupt
7 - wake-gpios : GPIO specification for the WAKE input
8 - touchscreen-size-x : horizontal resolution of touchscreen (in pixels)
9 - touchscreen-size-y : vertical resolution of touchscreen (in pixels)
12 - pinctrl-names : should be "default"
13 - pinctrl-0: : a phandle pointing to the pin settings for the
14 control gpios
15 - touchscreen-fuzz-x : horizontal noise value of the absolute input
[all …]
|
| /kernel/linux/linux-6.6/drivers/gpio/ |
| D | gpio-twl4030.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * Access to GPIOs on TWL4030/TPS659x0 chips
5 * Copyright (C) 2006-2007 Texas Instruments, Inc.
8 * Code re-arranged and cleaned up by:
30 * The GPIO "subchip" supports 18 GPIOs which can be configured as
37 * There are also two LED pins used sometimes as output-only GPIOs.
52 /* Mask for GPIO registers when aggregated into a 32-bit integer */
66 /*----------------------------------------------------------------------*/
76 /*----------------------------------------------------------------------*/
101 /*----------------------------------------------------------------------*/
[all …]
|
| D | gpio-davinci.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
5 * Copyright (c) 2006-2007 David Brownell
22 #include <linux/platform_data/gpio-davinci.h>
45 #define BINTEN 0x8 /* GPIO Interrupt Per-Bank Enable Register */
84 /*--------------------------------------------------------------------------*/
97 g = d->regs[bank]; in __davinci_direction()
98 spin_lock_irqsave(&d->lock, flags); in __davinci_direction()
99 temp = readl_relaxed(&g->dir); in __davinci_direction()
102 writel_relaxed(mask, value ? &g->set_data : &g->clr_data); in __davinci_direction()
106 writel_relaxed(temp, &g->dir); in __davinci_direction()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mfd/ |
| D | rohm,bd9576-pmic.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mfd/rohm,bd9576-pmic.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <mazziesaccount@gmail.com>
14 powering the R-Car series processors.
21 - rohm,bd9576
22 - rohm,bd9573
32 rohm,vout1-en-low:
35 controlled by a GPIO. This is dictated by state of vout1-en pin during
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpio/ |
| D | gpio-twl4030.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * Access to GPIOs on TWL4030/TPS659x0 chips
5 * Copyright (C) 2006-2007 Texas Instruments, Inc.
8 * Code re-arranged and cleaned up by:
28 * The GPIO "subchip" supports 18 GPIOs which can be configured as
35 * There are also two LED pins used sometimes as output-only GPIOs.
50 /* Mask for GPIO registers when aggregated into a 32-bit integer */
64 /*----------------------------------------------------------------------*/
74 /*----------------------------------------------------------------------*/
99 /*----------------------------------------------------------------------*/
[all …]
|
| D | gpio-davinci.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
5 * Copyright (c) 2006-2007 David Brownell
22 #include <linux/platform_data/gpio-davinci.h>
26 #include <asm-generic/gpio.h>
46 #define BINTEN 0x8 /* GPIO Interrupt Per-Bank Enable Register */
83 /*--------------------------------------------------------------------------*/
96 g = d->regs[bank]; in __davinci_direction()
97 spin_lock_irqsave(&d->lock, flags); in __davinci_direction()
98 temp = readl_relaxed(&g->dir); in __davinci_direction()
101 writel_relaxed(mask, value ? &g->set_data : &g->clr_data); in __davinci_direction()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/firmware-guide/acpi/ |
| D | gpio-properties.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 allows names to be given to GPIOs (and other things as well) returned
13 With _DSD we can now query GPIOs using a name instead of an integer
16 // Bluetooth device with reset and shutdown GPIOs
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 } },
61 In our Bluetooth example the "reset-gpios" refers to the second GpioIo()
70 +-------------+-------------+-----------------------------------------------+
74 +-------------+-------------+-----------------------------------------------+
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-mvebu/ |
| D | pm-board.c | 2 * Board-level suspend/resume support.
4 * Copyright (C) 2014-2015 Marvell
6 * Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
34 /* Put 001 as value on the GPIOs */ in mvebu_armada_pm_enter()
41 /* Prepare writing 111 to the GPIOs */ in mvebu_armada_pm_enter()
85 if (!of_machine_is_compatible("marvell,axp-gp")) in mvebu_armada_pm_init()
86 return -ENODEV; in mvebu_armada_pm_init()
90 return -ENODEV; in mvebu_armada_pm_init()
96 pic_gpios[i] = of_get_named_gpio(np, "ctrl-gpios", i); in mvebu_armada_pm_init()
98 ret = -ENODEV; in mvebu_armada_pm_init()
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/mach-s3c/ |
| D | pm.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
14 #include "pm-common.h"
40 /* per-cpu sleep functions */
68 * s3c_pm_configure_extint() - ensure pins are correctly set for IRQ
77 * samsung_pm_restore_gpios() - restore the state of the gpios after sleep.
81 * resume code has done.
86 * samsung_pm_save_gpios() - save the state of the GPIOs for restoring after sleep.
|
| /kernel/linux/linux-5.10/Documentation/driver-api/serial/ |
| D | driver.rst | 10 The reference implementation is contained within amba-pl011.c.
15 --------------------------------
25 ---------------
38 -------
41 necessary locking using port->lock. There are some exceptions (which
44 There are two locks. A per-port spinlock, and an overall semaphore.
46 From the core driver perspective, the port->lock locks the following
49 port->mctrl
50 port->icount
51 port->state->xmit.head (circ_buf->head)
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/mach-mvebu/ |
| D | pm-board.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * Board-level suspend/resume support.
5 * Copyright (C) 2014-2015 Marvell
7 * Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
31 /* Put 001 as value on the GPIOs */ in mvebu_armada_pm_enter()
38 /* Prepare writing 111 to the GPIOs */ in mvebu_armada_pm_enter()
82 if (!of_machine_is_compatible("marvell,axp-gp")) in mvebu_armada_pm_init()
83 return -ENODEV; in mvebu_armada_pm_init()
87 return -ENODEV; in mvebu_armada_pm_init()
93 name = kasprintf(GFP_KERNEL, "pic-pin%d", i); in mvebu_armada_pm_init()
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/microchip/ |
| D | at91-sama5d27_wlsom1_ek.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3 * at91-sama5d27_wlsom1_ek.dts - Device Tree file for SAMA5D27 WLSOM1 EK
9 /dts-v1/;
10 #include "at91-sama5d27_wlsom1.dtsi"
11 #include <dt-bindings/input/input.h>
15 …compatible = "microchip,sama5d27-wlsom1-ek", "microchip,sama5d27-wlsom1", "atmel,sama5d27", "atmel…
26 stdout-path = "serial0:115200n8";
29 gpio-keys {
30 compatible = "gpio-keys";
32 pinctrl-names = "default";
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | at91-sama5d27_wlsom1_ek.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3 * at91-sama5d27_wlsom1_ek.dts - Device Tree file for SAMA5D27 WLSOM1 EK
9 /dts-v1/;
10 #include "at91-sama5d27_wlsom1.dtsi"
11 #include <dt-bindings/input/input.h>
15 …compatible = "microchip,sama5d27-wlsom1-ek", "microchip,sama5d27-wlsom1", "atmel,sama5d27", "atmel…
26 stdout-path = "serial0:115200n8";
30 compatible = "gpio-keys";
32 pinctrl-names = "default";
33 pinctrl-0 = <&pinctrl_key_gpio_default>;
[all …]
|