Lines Matching +full:zynq +full:- +full:can +full:- +full:1
1 # SPDX-License-Identifier: GPL-2.0-only
60 non-sleeping contexts. They can make bitbanged serial protocols
81 numberspace-based functionalities of the sysfs interface.
97 bool "Support GPIO ABI Version 1"
101 Say Y here to support version 1 of the GPIO CDEV ABI.
137 Enables support for the idio-16 library functions. The idio-16 library
139 ACCES IDIO-16 family such as the 104-IDIO-16 and the PCI-IDIO-16.
141 If built as a module its name will be gpio-idio-16.
147 tristate "GPIO driver for 74xx-ICs with MMIO access"
151 Say yes here to support GPIO functionality for 74xx-compatible ICs
153 1 bit: 741G125 (Input), 741G74 (Output)
166 If driver is built as a module it will be called gpio-altera.
205 # Make sure not 'y' when RASPBERRYPI_FIRMWARE is 'm'. This can only
341 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
344 Say yes here to support basic platform_device memory-mapped GPIO controllers.
347 tristate "Intel Granite Rapids-D vGPIO support"
354 - Intel Granite Rapids-D
362 be called gpio-graniterapids.
381 This GPIO controller supports double-edge interrupt and multi-core
399 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
429 bool "Loongson-2/3 GPIO support"
432 Driver for GPIO functionality on Loongson-2F/3A/3B processors.
482 created by attaching a 16-bit latch to the bus.
536 It handles up to 32 GPIOs per bank, that can all be interrupt sources.
552 Say yes here to support the on-chip GPIO lines on the OCTEON
586 tristate "Renesas R-Car and RZ/G GPIO support"
590 Say yes here to support GPIO on Renesas R-Car or RZ/G SoCs.
610 are grouped in four 8-bit wide ports.
617 A 32-bit single register GPIO fixed in/out implementation. This
618 can be used to represent any register as a set of GPIO signals.
651 PIOBU pins on the SAMA5D2 can be used as GPIOs.
653 maintain their value during backup/self-refresh.
671 via a SIOX bus and have a number of fixed-direction I/O lines.
679 This is a single-register MMIO GPIO driver for complex cases
714 that can be up to 24 bits. This peripheral is aimed at driving LEDs.
715 Some of the GPIOs/LEDs can be auto updated by the SoC with DSL and
730 - Elkhart Lake
731 - Merrifield
733 If built as a module its name will be gpio-tangier.
763 tristate "TS-4800 DIO blocks and compatibles"
768 This driver support TS-4800 FPGA GPIO controllers.
771 tristate "Cavium ThunderX/OCTEON-TX GPIO"
778 Say yes here to support the on-chip GPIO lines on the ThunderX
779 and OCTEON-TX families of SoCs.
816 bool "APM X-Gene GPIO controller support"
819 This driver is to support the GPIO block within the APM X-Gene SoC
825 tristate "APM X-Gene GPIO standby controller support"
831 This driver supports the GPIO block within the APM X-Gene
866 tristate "Xilinx Zynq GPIO support"
870 Say yes here to support Xilinx Zynq GPIO controller.
873 tristate "ZynqMP ps-mode pin GPIO configuration driver"
877 Say yes here to support the ZynqMP ps-mode pin GPIO configuration
880 This ps-mode pin GPIO driver is based on GPIO framework. PS_MODE
881 is 4-bits boot mode pins. It sets and gets the status of
882 the ps-mode pin. Every pin can be configured as input/output.
892 tristate "GPIO support for AMD Fusion Controller Hub (G-series SOCs)"
895 as found on G-series SOCs (e.g. GX-412TC).
898 needs to be provided with platform-specific configuration.
909 ARMv7-based SoCs.
918 IDT 79RC3243X-based devices like Mikrotik RB532.
921 be called gpio-idt3243x.
925 menu "Port-mapped I/O GPIO drivers"
951 If built as a module its name will be gpio-i8255.
954 tristate "ACCES 104-DIO-48E GPIO support"
963 Enables GPIO support for the ACCES 104-DIO-48E series (104-DIO-48E,
964 104-DIO-24E). The base port addresses for the devices may be
969 tristate "ACCES 104-IDIO-16 GPIO support"
975 Enables GPIO support for the ACCES 104-IDIO-16 family (104-IDIO-16,
976 104-IDIO-16E, 104-IDO-16, 104-IDIO-8, 104-IDIO-8E, 104-IDO-8). The
982 tristate "ACCES 104-IDI-48 GPIO support"
990 Enables GPIO support for the ACCES 104-IDI-48 family (104-IDI-48A,
991 104-IDI-48AC, 104-IDI-48B, 104-IDI-48BC). The base port addresses for
997 tristate "Fintek and Nuvoton Super-I/O GPIO support"
999 This option enables support for GPIOs found on Fintek Super-I/O
1001 As well as Nuvoton Super-I/O chip NCT6126D.
1004 be called f7188x-gpio.
1007 tristate "Diamond Systems GPIO-MM GPIO support"
1013 Enables GPIO support for the Diamond Systems GPIO-MM and GPIO-MM-12.
1015 The Diamond Systems GPIO-MM device features 48 lines of digital I/O
1048 active during S3. The suspend-powered GPIOs can be used to wake the
1049 system from the Suspend-to-RAM state.
1055 Twenty-one are powered by the core power rail and 9 from the
1068 be called gpio-sch311x.
1071 tristate "TS-5500 DIO blocks and compatibles"
1076 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
1089 boot-time parameter "gpio_winbond.gpios" with a bitmask of GPIO
1090 ports to enable (bit 0 is GPIO1, bit 1 is GPIO2, etc.).
1093 be called gpio-winbond.
1114 tristate "Avionic Design N-bit GPIO expander"
1133 be called gpio-fxl6408.
1140 GPIO driver for ADI DS4520 I2C-based GPIO expander.
1144 be called gpio-ds4520.
1151 Expander. This is used at least on the Cambria GW2358-4.
1157 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
1160 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
1162 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
1164 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
1189 Say yes here to provide access to several register-oriented
1218 tristate "PCA9570 4-Bit I2C GPO expander"
1223 be called gpio-pca9570.
1230 Say yes here to provide access to most "quasi-bidirectional" I2C
1244 can then be used from drivers and other kernel code, just like
1247 This driver provides an in-kernel interface to those GPIOs using
1248 platform-neutral GPIO calls.
1251 tristate "TPIC2810 8-Bit I2C GPO expander"
1256 be called gpio-tpic2810.
1264 Series supported include TS-4100, TS-4900, TS-7970 and TS-7990.
1274 This option enables support for on-chip GPIO found
1306 This driver can also be built as a module. If so, the module
1307 will be called gpio-bd71815.
1318 This driver can also be built as a module. If so, the module
1319 will be called gpio-bd71828.
1326 available on the ROHM PMIC in total, both of which can also
1329 This driver can also be built as a module. If so, the module
1330 will be called gpio-bd9571mwv.
1339 This driver can also be built as a module. If so, the module will be
1340 called gpio-cgbc.
1349 This driver can also be built as a module. If so, the module
1350 will be called gpio-cros-ec.
1359 Say Yes if you have a Intel SoC-based tablet with Crystal Cove PMIC
1362 This driver can also be built as a module. If so, the module will be
1363 called gpio-crystalcove.
1371 can be used for quite a number of things. The CS5535/6 is found on
1388 The Dialog DA9055 PMIC chip has 3 GPIO pins that can be
1391 If driver is built as a module it will be called gpio-da9055.
1402 This driver can also be built as a module. If so, the module
1403 will be called gpio-dln2.
1422 be called gpio-elkhartlake.
1425 tristate "Janz VMOD-TTL Digital IO Module"
1428 This enables support for the Janz VMOD-TTL Digital IO module.
1439 This driver can also be built as a module. If so, the module will be
1440 called gpio-kempld.
1451 This driver can also be built as a module. If so, the module
1452 will be called gpio-ljca.
1459 LP3943 can be used as a GPIO expander which provides up to 16 GPIOs.
1469 This driver can also be built as a module. If so, the module will be
1470 called gpio-lp873x.
1479 This driver can also be built as a module. If so, the module will be
1480 called gpio-lp87565.
1489 This driver can also be built as a module. If so, the module will be
1490 called gpio-macsmc.
1507 This driver can also be built as a module. If so, the module will be
1508 called gpio-max7360.
1516 MAX77620 PMIC has 8 pins that can be configured as GPIOs. The
1525 These chips have a single pin that can be configured as GPIO.
1535 which can also generate interrupts.
1537 This driver can also be built as a module. If so, the module will be
1538 called gpio-max77759.
1546 This driver supports 8 GPIO pins per bank that can all be interrupt
1549 This driver can also be built as a module. If so, the module will be
1550 called gpio-nct6694.
1594 This driver can also be built as a module. If so, the module will be
1595 called gpio-sl28cpld.
1629 they are input-only or output-only type.
1631 This driver can also be built as a module. If so, the
1632 module will be called gpio-tn48m.
1656 is statically configured by NVM. GPIO0 can't be used as a generic
1658 MULTI_DEVICE_EN=1.
1660 This driver can also be built as a module. If so, the module will be
1689 There are 7 GPIOs and few sensor-related GPIOs supported
1690 by the TPS68470. While the 7 GPIOs can be configured as
1695 tristate "TQ-Systems TQMx86 GPIO"
1706 Say yes here to access the GPIO signals of various multi-function
1723 Say Yes if you have an Intel SoC-based tablet with Whiskey Cove PMIC
1726 This driver can also be built as a module. If so, the module will be
1727 called gpio-wcove.
1760 The AMD 8111 southbridge contains 32 GPIO pins which can be used.
1772 The BT8xx frame grabber chip has 24 GPIO pins that can be abused
1775 This chip can be found on Miro, Hauppauge and STB TV-cards.
1780 Documentation/driver-api/gpio/bt8xxgpio.rst
1815 This controller should be used in parallel with pinctrl-mlxbf3 to
1817 This driver can also be built as a module called mlxbf3-gpio.
1825 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH (Input/Output
1826 Hub) which is for IVI (In-Vehicle Infotainment) use.
1827 This driver can access the IOH's GPIO device.
1836 This driver can access PCH GPIO device.
1838 This driver also can be used for LAPIS Semiconductor IOH (Input/
1846 tristate "ACCES PCI-IDIO-16 GPIO support"
1850 Enables GPIO support for the ACCES PCI-IDIO-16. An interrupt is
1856 tristate "ACCES PCIe-IDIO-24 GPIO support"
1862 Enables GPIO support for the ACCES PCIe-IDIO-24 family (PCIe-IDIO-24,
1863 PCIe-IDI-24, PCIe-IDO-24, PCIe-IDIO-12). An interrupt is generated
1869 tristate "RDC R-321x GPIO support"
1890 tristate "74x164 serial-in/parallel-out 8-bits shift register"
1892 Driver for 74x164 compatible serial-in/parallel-out 8-outputs
1893 shift registers. This driver can be used to provide access
1901 MAX31953 and MAX31963 industrial serializer, a daisy-chainable
1910 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
1913 tristate "Freescale MC33880 high-side/low-side switch"
1915 SPI driver for Freescale MC33880 high-side/low-side switch.
1919 tristate "Generic parallel-in/serial-out shift register"
1921 GPIO driver for SPI compatible parallel-in/serial-out shift
1925 tristate "EXAR XRA1403 16-bit GPIO expander"
1928 GPIO driver for EXAR XRA1403 16-bit SPI-based GPIO expander.
1937 so that phylink can use corresponding GPIOs.
1959 GPIO driver for FTDI's MPSSE interface. These can do input and
1970 This driver can also be built as a module. If so, the module
1984 This can serve the following purposes:
1985 - Assign permissions for a collection of GPIO lines to a user,
1986 - Export a collection of GPIO lines to a virtual machine,
1987 - Provide a generic driver for a GPIO-operated device in an
2001 This module is DEPRECATED. Please consider using gpio-sim instead.
2006 tools/testing/selftests/gpio/gpio-mockup.sh. Reference the usage in
2014 Say Y here to enable guest support for virtio-based GPIO controllers.
2016 These virtual GPIOs can be routed to real GPIOs or attached to
2025 This enables the GPIO simulator - a configfs-based GPIO testing
2029 tristate "Proxy driver for non-exclusive GPIOs"
2034 This enables the GPIO shared proxy driver - an abstraction layer
2046 GPIOs. Use the 'tools/gpio/gpio-sloppy-logic-analyzer' script with
2049 analyzer which can be affected by latencies, non-deterministic code
2054 'gpio-sloppy-logic-analyzer'.
2063 Say Y here to enable the configurable, configfs-based virtual GPIO
2067 hot-unplug handling in GPIOLIB.