2019-05-19 12:07:45 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2008-02-05 06:28:17 +00:00
|
|
|
#
|
2011-05-20 06:40:19 +00:00
|
|
|
# GPIO infrastructure and drivers
|
2008-02-05 06:28:17 +00:00
|
|
|
#
|
|
|
|
|
|
2012-04-15 09:52:54 +00:00
|
|
|
config ARCH_HAVE_CUSTOM_GPIO_H
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Selecting this config option from the architecture Kconfig allows
|
|
|
|
|
the architecture to provide a custom asm/gpio.h implementation
|
|
|
|
|
overriding the default implementations. New uses of this are
|
|
|
|
|
strongly discouraged.
|
|
|
|
|
|
2008-07-25 08:46:11 +00:00
|
|
|
menuconfig GPIOLIB
|
|
|
|
|
bool "GPIO Support"
|
|
|
|
|
help
|
|
|
|
|
This enables GPIO support through the generic GPIO library.
|
|
|
|
|
You only need to enable this, if you also want to enable
|
2011-05-20 06:40:19 +00:00
|
|
|
one or more of the GPIO drivers below.
|
2008-07-25 08:46:11 +00:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
2008-02-05 06:28:17 +00:00
|
|
|
|
2008-07-25 08:46:11 +00:00
|
|
|
if GPIOLIB
|
2008-02-05 06:28:17 +00:00
|
|
|
|
2018-05-21 17:57:07 +00:00
|
|
|
config GPIOLIB_FASTPATH_LIMIT
|
|
|
|
|
int "Maximum number of GPIOs for fast path"
|
|
|
|
|
range 32 512
|
|
|
|
|
default 512
|
|
|
|
|
help
|
2019-03-05 00:35:31 +00:00
|
|
|
This adjusts the point at which certain APIs will switch from
|
|
|
|
|
using a stack allocated buffer to a dynamically allocated buffer.
|
2018-05-21 17:57:07 +00:00
|
|
|
|
2019-03-05 00:35:31 +00:00
|
|
|
You shouldn't need to change this unless you really need to
|
|
|
|
|
optimize either stack space or performance. Change this carefully
|
|
|
|
|
since setting an incorrect value could cause stack corruption.
|
2018-05-21 17:57:07 +00:00
|
|
|
|
2012-04-07 20:31:33 +00:00
|
|
|
config OF_GPIO
|
|
|
|
|
def_bool y
|
2016-07-05 06:46:43 +00:00
|
|
|
depends on OF
|
2016-08-16 07:58:25 +00:00
|
|
|
depends on HAS_IOMEM
|
2012-04-07 20:31:33 +00:00
|
|
|
|
2012-11-30 11:37:36 +00:00
|
|
|
config GPIO_ACPI
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on ACPI
|
|
|
|
|
|
2014-03-25 09:40:18 +00:00
|
|
|
config GPIOLIB_IRQCHIP
|
2014-05-29 14:52:46 +00:00
|
|
|
select IRQ_DOMAIN
|
2014-03-25 09:40:18 +00:00
|
|
|
bool
|
|
|
|
|
|
2008-02-05 06:28:17 +00:00
|
|
|
config DEBUG_GPIO
|
|
|
|
|
bool "Debug GPIO calls"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
Say Y here to add some extra checks and diagnostics to GPIO calls.
|
2009-01-26 10:12:25 +00:00
|
|
|
These checks help ensure that GPIOs have been properly initialized
|
|
|
|
|
before they are used, and that sleeping calls are not made from
|
|
|
|
|
non-sleeping contexts. They can make bitbanged serial protocols
|
2008-02-05 06:28:17 +00:00
|
|
|
slower. The diagnostics help catch the type of setup errors
|
|
|
|
|
that are most common when setting up new platforms or boards.
|
|
|
|
|
|
gpio: sysfs interface
This adds a simple sysfs interface for GPIOs.
/sys/class/gpio
/export ... asks the kernel to export a GPIO to userspace
/unexport ... to return a GPIO to the kernel
/gpioN ... for each exported GPIO #N
/value ... always readable, writes fail for input GPIOs
/direction ... r/w as: in, out (default low); write high, low
/gpiochipN ... for each gpiochip; #N is its first GPIO
/base ... (r/o) same as N
/label ... (r/o) descriptive, not necessarily unique
/ngpio ... (r/o) number of GPIOs; numbered N .. N+(ngpio - 1)
GPIOs claimed by kernel code may be exported by its owner using a new
gpio_export() call, which should be most useful for driver debugging.
Such exports may optionally be done without a "direction" attribute.
Userspace may ask to take over a GPIO by writing to a sysfs control file,
helping to cope with incomplete board support or other "one-off"
requirements that don't merit full kernel support:
echo 23 > /sys/class/gpio/export
... will gpio_request(23, "sysfs") and gpio_export(23);
use /sys/class/gpio/gpio-23/direction to (re)configure it,
when that GPIO can be used as both input and output.
echo 23 > /sys/class/gpio/unexport
... will gpio_free(23), when it was exported as above
The extra D-space footprint is a few hundred bytes, except for the sysfs
resources associated with each exported GPIO. The additional I-space
footprint is about two thirds of the current size of gpiolib (!). Since
no /dev node creation is involved, no "udev" support is needed.
Related changes:
* This adds a device pointer to "struct gpio_chip". When GPIO
providers initialize that, sysfs gpio class devices become children of
that device instead of being "virtual" devices.
* The (few) gpio_chip providers which have such a device node have
been updated.
* Some gpio_chip drivers also needed to update their module "owner"
field ... for which missing kerneldoc was added.
* Some gpio_chips don't support input GPIOs. Those GPIOs are now
flagged appropriately when the chip is registered.
Based on previous patches, and discussion both on and off LKML.
A Documentation/ABI/testing/sysfs-gpio update is ready to submit once this
merges to mainline.
[akpm@linux-foundation.org: a few maintenance build fixes]
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Cc: Guennadi Liakhovetski <g.liakhovetski@pengutronix.de>
Cc: Greg KH <greg@kroah.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2008-07-25 08:46:07 +00:00
|
|
|
config GPIO_SYSFS
|
|
|
|
|
bool "/sys/class/gpio/... (sysfs interface)"
|
2013-01-17 02:53:32 +00:00
|
|
|
depends on SYSFS
|
gpio: sysfs interface
This adds a simple sysfs interface for GPIOs.
/sys/class/gpio
/export ... asks the kernel to export a GPIO to userspace
/unexport ... to return a GPIO to the kernel
/gpioN ... for each exported GPIO #N
/value ... always readable, writes fail for input GPIOs
/direction ... r/w as: in, out (default low); write high, low
/gpiochipN ... for each gpiochip; #N is its first GPIO
/base ... (r/o) same as N
/label ... (r/o) descriptive, not necessarily unique
/ngpio ... (r/o) number of GPIOs; numbered N .. N+(ngpio - 1)
GPIOs claimed by kernel code may be exported by its owner using a new
gpio_export() call, which should be most useful for driver debugging.
Such exports may optionally be done without a "direction" attribute.
Userspace may ask to take over a GPIO by writing to a sysfs control file,
helping to cope with incomplete board support or other "one-off"
requirements that don't merit full kernel support:
echo 23 > /sys/class/gpio/export
... will gpio_request(23, "sysfs") and gpio_export(23);
use /sys/class/gpio/gpio-23/direction to (re)configure it,
when that GPIO can be used as both input and output.
echo 23 > /sys/class/gpio/unexport
... will gpio_free(23), when it was exported as above
The extra D-space footprint is a few hundred bytes, except for the sysfs
resources associated with each exported GPIO. The additional I-space
footprint is about two thirds of the current size of gpiolib (!). Since
no /dev node creation is involved, no "udev" support is needed.
Related changes:
* This adds a device pointer to "struct gpio_chip". When GPIO
providers initialize that, sysfs gpio class devices become children of
that device instead of being "virtual" devices.
* The (few) gpio_chip providers which have such a device node have
been updated.
* Some gpio_chip drivers also needed to update their module "owner"
field ... for which missing kerneldoc was added.
* Some gpio_chips don't support input GPIOs. Those GPIOs are now
flagged appropriately when the chip is registered.
Based on previous patches, and discussion both on and off LKML.
A Documentation/ABI/testing/sysfs-gpio update is ready to submit once this
merges to mainline.
[akpm@linux-foundation.org: a few maintenance build fixes]
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Cc: Guennadi Liakhovetski <g.liakhovetski@pengutronix.de>
Cc: Greg KH <greg@kroah.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2008-07-25 08:46:07 +00:00
|
|
|
help
|
2019-05-23 06:54:19 +00:00
|
|
|
Say Y here to add the legacy sysfs interface for GPIOs.
|
gpio: sysfs interface
This adds a simple sysfs interface for GPIOs.
/sys/class/gpio
/export ... asks the kernel to export a GPIO to userspace
/unexport ... to return a GPIO to the kernel
/gpioN ... for each exported GPIO #N
/value ... always readable, writes fail for input GPIOs
/direction ... r/w as: in, out (default low); write high, low
/gpiochipN ... for each gpiochip; #N is its first GPIO
/base ... (r/o) same as N
/label ... (r/o) descriptive, not necessarily unique
/ngpio ... (r/o) number of GPIOs; numbered N .. N+(ngpio - 1)
GPIOs claimed by kernel code may be exported by its owner using a new
gpio_export() call, which should be most useful for driver debugging.
Such exports may optionally be done without a "direction" attribute.
Userspace may ask to take over a GPIO by writing to a sysfs control file,
helping to cope with incomplete board support or other "one-off"
requirements that don't merit full kernel support:
echo 23 > /sys/class/gpio/export
... will gpio_request(23, "sysfs") and gpio_export(23);
use /sys/class/gpio/gpio-23/direction to (re)configure it,
when that GPIO can be used as both input and output.
echo 23 > /sys/class/gpio/unexport
... will gpio_free(23), when it was exported as above
The extra D-space footprint is a few hundred bytes, except for the sysfs
resources associated with each exported GPIO. The additional I-space
footprint is about two thirds of the current size of gpiolib (!). Since
no /dev node creation is involved, no "udev" support is needed.
Related changes:
* This adds a device pointer to "struct gpio_chip". When GPIO
providers initialize that, sysfs gpio class devices become children of
that device instead of being "virtual" devices.
* The (few) gpio_chip providers which have such a device node have
been updated.
* Some gpio_chip drivers also needed to update their module "owner"
field ... for which missing kerneldoc was added.
* Some gpio_chips don't support input GPIOs. Those GPIOs are now
flagged appropriately when the chip is registered.
Based on previous patches, and discussion both on and off LKML.
A Documentation/ABI/testing/sysfs-gpio update is ready to submit once this
merges to mainline.
[akpm@linux-foundation.org: a few maintenance build fixes]
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Cc: Guennadi Liakhovetski <g.liakhovetski@pengutronix.de>
Cc: Greg KH <greg@kroah.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2008-07-25 08:46:07 +00:00
|
|
|
|
2019-05-23 06:54:19 +00:00
|
|
|
This ABI is deprecated. If you want to use GPIO from userspace,
|
|
|
|
|
use the character device /dev/gpiochipN with the appropriate
|
|
|
|
|
ioctl() operations instead. The character device is always
|
|
|
|
|
available.
|
gpio: sysfs interface
This adds a simple sysfs interface for GPIOs.
/sys/class/gpio
/export ... asks the kernel to export a GPIO to userspace
/unexport ... to return a GPIO to the kernel
/gpioN ... for each exported GPIO #N
/value ... always readable, writes fail for input GPIOs
/direction ... r/w as: in, out (default low); write high, low
/gpiochipN ... for each gpiochip; #N is its first GPIO
/base ... (r/o) same as N
/label ... (r/o) descriptive, not necessarily unique
/ngpio ... (r/o) number of GPIOs; numbered N .. N+(ngpio - 1)
GPIOs claimed by kernel code may be exported by its owner using a new
gpio_export() call, which should be most useful for driver debugging.
Such exports may optionally be done without a "direction" attribute.
Userspace may ask to take over a GPIO by writing to a sysfs control file,
helping to cope with incomplete board support or other "one-off"
requirements that don't merit full kernel support:
echo 23 > /sys/class/gpio/export
... will gpio_request(23, "sysfs") and gpio_export(23);
use /sys/class/gpio/gpio-23/direction to (re)configure it,
when that GPIO can be used as both input and output.
echo 23 > /sys/class/gpio/unexport
... will gpio_free(23), when it was exported as above
The extra D-space footprint is a few hundred bytes, except for the sysfs
resources associated with each exported GPIO. The additional I-space
footprint is about two thirds of the current size of gpiolib (!). Since
no /dev node creation is involved, no "udev" support is needed.
Related changes:
* This adds a device pointer to "struct gpio_chip". When GPIO
providers initialize that, sysfs gpio class devices become children of
that device instead of being "virtual" devices.
* The (few) gpio_chip providers which have such a device node have
been updated.
* Some gpio_chip drivers also needed to update their module "owner"
field ... for which missing kerneldoc was added.
* Some gpio_chips don't support input GPIOs. Those GPIOs are now
flagged appropriately when the chip is registered.
Based on previous patches, and discussion both on and off LKML.
A Documentation/ABI/testing/sysfs-gpio update is ready to submit once this
merges to mainline.
[akpm@linux-foundation.org: a few maintenance build fixes]
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Cc: Guennadi Liakhovetski <g.liakhovetski@pengutronix.de>
Cc: Greg KH <greg@kroah.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2008-07-25 08:46:07 +00:00
|
|
|
|
2011-06-05 00:38:28 +00:00
|
|
|
config GPIO_GENERIC
|
2016-10-03 07:46:58 +00:00
|
|
|
depends on HAS_IOMEM # Only for IOMEM drivers
|
2011-06-05 00:38:28 +00:00
|
|
|
tristate
|
|
|
|
|
|
2011-05-20 06:40:19 +00:00
|
|
|
# put drivers in the right section, in alphabetical order
|
2008-02-05 06:28:17 +00:00
|
|
|
|
2015-04-08 13:11:16 +00:00
|
|
|
# This symbol is selected by both I2C and SPI expanders
|
2010-03-05 21:44:33 +00:00
|
|
|
config GPIO_MAX730X
|
|
|
|
|
tristate
|
|
|
|
|
|
2015-04-08 13:11:16 +00:00
|
|
|
menu "Memory mapped GPIO drivers"
|
2016-10-03 07:46:58 +00:00
|
|
|
depends on HAS_IOMEM
|
2008-11-12 21:25:38 +00:00
|
|
|
|
2014-10-03 07:31:57 +00:00
|
|
|
config GPIO_74XX_MMIO
|
|
|
|
|
tristate "GPIO driver for 74xx-ICs with MMIO access"
|
|
|
|
|
depends on OF_GPIO
|
|
|
|
|
select GPIO_GENERIC
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support GPIO functionality for 74xx-compatible ICs
|
|
|
|
|
with MMIO access. Compatible models include:
|
|
|
|
|
1 bit: 741G125 (Input), 741G74 (Output)
|
|
|
|
|
2 bits: 742G125 (Input), 7474 (Output)
|
|
|
|
|
4 bits: 74125 (Input), 74175 (Output)
|
|
|
|
|
6 bits: 74365 (Input), 74174 (Output)
|
|
|
|
|
8 bits: 74244 (Input), 74273 (Output)
|
|
|
|
|
16 bits: 741624 (Input), 7416374 (Output)
|
|
|
|
|
|
2015-04-08 08:08:56 +00:00
|
|
|
config GPIO_ALTERA
|
|
|
|
|
tristate "Altera GPIO"
|
|
|
|
|
depends on OF_GPIO
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Say Y or M here to build support for the Altera PIO device.
|
|
|
|
|
|
|
|
|
|
If driver is built as a module it will be called gpio-altera.
|
|
|
|
|
|
2015-10-19 03:07:37 +00:00
|
|
|
config GPIO_AMDPT
|
|
|
|
|
tristate "AMD Promontory GPIO support"
|
|
|
|
|
depends on ACPI
|
2016-02-29 14:00:01 +00:00
|
|
|
select GPIO_GENERIC
|
2015-10-19 03:07:37 +00:00
|
|
|
help
|
|
|
|
|
driver for GPIO functionality on Promontory IOHub
|
|
|
|
|
Require ACPI ASL code to enumerate as a platform device.
|
|
|
|
|
|
2016-08-30 07:54:27 +00:00
|
|
|
config GPIO_ASPEED
|
|
|
|
|
tristate "Aspeed GPIO support"
|
|
|
|
|
depends on (ARCH_ASPEED || COMPILE_TEST) && OF_GPIO
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Say Y here to support Aspeed AST2400 and AST2500 GPIO controllers.
|
|
|
|
|
|
2019-09-27 11:48:33 +00:00
|
|
|
config GPIO_ASPEED_SGPIO
|
|
|
|
|
bool "Aspeed SGPIO support"
|
|
|
|
|
depends on (ARCH_ASPEED || COMPILE_TEST) && OF_GPIO
|
|
|
|
|
select GPIO_GENERIC
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Say Y here to support Aspeed AST2500 SGPIO functionality.
|
|
|
|
|
|
2016-01-28 19:44:29 +00:00
|
|
|
config GPIO_ATH79
|
|
|
|
|
tristate "Atheros AR71XX/AR724X/AR913X GPIO support"
|
|
|
|
|
default y if ATH79
|
2016-01-28 19:44:30 +00:00
|
|
|
depends on ATH79 || COMPILE_TEST
|
2016-01-28 19:44:29 +00:00
|
|
|
select GPIO_GENERIC
|
2016-01-28 19:44:32 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2016-01-28 19:44:29 +00:00
|
|
|
help
|
|
|
|
|
Select this option to enable GPIO driver for
|
|
|
|
|
Atheros AR71XX/AR724X/AR913X SoC devices.
|
|
|
|
|
|
2018-02-20 12:19:33 +00:00
|
|
|
config GPIO_RASPBERRYPI_EXP
|
|
|
|
|
tristate "Raspberry Pi 3 GPIO Expander"
|
|
|
|
|
default RASPBERRYPI_FIRMWARE
|
|
|
|
|
depends on OF_GPIO
|
2018-03-02 09:47:01 +00:00
|
|
|
# Make sure not 'y' when RASPBERRYPI_FIRMWARE is 'm'. This can only
|
|
|
|
|
# happen when COMPILE_TEST=y, hence the added !RASPBERRYPI_FIRMWARE.
|
2018-02-28 13:48:08 +00:00
|
|
|
depends on (ARCH_BCM2835 && RASPBERRYPI_FIRMWARE) || (COMPILE_TEST && !RASPBERRYPI_FIRMWARE)
|
2018-02-20 12:19:33 +00:00
|
|
|
help
|
|
|
|
|
Turn on GPIO support for the expander on Raspberry Pi 3 boards, using
|
|
|
|
|
the firmware mailbox to communicate with VideoCore on BCM283x chips.
|
|
|
|
|
|
2015-04-08 12:36:17 +00:00
|
|
|
config GPIO_BCM_KONA
|
|
|
|
|
bool "Broadcom Kona GPIO"
|
|
|
|
|
depends on OF_GPIO && (ARCH_BCM_MOBILE || COMPILE_TEST)
|
|
|
|
|
help
|
|
|
|
|
Turn on GPIO support for Broadcom "Kona" chips.
|
|
|
|
|
|
2019-10-24 20:27:03 +00:00
|
|
|
config GPIO_BCM_XGS_IPROC
|
|
|
|
|
tristate "BRCM XGS iProc GPIO support"
|
|
|
|
|
depends on OF_GPIO && (ARCH_BCM_IPROC || COMPILE_TEST)
|
|
|
|
|
select GPIO_GENERIC
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
default ARCH_BCM_IPROC
|
|
|
|
|
help
|
|
|
|
|
Say yes here to enable GPIO support for Broadcom XGS iProc SoCs.
|
|
|
|
|
|
2015-05-29 02:14:05 +00:00
|
|
|
config GPIO_BRCMSTB
|
|
|
|
|
tristate "BRCMSTB GPIO support"
|
2016-01-06 18:55:23 +00:00
|
|
|
default y if (ARCH_BRCMSTB || BMIPS_GENERIC)
|
|
|
|
|
depends on OF_GPIO && (ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST)
|
2015-05-29 02:14:05 +00:00
|
|
|
select GPIO_GENERIC
|
2017-10-24 19:54:50 +00:00
|
|
|
select IRQ_DOMAIN
|
2015-05-29 02:14:05 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to enable GPIO support for Broadcom STB (BCM7XXX) SoCs.
|
|
|
|
|
|
2018-12-18 16:10:42 +00:00
|
|
|
config GPIO_CADENCE
|
|
|
|
|
tristate "Cadence GPIO support"
|
|
|
|
|
depends on OF_GPIO
|
|
|
|
|
select GPIO_GENERIC
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Say yes here to enable support for Cadence GPIO controller.
|
|
|
|
|
|
2012-10-09 16:05:56 +00:00
|
|
|
config GPIO_CLPS711X
|
2013-04-26 15:47:28 +00:00
|
|
|
tristate "CLPS711X GPIO support"
|
2013-12-24 14:08:54 +00:00
|
|
|
depends on ARCH_CLPS711X || COMPILE_TEST
|
2013-04-26 15:47:28 +00:00
|
|
|
select GPIO_GENERIC
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support GPIO on CLPS711X SoCs.
|
2012-10-09 16:05:56 +00:00
|
|
|
|
2013-11-21 15:34:36 +00:00
|
|
|
config GPIO_DAVINCI
|
|
|
|
|
bool "TI Davinci/Keystone GPIO support"
|
|
|
|
|
default y if ARCH_DAVINCI
|
2019-06-05 05:55:19 +00:00
|
|
|
depends on (ARM || ARM64) && (ARCH_DAVINCI || ARCH_KEYSTONE || ARCH_K3)
|
2013-11-21 15:34:36 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to enable GPIO support for TI Davinci/Keystone SoCs.
|
|
|
|
|
|
2014-02-25 23:01:01 +00:00
|
|
|
config GPIO_DWAPB
|
|
|
|
|
tristate "Synopsys DesignWare APB GPIO driver"
|
|
|
|
|
select GPIO_GENERIC
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
help
|
|
|
|
|
Say Y or M here to build support for the Synopsys DesignWare APB
|
|
|
|
|
GPIO block.
|
|
|
|
|
|
2018-03-05 02:56:51 +00:00
|
|
|
config GPIO_EIC_SPRD
|
|
|
|
|
tristate "Spreadtrum EIC support"
|
|
|
|
|
depends on ARCH_SPRD || COMPILE_TEST
|
|
|
|
|
depends on OF_GPIO
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support Spreadtrum EIC device.
|
|
|
|
|
|
2012-05-17 06:22:23 +00:00
|
|
|
config GPIO_EM
|
|
|
|
|
tristate "Emma Mobile GPIO"
|
2016-11-20 17:48:36 +00:00
|
|
|
depends on (ARCH_EMEV2 || COMPILE_TEST) && OF_GPIO
|
2012-05-17 06:22:23 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to support GPIO on Renesas Emma Mobile SoCs.
|
|
|
|
|
|
2011-06-01 17:09:19 +00:00
|
|
|
config GPIO_EP93XX
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on ARCH_EP93XX
|
2011-06-08 21:35:33 +00:00
|
|
|
select GPIO_GENERIC
|
2018-08-22 20:41:11 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2011-06-01 17:09:19 +00:00
|
|
|
|
2017-01-19 22:23:20 +00:00
|
|
|
config GPIO_EXAR
|
|
|
|
|
tristate "Support for GPIO pins on XR17V352/354/358"
|
|
|
|
|
depends on SERIAL_8250_EXAR
|
|
|
|
|
help
|
|
|
|
|
Selecting this option will enable handling of GPIO pins present
|
|
|
|
|
on Exar XR17V352/354/358 chips.
|
|
|
|
|
|
2015-04-08 08:08:56 +00:00
|
|
|
config GPIO_GE_FPGA
|
|
|
|
|
bool "GE FPGA based GPIO"
|
|
|
|
|
depends on GE_FPGA
|
|
|
|
|
select GPIO_GENERIC
|
|
|
|
|
help
|
|
|
|
|
Support for common GPIO functionality provided on some GE Single Board
|
|
|
|
|
Computers.
|
|
|
|
|
|
|
|
|
|
This driver provides basic support (configure as input or output, read
|
|
|
|
|
and write pin state) for GPIO implemented in a number of GE single
|
|
|
|
|
board computers.
|
|
|
|
|
|
2017-03-12 23:28:16 +00:00
|
|
|
config GPIO_FTGPIO010
|
|
|
|
|
bool "Faraday FTGPIO010 GPIO"
|
2017-01-22 12:18:44 +00:00
|
|
|
depends on OF_GPIO
|
|
|
|
|
select GPIO_GENERIC
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
2017-03-12 23:28:17 +00:00
|
|
|
default (ARCH_GEMINI || ARCH_MOXART)
|
2017-01-22 12:18:44 +00:00
|
|
|
help
|
2017-03-12 23:28:16 +00:00
|
|
|
Support for common GPIOs from the Faraday FTGPIO010 IP core, found in
|
|
|
|
|
Cortina systems Gemini platforms, Moxa ART and others.
|
2017-01-22 12:18:44 +00:00
|
|
|
|
2015-04-08 08:08:56 +00:00
|
|
|
config GPIO_GENERIC_PLATFORM
|
|
|
|
|
tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
|
|
|
|
|
select GPIO_GENERIC
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support basic platform_device memory-mapped GPIO controllers.
|
|
|
|
|
|
|
|
|
|
config GPIO_GRGPIO
|
|
|
|
|
tristate "Aeroflex Gaisler GRGPIO support"
|
2016-08-16 10:07:31 +00:00
|
|
|
depends on OF_GPIO
|
2015-04-08 08:08:56 +00:00
|
|
|
select GPIO_GENERIC
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
help
|
|
|
|
|
Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
|
|
|
|
|
VHDL IP core library.
|
|
|
|
|
|
gpio: Add GPIO driver for Nintendo Wii
The Nintendo Wii's chipset (called "Hollywood") has a GPIO controller
that supports a configurable number of pins (up to 32), interrupts, and
some special mechanisms to share the controller between the system's
security processor (an ARM926) and the PowerPC CPU. Pin multiplexing is
not supported.
This patch adds a basic driver for this GPIO controller. Interrupt
support will come in a later patch.
This patch is based on code developed by Albert Herranz and the GameCube
Linux Team, file arch/powerpc/platforms/embedded6xx/hlwd-gpio.c,
available at https://github.com/DeltaResero/GC-Wii-Linux-Kernels, but
has grown quite dissimilar.
v3:
- Do some style cleanups, as suggest by Andy Shevchenko
v2:
- Change hlwd_gpio_driver.driver.name to "gpio-hlwd" to match the
filename (was "hlwd_gpio")
- Remove unnecessary include of linux/of_gpio.h, as suggested by Linus
Walleij.
- Add struct device pointer to context struct to make it possible to use
dev_info(hlwd->dev, "..."), as suggested by Linus Walleij
- Use the GPIO_GENERIC library to reduce code size, as suggested by
Linus Walleij
- Use iowrite32be instead of __raw_writel for big-endian MMIO access, as
suggested by Linus Walleij
- Remove commit message paragraph suggesting to diff against the
original driver, because it's so different now
Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
Cc: Albert Herranz <albert_herranz@yahoo.es>
Reviewed-by: Segher Boessenkool <segher@kernel.crashing.org>
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2018-02-09 12:07:29 +00:00
|
|
|
config GPIO_HLWD
|
|
|
|
|
tristate "Nintendo Wii (Hollywood) GPIO"
|
|
|
|
|
depends on OF_GPIO
|
|
|
|
|
select GPIO_GENERIC
|
2019-01-14 19:14:49 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
gpio: Add GPIO driver for Nintendo Wii
The Nintendo Wii's chipset (called "Hollywood") has a GPIO controller
that supports a configurable number of pins (up to 32), interrupts, and
some special mechanisms to share the controller between the system's
security processor (an ARM926) and the PowerPC CPU. Pin multiplexing is
not supported.
This patch adds a basic driver for this GPIO controller. Interrupt
support will come in a later patch.
This patch is based on code developed by Albert Herranz and the GameCube
Linux Team, file arch/powerpc/platforms/embedded6xx/hlwd-gpio.c,
available at https://github.com/DeltaResero/GC-Wii-Linux-Kernels, but
has grown quite dissimilar.
v3:
- Do some style cleanups, as suggest by Andy Shevchenko
v2:
- Change hlwd_gpio_driver.driver.name to "gpio-hlwd" to match the
filename (was "hlwd_gpio")
- Remove unnecessary include of linux/of_gpio.h, as suggested by Linus
Walleij.
- Add struct device pointer to context struct to make it possible to use
dev_info(hlwd->dev, "..."), as suggested by Linus Walleij
- Use the GPIO_GENERIC library to reduce code size, as suggested by
Linus Walleij
- Use iowrite32be instead of __raw_writel for big-endian MMIO access, as
suggested by Linus Walleij
- Remove commit message paragraph suggesting to diff against the
original driver, because it's so different now
Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
Cc: Albert Herranz <albert_herranz@yahoo.es>
Reviewed-by: Segher Boessenkool <segher@kernel.crashing.org>
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2018-02-09 12:07:29 +00:00
|
|
|
help
|
|
|
|
|
Select this to support the GPIO controller of the Nintendo Wii.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2015-04-08 08:08:56 +00:00
|
|
|
config GPIO_ICH
|
|
|
|
|
tristate "Intel ICH GPIO"
|
|
|
|
|
depends on PCI && X86
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
select LPC_ICH
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support the GPIO functionality of a number of Intel
|
|
|
|
|
ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
|
|
|
|
|
ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
|
|
|
|
|
Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config GPIO_IOP
|
|
|
|
|
tristate "Intel IOP GPIO"
|
2019-08-09 16:33:15 +00:00
|
|
|
depends on ARCH_IOP32X || COMPILE_TEST
|
2016-09-09 06:20:03 +00:00
|
|
|
select GPIO_GENERIC
|
2015-04-08 08:08:56 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to support the GPIO functionality of a number of Intel
|
|
|
|
|
IOP32X or IOP33X.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2019-01-25 20:59:11 +00:00
|
|
|
config GPIO_IXP4XX
|
|
|
|
|
bool "Intel IXP4xx GPIO"
|
|
|
|
|
depends on ARM # For <asm/mach-types.h>
|
|
|
|
|
depends on ARCH_IXP4XX
|
|
|
|
|
select GPIO_GENERIC
|
2019-08-08 12:32:38 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2019-01-25 20:59:11 +00:00
|
|
|
select IRQ_DOMAIN_HIERARCHY
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support the GPIO functionality of a number of Intel
|
|
|
|
|
IXP4xx series of chips.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2015-04-08 08:08:56 +00:00
|
|
|
config GPIO_LOONGSON
|
|
|
|
|
bool "Loongson-2/3 GPIO support"
|
|
|
|
|
depends on CPU_LOONGSON2 || CPU_LOONGSON3
|
|
|
|
|
help
|
|
|
|
|
driver for GPIO functionality on Loongson-2F/3A/3B processors.
|
|
|
|
|
|
2015-05-02 21:11:34 +00:00
|
|
|
config GPIO_LPC18XX
|
2016-06-05 18:23:43 +00:00
|
|
|
tristate "NXP LPC18XX/43XX GPIO support"
|
2015-05-02 21:11:34 +00:00
|
|
|
default y if ARCH_LPC18XX
|
|
|
|
|
depends on OF_GPIO && (ARCH_LPC18XX || COMPILE_TEST)
|
gpio: lpc18xx: add GPIO pin interrupt controller support
The change adds support of LPC18xx/LPC43xx GPIO pin interrupt controller
block within SoC GPIO controller. The new interrupt controller driver
allows to configure and capture edge or level interrupts on 8 arbitrary
selectedinput GPIO pins, and lift the signals to be reported as NVIC rising
edge interrupts. Configuration of a particular GPIO pin to serve as
interrupt and its mapping to an interrupt on NVIC is done by SCU pin
controller, for more details see description of 'nxp,gpio-pin-interrupt'
device tree property of a GPIO pin [1].
From LPC18xx and LPC43xx User Manuals the GPIO controller consists of
the following blocks:
* GPIO pin interrupt block at 0x40087000, this change adds its support,
* GPIO GROUP0 interrupt block at 0x40088000,
* GPIO GROUP1 interrupt block at 0x40089000,
* GPIO port block at 0x400F4000, it is supported by the original driver.
While all 4 sub-controller blocks have their own I/O addresses, moreover
all 3 interrupt blocks are APB0 peripherals and high-speed GPIO block is
an AHB slave, according to the hardware manual the GPIO controller is
seen as a single block, and 4 sub-controllers have the shared reset signal
RGU #28 and clock to register interface CLK_CPU_GPIO on CCU1.
Likely support of two GPIO group interrupt blocks won't be added in short
term, because the mechanism to mask several interrupt sources is not well
defined.
[1] Documentation/devicetree/bindings/pinctrl/nxp,lpc1850-scu.txt
Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2018-11-28 22:48:41 +00:00
|
|
|
select IRQ_DOMAIN_HIERARCHY
|
2015-05-02 21:11:34 +00:00
|
|
|
help
|
|
|
|
|
Select this option to enable GPIO driver for
|
|
|
|
|
NXP LPC18XX/43XX devices.
|
|
|
|
|
|
2019-08-09 14:40:31 +00:00
|
|
|
config GPIO_LPC32XX
|
|
|
|
|
tristate "NXP LPC32XX GPIO support"
|
|
|
|
|
depends on OF_GPIO && (ARCH_LPC32XX || COMPILE_TEST)
|
|
|
|
|
help
|
|
|
|
|
Select this option to enable GPIO driver for
|
|
|
|
|
NXP LPC32XX devices.
|
|
|
|
|
|
2015-04-08 08:08:56 +00:00
|
|
|
config GPIO_LYNXPOINT
|
|
|
|
|
tristate "Intel Lynxpoint GPIO support"
|
|
|
|
|
depends on ACPI && X86
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
driver for GPIO functionality on Intel Lynxpoint PCH chipset
|
|
|
|
|
Requires ACPI device enumeration code to set up a platform device.
|
|
|
|
|
|
2015-01-19 10:35:53 +00:00
|
|
|
config GPIO_MB86S7X
|
2017-10-27 20:21:47 +00:00
|
|
|
tristate "GPIO support for Fujitsu MB86S7x Platforms"
|
2015-01-19 10:35:53 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to support the GPIO controller in Fujitsu MB86S70 SoCs.
|
|
|
|
|
|
2016-02-29 18:44:43 +00:00
|
|
|
config GPIO_MENZ127
|
|
|
|
|
tristate "MEN 16Z127 GPIO support"
|
|
|
|
|
depends on MCB
|
|
|
|
|
select GPIO_GENERIC
|
|
|
|
|
help
|
2019-03-05 00:35:31 +00:00
|
|
|
Say yes here to support the MEN 16Z127 GPIO Controller
|
2016-02-29 18:44:43 +00:00
|
|
|
|
2015-04-08 08:08:56 +00:00
|
|
|
config GPIO_MM_LANTIQ
|
|
|
|
|
bool "Lantiq Memory mapped GPIOs"
|
|
|
|
|
depends on LANTIQ && SOC_XWAY
|
|
|
|
|
help
|
|
|
|
|
This enables support for memory mapped GPIOs on the External Bus Unit
|
|
|
|
|
(EBU) found on Lantiq SoCs. The gpios are output only as they are
|
|
|
|
|
created by attaching a 16bit latch to the bus.
|
|
|
|
|
|
2011-07-06 17:54:19 +00:00
|
|
|
config GPIO_MPC5200
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on PPC_MPC52xx
|
|
|
|
|
|
2011-09-21 10:49:20 +00:00
|
|
|
config GPIO_MPC8XXX
|
2016-01-12 12:10:09 +00:00
|
|
|
bool "MPC512x/MPC8xxx/QorIQ GPIO support"
|
2011-09-21 10:49:20 +00:00
|
|
|
depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
|
2016-01-12 12:10:09 +00:00
|
|
|
FSL_SOC_BOOKE || PPC_86xx || ARCH_LAYERSCAPE || ARM || \
|
|
|
|
|
COMPILE_TEST
|
|
|
|
|
select GPIO_GENERIC
|
2016-04-19 12:10:08 +00:00
|
|
|
select IRQ_DOMAIN
|
2011-09-21 10:49:20 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you're going to use hardware that connects to the
|
2016-01-12 12:10:09 +00:00
|
|
|
MPC512x/831x/834x/837x/8572/8610/QorIQ GPIOs.
|
2011-09-21 10:49:20 +00:00
|
|
|
|
2018-07-05 13:43:10 +00:00
|
|
|
config GPIO_MT7621
|
|
|
|
|
bool "Mediatek MT7621 GPIO Support"
|
|
|
|
|
depends on SOC_MT7620 || SOC_MT7621 || COMPILE_TEST
|
2018-07-10 15:18:47 +00:00
|
|
|
depends on OF_GPIO
|
2018-07-05 13:43:10 +00:00
|
|
|
select GPIO_GENERIC
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support the Mediatek MT7621 SoC GPIO device
|
|
|
|
|
|
2012-09-19 20:52:58 +00:00
|
|
|
config GPIO_MVEBU
|
|
|
|
|
def_bool y
|
2017-05-19 16:09:23 +00:00
|
|
|
depends on PLAT_ORION || ARCH_MVEBU
|
2016-08-16 10:07:31 +00:00
|
|
|
depends on OF_GPIO
|
2012-09-19 20:52:58 +00:00
|
|
|
select GENERIC_IRQ_CHIP
|
2017-05-24 14:32:06 +00:00
|
|
|
select REGMAP_MMIO
|
2012-09-19 20:52:58 +00:00
|
|
|
|
2011-06-05 16:07:54 +00:00
|
|
|
config GPIO_MXC
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on ARCH_MXC
|
2011-06-05 00:38:28 +00:00
|
|
|
select GPIO_GENERIC
|
2011-06-07 08:25:37 +00:00
|
|
|
select GENERIC_IRQ_CHIP
|
2011-06-05 00:38:28 +00:00
|
|
|
|
|
|
|
|
config GPIO_MXS
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on ARCH_MXS
|
2011-06-06 14:31:29 +00:00
|
|
|
select GPIO_GENERIC
|
2011-06-07 14:00:54 +00:00
|
|
|
select GENERIC_IRQ_CHIP
|
2011-06-05 16:07:54 +00:00
|
|
|
|
2013-07-29 21:29:10 +00:00
|
|
|
config GPIO_OCTEON
|
|
|
|
|
tristate "Cavium OCTEON GPIO"
|
|
|
|
|
depends on GPIOLIB && CAVIUM_OCTEON_SOC
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support the on-chip GPIO lines on the OCTEON
|
|
|
|
|
family of SOCs.
|
|
|
|
|
|
2014-04-06 14:58:15 +00:00
|
|
|
config GPIO_OMAP
|
2015-04-23 23:56:22 +00:00
|
|
|
tristate "TI OMAP GPIO support" if ARCH_OMAP2PLUS || COMPILE_TEST
|
2014-04-06 14:58:15 +00:00
|
|
|
default y if ARCH_OMAP
|
2014-04-28 09:07:03 +00:00
|
|
|
depends on ARM
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
2014-04-06 14:58:16 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2014-04-06 14:58:15 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to enable GPIO support for TI OMAP SoCs.
|
|
|
|
|
|
2009-06-18 23:48:58 +00:00
|
|
|
config GPIO_PL061
|
|
|
|
|
bool "PrimeCell PL061 GPIO support"
|
2013-11-06 03:27:02 +00:00
|
|
|
depends on ARM_AMBA
|
2014-02-04 12:39:01 +00:00
|
|
|
select IRQ_DOMAIN
|
2014-03-25 09:42:35 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2009-06-18 23:48:58 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to support the PrimeCell PL061 GPIO device
|
|
|
|
|
|
2018-03-05 02:56:52 +00:00
|
|
|
config GPIO_PMIC_EIC_SPRD
|
|
|
|
|
tristate "Spreadtrum PMIC EIC support"
|
|
|
|
|
depends on MFD_SC27XX_PMIC || COMPILE_TEST
|
|
|
|
|
depends on OF_GPIO
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support Spreadtrum PMIC EIC device.
|
|
|
|
|
|
2011-10-17 12:37:52 +00:00
|
|
|
config GPIO_PXA
|
|
|
|
|
bool "PXA GPIO support"
|
|
|
|
|
depends on ARCH_PXA || ARCH_MMP
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support the PXA GPIO device
|
|
|
|
|
|
2013-03-13 11:32:13 +00:00
|
|
|
config GPIO_RCAR
|
|
|
|
|
tristate "Renesas R-Car GPIO"
|
2016-02-23 01:36:51 +00:00
|
|
|
depends on ARCH_RENESAS || COMPILE_TEST
|
2015-01-12 10:07:59 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2013-03-13 11:32:13 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to support GPIO on Renesas R-Car SoCs.
|
|
|
|
|
|
2019-10-21 06:44:12 +00:00
|
|
|
config GPIO_RDA
|
|
|
|
|
bool "RDA Micro GPIO controller support"
|
|
|
|
|
depends on ARCH_RDA || COMPILE_TEST
|
|
|
|
|
depends on OF_GPIO
|
|
|
|
|
select GPIO_GENERIC
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Say Y here to support RDA Micro GPIO controller.
|
|
|
|
|
|
2016-08-31 07:49:44 +00:00
|
|
|
config GPIO_REG
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
A 32-bit single register GPIO fixed in/out implementation. This
|
|
|
|
|
can be used to represent any register as a set of GPIO signals.
|
|
|
|
|
|
2018-12-12 11:57:15 +00:00
|
|
|
config GPIO_SAMA5D2_PIOBU
|
|
|
|
|
tristate "SAMA5D2 PIOBU GPIO support"
|
|
|
|
|
depends on MFD_SYSCON
|
2018-12-22 10:04:55 +00:00
|
|
|
depends on OF_GPIO
|
2018-12-12 11:57:15 +00:00
|
|
|
select GPIO_SYSCON
|
|
|
|
|
help
|
|
|
|
|
Say yes here to use the PIOBU pins as GPIOs.
|
|
|
|
|
|
|
|
|
|
PIOBU pins on the SAMA5D2 can be used as GPIOs.
|
|
|
|
|
The difference from regular GPIOs is that they
|
|
|
|
|
maintain their value during backup/self-refresh.
|
|
|
|
|
|
2018-09-27 07:48:08 +00:00
|
|
|
config GPIO_SIOX
|
|
|
|
|
tristate "SIOX GPIO support"
|
|
|
|
|
depends on SIOX
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support SIOX I/O devices. These are units connected
|
|
|
|
|
via a SIOX bus and have a number of fixed-direction I/O lines.
|
|
|
|
|
|
2018-09-28 13:15:30 +00:00
|
|
|
config GPIO_SNPS_CREG
|
|
|
|
|
bool "Synopsys GPIO via CREG (Control REGisters) driver"
|
|
|
|
|
depends on ARC || COMPILE_TEST
|
2018-10-13 03:46:29 +00:00
|
|
|
depends on OF_GPIO
|
2018-09-28 13:15:30 +00:00
|
|
|
help
|
|
|
|
|
This driver supports GPIOs via CREG on various Synopsys SoCs.
|
|
|
|
|
This is a single-register MMIO GPIO driver for complex cases
|
|
|
|
|
where only several fields in register belong to GPIO lines and
|
|
|
|
|
each GPIO line owns a field with different length and on/off value.
|
|
|
|
|
|
2012-11-16 05:15:25 +00:00
|
|
|
config GPIO_SPEAR_SPICS
|
|
|
|
|
bool "ST SPEAr13xx SPI Chip Select as GPIO support"
|
|
|
|
|
depends on PLAT_SPEAR
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support ST SPEAr SPI Chip Select as GPIO device
|
|
|
|
|
|
2018-02-24 02:07:18 +00:00
|
|
|
config GPIO_SPRD
|
|
|
|
|
tristate "Spreadtrum GPIO support"
|
|
|
|
|
depends on ARCH_SPRD || COMPILE_TEST
|
|
|
|
|
depends on OF_GPIO
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support Spreadtrum GPIO device.
|
|
|
|
|
|
2012-04-12 08:48:55 +00:00
|
|
|
config GPIO_STA2X11
|
|
|
|
|
bool "STA2x11/ConneXt GPIO support"
|
|
|
|
|
depends on MFD_STA2X11
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support the STA2x11/ConneXt GPIO device.
|
|
|
|
|
The GPIO module has 128 GPIO pins with alternate functions.
|
|
|
|
|
|
2015-04-08 12:51:23 +00:00
|
|
|
config GPIO_STP_XWAY
|
|
|
|
|
bool "XWAY STP GPIOs"
|
2019-07-02 22:32:48 +00:00
|
|
|
depends on SOC_XWAY || COMPILE_TEST
|
|
|
|
|
depends on OF_GPIO
|
2015-04-08 12:51:23 +00:00
|
|
|
help
|
|
|
|
|
This enables support for the Serial To Parallel (STP) unit found on
|
|
|
|
|
XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
|
|
|
|
|
that can be up to 24 bit. This peripheral is aimed at driving leds.
|
|
|
|
|
Some of the gpios/leds can be auto updated by the soc with dsl and
|
|
|
|
|
phy status.
|
|
|
|
|
|
2014-03-11 17:55:14 +00:00
|
|
|
config GPIO_SYSCON
|
|
|
|
|
tristate "GPIO based on SYSCON"
|
|
|
|
|
depends on MFD_SYSCON && OF
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support GPIO functionality though SYSCON driver.
|
|
|
|
|
|
2015-04-08 08:08:56 +00:00
|
|
|
config GPIO_TB10X
|
|
|
|
|
bool
|
2018-08-06 14:59:42 +00:00
|
|
|
select GPIO_GENERIC
|
2015-04-08 08:08:56 +00:00
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
select OF_GPIO
|
|
|
|
|
|
2016-02-24 19:54:32 +00:00
|
|
|
config GPIO_TEGRA
|
2016-07-06 12:54:03 +00:00
|
|
|
bool "NVIDIA Tegra GPIO support"
|
|
|
|
|
default ARCH_TEGRA
|
2016-02-24 19:54:32 +00:00
|
|
|
depends on ARCH_TEGRA || COMPILE_TEST
|
2016-08-16 10:07:31 +00:00
|
|
|
depends on OF_GPIO
|
2016-07-06 12:54:03 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to support GPIO pins on NVIDIA Tegra SoCs.
|
2016-02-24 19:54:32 +00:00
|
|
|
|
2017-11-07 18:15:56 +00:00
|
|
|
config GPIO_TEGRA186
|
|
|
|
|
tristate "NVIDIA Tegra186 GPIO support"
|
|
|
|
|
default ARCH_TEGRA_186_SOC
|
|
|
|
|
depends on ARCH_TEGRA_186_SOC || COMPILE_TEST
|
|
|
|
|
depends on OF_GPIO
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
2019-10-02 14:45:02 +00:00
|
|
|
select IRQ_DOMAIN_HIERARCHY
|
2017-11-07 18:15:56 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to support GPIO pins on NVIDIA Tegra186 SoCs.
|
|
|
|
|
|
2016-01-13 16:57:43 +00:00
|
|
|
config GPIO_TS4800
|
|
|
|
|
tristate "TS-4800 DIO blocks and compatibles"
|
|
|
|
|
depends on OF_GPIO
|
2016-02-26 23:06:59 +00:00
|
|
|
depends on SOC_IMX51 || COMPILE_TEST
|
2016-01-13 16:57:43 +00:00
|
|
|
select GPIO_GENERIC
|
|
|
|
|
help
|
|
|
|
|
This driver support TS-4800 FPGA GPIO controllers.
|
|
|
|
|
|
2017-08-18 00:53:35 +00:00
|
|
|
config GPIO_THUNDERX
|
|
|
|
|
tristate "Cavium ThunderX/OCTEON-TX GPIO"
|
|
|
|
|
depends on ARCH_THUNDER || (64BIT && COMPILE_TEST)
|
2017-09-06 01:40:52 +00:00
|
|
|
depends on PCI_MSI
|
2019-08-08 12:32:40 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2017-09-06 01:40:52 +00:00
|
|
|
select IRQ_DOMAIN_HIERARCHY
|
2017-08-18 00:53:35 +00:00
|
|
|
select IRQ_FASTEOI_HIERARCHY_HANDLERS
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support the on-chip GPIO lines on the ThunderX
|
|
|
|
|
and OCTEON-TX families of SoCs.
|
|
|
|
|
|
2017-10-12 11:36:16 +00:00
|
|
|
config GPIO_UNIPHIER
|
|
|
|
|
tristate "UniPhier GPIO support"
|
|
|
|
|
depends on ARCH_UNIPHIER || COMPILE_TEST
|
|
|
|
|
depends on OF_GPIO
|
|
|
|
|
select IRQ_DOMAIN_HIERARCHY
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support UniPhier GPIOs.
|
|
|
|
|
|
2014-10-16 19:47:58 +00:00
|
|
|
config GPIO_VF610
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on ARCH_MXC && SOC_VF610
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support Vybrid vf610 GPIOs.
|
|
|
|
|
|
2015-04-08 08:08:56 +00:00
|
|
|
config GPIO_VR41XX
|
|
|
|
|
tristate "NEC VR4100 series General-purpose I/O Uint support"
|
|
|
|
|
depends on CPU_VR41XX
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support the NEC VR4100 series General-purpose I/O Uint
|
|
|
|
|
|
|
|
|
|
config GPIO_VX855
|
|
|
|
|
tristate "VIA VX855/VX875 GPIO"
|
2016-11-20 17:37:25 +00:00
|
|
|
depends on (X86 || COMPILE_TEST) && PCI
|
2015-04-08 08:08:56 +00:00
|
|
|
select MFD_CORE
|
|
|
|
|
select MFD_VX855
|
|
|
|
|
help
|
|
|
|
|
Support access to the VX855/VX875 GPIO lines through the gpio library.
|
|
|
|
|
|
|
|
|
|
This driver provides common support for accessing the device,
|
|
|
|
|
additional drivers must be enabled in order to use the
|
|
|
|
|
functionality of the device.
|
|
|
|
|
|
2014-07-31 19:03:25 +00:00
|
|
|
config GPIO_XGENE
|
|
|
|
|
bool "APM X-Gene GPIO controller support"
|
|
|
|
|
depends on ARM64 && OF_GPIO
|
|
|
|
|
help
|
|
|
|
|
This driver is to support the GPIO block within the APM X-Gene SoC
|
|
|
|
|
platform's generic flash controller. The GPIO pins are muxed with
|
|
|
|
|
the generic flash controller's address and data pins. Say yes
|
|
|
|
|
here to enable the GFC GPIO functionality.
|
|
|
|
|
|
2015-01-16 07:34:19 +00:00
|
|
|
config GPIO_XGENE_SB
|
|
|
|
|
tristate "APM X-Gene GPIO standby controller support"
|
|
|
|
|
depends on ARCH_XGENE && OF_GPIO
|
|
|
|
|
select GPIO_GENERIC
|
2016-03-04 10:59:58 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2017-07-11 23:11:50 +00:00
|
|
|
select IRQ_DOMAIN_HIERARCHY
|
2015-01-16 07:34:19 +00:00
|
|
|
help
|
|
|
|
|
This driver supports the GPIO block within the APM X-Gene
|
|
|
|
|
Standby Domain. Say yes here to enable the GPIO functionality.
|
|
|
|
|
|
2008-11-12 21:25:38 +00:00
|
|
|
config GPIO_XILINX
|
2014-12-17 15:51:10 +00:00
|
|
|
tristate "Xilinx GPIO support"
|
2008-11-12 21:25:38 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to support the Xilinx FPGA GPIO device
|
|
|
|
|
|
2015-04-28 14:40:45 +00:00
|
|
|
config GPIO_XLP
|
|
|
|
|
tristate "Netlogic XLP GPIO support"
|
2017-05-22 08:58:31 +00:00
|
|
|
depends on OF_GPIO && (CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST)
|
2015-04-28 14:40:45 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
This driver provides support for GPIO interface on Netlogic XLP MIPS64
|
|
|
|
|
SoCs. Currently supported XLP variants are XLP8XX, XLP3XX, XLP2XX,
|
2017-05-22 08:58:31 +00:00
|
|
|
XLP9XX and XLP5XX. The same GPIO controller block is also present in
|
|
|
|
|
Cavium's ThunderX2 CN99XX SoCs.
|
2015-04-28 14:40:45 +00:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2013-12-12 09:18:41 +00:00
|
|
|
config GPIO_XTENSA
|
|
|
|
|
bool "Xtensa GPIO32 support"
|
|
|
|
|
depends on XTENSA
|
2013-12-18 07:10:29 +00:00
|
|
|
depends on HAVE_XTENSA_GPIO32
|
2013-12-12 09:18:41 +00:00
|
|
|
depends on !SMP
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support the Xtensa internal GPIO32 IMPWIRE (input)
|
|
|
|
|
and EXPSTATE (output) ports
|
|
|
|
|
|
2015-04-08 08:08:56 +00:00
|
|
|
config GPIO_ZEVIO
|
|
|
|
|
bool "LSI ZEVIO SoC memory mapped GPIOs"
|
|
|
|
|
depends on ARM && OF_GPIO
|
2009-06-29 02:11:05 +00:00
|
|
|
help
|
2015-04-08 08:08:56 +00:00
|
|
|
Say yes here to support the GPIO controller in LSI ZEVIO SoCs.
|
2009-06-29 02:11:05 +00:00
|
|
|
|
2015-04-08 08:08:56 +00:00
|
|
|
config GPIO_ZYNQ
|
|
|
|
|
tristate "Xilinx Zynq GPIO support"
|
2015-06-04 12:10:32 +00:00
|
|
|
depends on ARCH_ZYNQ || ARCH_ZYNQMP
|
2014-07-25 06:54:46 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2010-03-02 09:48:55 +00:00
|
|
|
help
|
2015-04-08 08:08:56 +00:00
|
|
|
Say yes here to support Xilinx Zynq GPIO controller.
|
2014-12-08 09:38:10 +00:00
|
|
|
|
2015-11-01 09:50:19 +00:00
|
|
|
config GPIO_ZX
|
|
|
|
|
bool "ZTE ZX GPIO support"
|
2016-11-20 17:44:48 +00:00
|
|
|
depends on ARCH_ZX || COMPILE_TEST
|
2015-11-01 09:50:19 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support the GPIO device on ZTE ZX SoCs.
|
|
|
|
|
|
2016-04-06 12:34:53 +00:00
|
|
|
config GPIO_LOONGSON1
|
|
|
|
|
tristate "Loongson1 GPIO support"
|
|
|
|
|
depends on MACH_LOONGSON32
|
|
|
|
|
select GPIO_GENERIC
|
|
|
|
|
help
|
|
|
|
|
Say Y or M here to support GPIO on Loongson1 SoCs.
|
|
|
|
|
|
2019-02-22 09:54:15 +00:00
|
|
|
config GPIO_AMD_FCH
|
|
|
|
|
tristate "GPIO support for AMD Fusion Controller Hub (G-series SOCs)"
|
|
|
|
|
help
|
|
|
|
|
This option enables driver for GPIO on AMDs Fusion Controller Hub,
|
|
|
|
|
as found on G-series SOCs (eg. GX-412TC)
|
|
|
|
|
|
|
|
|
|
Note: This driver doesn't registers itself automatically, as it
|
|
|
|
|
needs to be provided with platform specific configuration.
|
|
|
|
|
(See eg. CONFIG_PCENGINES_APU2.)
|
2015-04-08 13:11:16 +00:00
|
|
|
endmenu
|
2010-03-02 09:48:55 +00:00
|
|
|
|
2015-10-30 09:32:19 +00:00
|
|
|
menu "Port-mapped I/O GPIO drivers"
|
2015-11-01 09:39:07 +00:00
|
|
|
depends on X86 # Unconditional I/O space access
|
2015-10-30 09:32:19 +00:00
|
|
|
|
2016-01-20 18:50:11 +00:00
|
|
|
config GPIO_104_DIO_48E
|
|
|
|
|
tristate "ACCES 104-DIO-48E GPIO support"
|
2017-12-29 20:13:46 +00:00
|
|
|
depends on PC104
|
|
|
|
|
select ISA_BUS_API
|
2016-01-20 18:50:11 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
2016-05-01 22:44:39 +00:00
|
|
|
Enables GPIO support for the ACCES 104-DIO-48E series (104-DIO-48E,
|
|
|
|
|
104-DIO-24E). The base port addresses for the devices may be
|
|
|
|
|
configured via the base module parameter. The interrupt line numbers
|
|
|
|
|
for the devices may be configured via the irq module parameter.
|
2016-01-20 18:50:11 +00:00
|
|
|
|
2015-10-30 09:32:19 +00:00
|
|
|
config GPIO_104_IDIO_16
|
|
|
|
|
tristate "ACCES 104-IDIO-16 GPIO support"
|
2017-12-29 20:13:46 +00:00
|
|
|
depends on PC104
|
|
|
|
|
select ISA_BUS_API
|
2015-11-03 12:54:23 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2015-10-30 09:32:19 +00:00
|
|
|
help
|
2016-05-01 22:45:11 +00:00
|
|
|
Enables GPIO support for the ACCES 104-IDIO-16 family (104-IDIO-16,
|
|
|
|
|
104-IDIO-16E, 104-IDO-16, 104-IDIO-8, 104-IDIO-8E, 104-IDO-8). The
|
|
|
|
|
base port addresses for the devices may be configured via the base
|
|
|
|
|
module parameter. The interrupt line numbers for the devices may be
|
|
|
|
|
configured via the irq module parameter.
|
2015-10-30 09:32:19 +00:00
|
|
|
|
2015-11-23 17:54:50 +00:00
|
|
|
config GPIO_104_IDI_48
|
|
|
|
|
tristate "ACCES 104-IDI-48 GPIO support"
|
2017-12-29 20:13:46 +00:00
|
|
|
depends on PC104
|
|
|
|
|
select ISA_BUS_API
|
2015-11-23 17:54:50 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
2016-05-01 22:44:55 +00:00
|
|
|
Enables GPIO support for the ACCES 104-IDI-48 family (104-IDI-48A,
|
|
|
|
|
104-IDI-48AC, 104-IDI-48B, 104-IDI-48BC). The base port addresses for
|
|
|
|
|
the devices may be configured via the base module parameter. The
|
|
|
|
|
interrupt line numbers for the devices may be configured via the irq
|
|
|
|
|
module parameter.
|
2015-11-23 17:54:50 +00:00
|
|
|
|
2015-10-30 09:32:19 +00:00
|
|
|
config GPIO_F7188X
|
2016-01-22 07:23:33 +00:00
|
|
|
tristate "F71869, F71869A, F71882FG, F71889F and F81866 GPIO support"
|
2015-10-30 09:32:19 +00:00
|
|
|
help
|
|
|
|
|
This option enables support for GPIOs found on Fintek Super-I/O
|
2016-01-22 07:23:33 +00:00
|
|
|
chips F71869, F71869A, F71882FG, F71889F and F81866.
|
2015-10-30 09:32:19 +00:00
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called f7188x-gpio.
|
|
|
|
|
|
2016-08-02 13:57:47 +00:00
|
|
|
config GPIO_GPIO_MM
|
|
|
|
|
tristate "Diamond Systems GPIO-MM GPIO support"
|
2017-12-29 20:13:46 +00:00
|
|
|
depends on PC104
|
|
|
|
|
select ISA_BUS_API
|
2016-08-02 13:57:47 +00:00
|
|
|
help
|
|
|
|
|
Enables GPIO support for the Diamond Systems GPIO-MM and GPIO-MM-12.
|
|
|
|
|
|
|
|
|
|
The Diamond Systems GPIO-MM device features 48 lines of digital I/O
|
|
|
|
|
via the emulation of dual 82C55A PPI chips. This driver provides GPIO
|
|
|
|
|
support for these 48 channels of digital I/O.
|
|
|
|
|
|
|
|
|
|
The base port addresses for the devices may be configured via the base
|
|
|
|
|
array module parameter.
|
|
|
|
|
|
2015-10-30 09:32:19 +00:00
|
|
|
config GPIO_IT87
|
|
|
|
|
tristate "IT87xx GPIO support"
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support GPIO functionality of IT87xx Super I/O chips.
|
|
|
|
|
|
|
|
|
|
This driver is tested with ITE IT8728 and IT8732 Super I/O chips, and
|
2018-08-08 22:26:36 +00:00
|
|
|
supports the IT8761E, IT8613, IT8620E, and IT8628E Super I/O chips as
|
|
|
|
|
well.
|
2015-10-30 09:32:19 +00:00
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called gpio_it87
|
|
|
|
|
|
|
|
|
|
config GPIO_SCH
|
|
|
|
|
tristate "Intel SCH/TunnelCreek/Centerton/Quark X1000 GPIO"
|
2016-11-20 17:37:25 +00:00
|
|
|
depends on (X86 || COMPILE_TEST) && PCI
|
2015-10-30 09:32:19 +00:00
|
|
|
select MFD_CORE
|
|
|
|
|
select LPC_SCH
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support GPIO interface on Intel Poulsbo SCH,
|
|
|
|
|
Intel Tunnel Creek processor, Intel Centerton processor or
|
|
|
|
|
Intel Quark X1000 SoC.
|
|
|
|
|
|
|
|
|
|
The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
|
|
|
|
|
powered by the core power rail and are turned off during sleep
|
|
|
|
|
modes (S3 and higher). The remaining four GPIOs are powered by
|
|
|
|
|
the Intel SCH suspend power supply. These GPIOs remain
|
|
|
|
|
active during S3. The suspend powered GPIOs can be used to wake the
|
|
|
|
|
system from the Suspend-to-RAM state.
|
|
|
|
|
|
|
|
|
|
The Intel Tunnel Creek processor has 5 GPIOs powered by the
|
|
|
|
|
core power rail and 9 from suspend power supply.
|
|
|
|
|
|
|
|
|
|
The Intel Centerton processor has a total of 30 GPIO pins.
|
|
|
|
|
Twenty-one are powered by the core power rail and 9 from the
|
|
|
|
|
suspend power supply.
|
|
|
|
|
|
|
|
|
|
The Intel Quark X1000 SoC has 2 GPIOs powered by the core
|
|
|
|
|
power well and 6 from the suspend power well.
|
|
|
|
|
|
|
|
|
|
config GPIO_SCH311X
|
|
|
|
|
tristate "SMSC SCH311x SuperI/O GPIO"
|
|
|
|
|
help
|
|
|
|
|
Driver to enable the GPIOs found on SMSC SMSC SCH3112, SCH3114 and
|
|
|
|
|
SCH3116 "Super I/O" chipsets.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called gpio-sch311x.
|
|
|
|
|
|
|
|
|
|
config GPIO_TS5500
|
|
|
|
|
tristate "TS-5500 DIO blocks and compatibles"
|
|
|
|
|
depends on TS5500 || COMPILE_TEST
|
|
|
|
|
help
|
|
|
|
|
This driver supports Digital I/O exposed by pin blocks found on some
|
|
|
|
|
Technologic Systems platforms. It includes, but is not limited to, 3
|
|
|
|
|
blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
|
|
|
|
|
LCD port.
|
|
|
|
|
|
2018-01-05 23:46:08 +00:00
|
|
|
config GPIO_WINBOND
|
|
|
|
|
tristate "Winbond Super I/O GPIO support"
|
2018-02-23 14:55:17 +00:00
|
|
|
select ISA_BUS_API
|
2018-01-05 23:46:08 +00:00
|
|
|
help
|
|
|
|
|
This option enables support for GPIOs found on Winbond Super I/O
|
|
|
|
|
chips.
|
|
|
|
|
Currently, only W83627UHG (also known as Nuvoton NCT6627UD) is
|
|
|
|
|
supported.
|
|
|
|
|
|
|
|
|
|
You will need to provide a module parameter "gpios", or a
|
|
|
|
|
boot-time parameter "gpio_winbond.gpios" with a bitmask of GPIO
|
|
|
|
|
ports to enable (bit 0 is GPIO1, bit 1 is GPIO2, etc.).
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called gpio-winbond.
|
|
|
|
|
|
2016-01-20 18:45:33 +00:00
|
|
|
config GPIO_WS16C48
|
|
|
|
|
tristate "WinSystems WS16C48 GPIO support"
|
2017-12-29 20:13:46 +00:00
|
|
|
select ISA_BUS_API
|
2016-01-20 18:45:33 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
2016-05-01 22:45:24 +00:00
|
|
|
Enables GPIO support for the WinSystems WS16C48. The base port
|
|
|
|
|
addresses for the devices may be configured via the base module
|
|
|
|
|
parameter. The interrupt line numbers for the devices may be
|
|
|
|
|
configured via the irq module parameter.
|
2016-01-20 18:45:33 +00:00
|
|
|
|
2015-10-30 09:32:19 +00:00
|
|
|
endmenu
|
|
|
|
|
|
2015-04-08 13:11:16 +00:00
|
|
|
menu "I2C GPIO expanders"
|
|
|
|
|
depends on I2C
|
2014-12-08 09:38:10 +00:00
|
|
|
|
2015-04-08 12:14:40 +00:00
|
|
|
config GPIO_ADP5588
|
|
|
|
|
tristate "ADP5588 I2C GPIO expander"
|
gpio: Add support for Intel ICHx/3100/Series[56] GPIO
This driver works on many Intel chipsets, including the ICH6, ICH7,
ICH8, ICH9, ICH10, 3100, Series 5/3400 (Ibex Peak), Series 6/C200
(Cougar Point), and NM10 (Tiger Point).
Additional Intel chipsets should be easily supported if needed, eg the
ICH1-5, EP80579, etc.
Tested on QM67 (Cougar Point), QM57 (Ibex Peak), 3100 (Whitmore Lake),
and NM10 (Tiger Point).
Includes work from Jean Delvare:
- Resource leak removal during module load/unload
- GPIO API bit value enforcement
Also includes code cleanup from Guenter Roeck and Grant Likely.
Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
Signed-off-by: Aaron Sierra <asierra@xes-inc.com>
Acked-by: Grant Likely <grant.likely@secretlab.ca>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2012-04-18 14:48:24 +00:00
|
|
|
help
|
2015-04-08 12:14:40 +00:00
|
|
|
This option enables support for 18 GPIOs found
|
|
|
|
|
on Analog Devices ADP5588 GPIO Expanders.
|
2010-03-02 09:48:55 +00:00
|
|
|
|
2015-04-08 12:14:40 +00:00
|
|
|
config GPIO_ADP5588_IRQ
|
|
|
|
|
bool "Interrupt controller support for ADP5588"
|
|
|
|
|
depends on GPIO_ADP5588=y
|
2019-05-23 22:00:41 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2013-09-09 09:59:51 +00:00
|
|
|
help
|
2015-04-08 12:14:40 +00:00
|
|
|
Say yes here to enable the adp5588 to be used as an interrupt
|
|
|
|
|
controller. It requires the driver to be built in the kernel.
|
2012-06-23 12:29:25 +00:00
|
|
|
|
2015-04-08 12:14:40 +00:00
|
|
|
config GPIO_ADNP
|
|
|
|
|
tristate "Avionic Design N-bit GPIO expander"
|
2015-11-01 09:43:16 +00:00
|
|
|
depends on OF_GPIO
|
2014-06-03 05:26:04 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
2015-04-08 12:14:40 +00:00
|
|
|
This option enables support for N GPIOs found on Avionic Design
|
|
|
|
|
I2C GPIO expanders. The register space will be extended by powers
|
|
|
|
|
of two, so the controller will need to accommodate for that. For
|
|
|
|
|
example: if a controller provides 48 pins, 6 registers will be
|
|
|
|
|
enough to represent all pins, but the driver will assume a
|
|
|
|
|
register layout for 64 pins (8 registers).
|
gpio: add LP3943 I2C GPIO expander driver
This is one of LP3943 MFD driver.
LP3943 is configurable as a GPIO expander, up to 16 GPIOs.
* Application note: how to configure LP3943 as a GPIO expander
http://www.ti.com/lit/an/snva287a/snva287a.pdf
* Supported GPIO controller operations
request, free, direction_input, direction_output, get and set
* GPIO direction register not supported
LP3943 doesn't have the GPIO direction register. It only provides input and
output status registers.
So, private data for the direction should be handled manually.
This variable is updated whenever the direction is changed and
used in 'get' operation.
* Pin assignment
A driver data, 'pin_used' is checked when a GPIO is requested.
If the GPIO is already assigned, then returns as failure.
If the GPIO is available, 'pin_used' is set.
When the GPIO is not used anymore, then it is cleared.
It is defined as unsigned long type for atomic bit operation APIs,
but only LSB 16bits are used because LP3943 has 16 outputs.
Signed-off-by: Milo Kim <milo.kim@ti.com>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Lee Jones <lee.jones@linaro.org>
2013-12-06 02:18:42 +00:00
|
|
|
|
2019-02-01 20:41:31 +00:00
|
|
|
config GPIO_GW_PLD
|
|
|
|
|
tristate "Gateworks PLD GPIO Expander"
|
|
|
|
|
depends on OF_GPIO
|
|
|
|
|
help
|
|
|
|
|
Say yes here to provide access to the Gateworks I2C PLD GPIO
|
|
|
|
|
Expander. This is used at least on the Cambria GW2358-4.
|
|
|
|
|
|
2010-03-05 21:44:33 +00:00
|
|
|
config GPIO_MAX7300
|
|
|
|
|
tristate "Maxim MAX7300 GPIO expander"
|
|
|
|
|
select GPIO_MAX730X
|
|
|
|
|
help
|
2013-05-19 06:25:48 +00:00
|
|
|
GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
|
2010-03-05 21:44:33 +00:00
|
|
|
|
2008-07-25 08:46:14 +00:00
|
|
|
config GPIO_MAX732X
|
|
|
|
|
tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support the MAX7319, MAX7320-7327 series of I2C
|
|
|
|
|
Port Expanders. Each IO port on these chips has a fixed role of
|
|
|
|
|
Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
|
|
|
|
|
Input and Output (designed by 'P'). The combinations are listed
|
|
|
|
|
below:
|
|
|
|
|
|
2019-03-05 00:35:31 +00:00
|
|
|
8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
|
|
|
|
|
max7322 (4I4O), max7323 (4P4O)
|
2008-07-25 08:46:14 +00:00
|
|
|
|
2019-03-05 00:35:31 +00:00
|
|
|
16 bits: max7324 (8I8O), max7325 (8P8O),
|
|
|
|
|
max7326 (4I12O), max7327 (4P12O)
|
2008-07-25 08:46:14 +00:00
|
|
|
|
|
|
|
|
Board setup code must specify the model to use, and the start
|
|
|
|
|
number for these GPIOs.
|
|
|
|
|
|
2010-05-26 21:42:16 +00:00
|
|
|
config GPIO_MAX732X_IRQ
|
|
|
|
|
bool "Interrupt controller support for MAX732x"
|
2013-08-30 07:39:53 +00:00
|
|
|
depends on GPIO_MAX732X=y
|
2015-01-30 10:32:01 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2010-05-26 21:42:16 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to enable the max732x to be used as an interrupt
|
|
|
|
|
controller. It requires the driver to be built in the kernel.
|
|
|
|
|
|
2012-01-30 06:31:20 +00:00
|
|
|
config GPIO_MC9S08DZ60
|
|
|
|
|
bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
|
2012-08-29 01:35:24 +00:00
|
|
|
depends on I2C=y && MACH_MX35_3DS
|
2012-01-30 06:31:20 +00:00
|
|
|
help
|
|
|
|
|
Select this to enable the MC9S08DZ60 GPIO driver
|
|
|
|
|
|
2008-02-06 09:39:03 +00:00
|
|
|
config GPIO_PCA953X
|
2014-02-13 12:59:23 +00:00
|
|
|
tristate "PCA95[357]x, PCA9698, TCA64xx, and MAX7310 I/O ports"
|
2018-12-16 17:38:58 +00:00
|
|
|
select REGMAP_I2C
|
2008-02-05 06:28:26 +00:00
|
|
|
help
|
2008-07-04 16:59:37 +00:00
|
|
|
Say yes here to provide access to several register-oriented
|
|
|
|
|
SMBus I/O expanders, made mostly by NXP or TI. Compatible
|
|
|
|
|
models include:
|
|
|
|
|
|
2019-03-05 00:35:31 +00:00
|
|
|
4 bits: pca9536, pca9537
|
2008-07-04 16:59:37 +00:00
|
|
|
|
2019-03-05 00:35:31 +00:00
|
|
|
8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
|
|
|
|
|
pca9556, pca9557, pca9574, tca6408, tca9554, xra1202
|
2008-07-04 16:59:37 +00:00
|
|
|
|
2019-03-05 00:35:31 +00:00
|
|
|
16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
|
|
|
|
|
tca6416
|
2008-02-05 06:28:26 +00:00
|
|
|
|
2019-03-05 00:35:31 +00:00
|
|
|
24 bits: tca6424
|
2014-02-07 22:35:48 +00:00
|
|
|
|
2019-03-05 00:35:31 +00:00
|
|
|
40 bits: pca9505, pca9698
|
2014-02-07 22:35:48 +00:00
|
|
|
|
2010-03-05 21:44:36 +00:00
|
|
|
config GPIO_PCA953X_IRQ
|
|
|
|
|
bool "Interrupt controller support for PCA953x"
|
|
|
|
|
depends on GPIO_PCA953X=y
|
2014-05-09 11:27:57 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2010-03-05 21:44:36 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to enable the pca953x to be used as an interrupt
|
|
|
|
|
controller. It requires the driver to be built in the kernel.
|
|
|
|
|
|
2008-02-05 06:28:24 +00:00
|
|
|
config GPIO_PCF857X
|
2008-07-21 21:21:34 +00:00
|
|
|
tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
|
2015-02-05 15:49:08 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2012-09-28 21:36:15 +00:00
|
|
|
select IRQ_DOMAIN
|
2008-02-05 06:28:24 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to provide access to most "quasi-bidirectional" I2C
|
|
|
|
|
GPIO expanders used for additional digital outputs or inputs.
|
|
|
|
|
Most of these parts are from NXP, though TI is a second source for
|
|
|
|
|
some of them. Compatible models include:
|
|
|
|
|
|
|
|
|
|
8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
|
2008-07-21 21:21:34 +00:00
|
|
|
pca9670, pca9672, pca9674, pca9674a,
|
2019-03-05 00:35:31 +00:00
|
|
|
max7328, max7329
|
2008-02-05 06:28:24 +00:00
|
|
|
|
|
|
|
|
16 bits: pcf8575, pcf8575c, pca8575,
|
|
|
|
|
pca9671, pca9673, pca9675
|
|
|
|
|
|
|
|
|
|
Your board setup code will need to declare the expanders in
|
|
|
|
|
use, and assign numbers to the GPIOs they expose. Those GPIOs
|
|
|
|
|
can then be used from drivers and other kernel code, just like
|
|
|
|
|
other GPIOs, but only accessible from task contexts.
|
|
|
|
|
|
|
|
|
|
This driver provides an in-kernel interface to those GPIOs using
|
|
|
|
|
platform-neutral GPIO calls.
|
|
|
|
|
|
2016-01-25 16:14:12 +00:00
|
|
|
config GPIO_TPIC2810
|
|
|
|
|
tristate "TPIC2810 8-Bit I2C GPO expander"
|
|
|
|
|
help
|
|
|
|
|
Say yes here to enable the GPO driver for the TI TPIC2810 chip.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called gpio-tpic2810.
|
|
|
|
|
|
2016-08-12 15:16:49 +00:00
|
|
|
config GPIO_TS4900
|
|
|
|
|
tristate "Technologic Systems FPGA I2C GPIO"
|
2016-10-14 12:24:09 +00:00
|
|
|
depends on SOC_IMX6 || COMPILE_TEST
|
2016-08-12 15:16:49 +00:00
|
|
|
select REGMAP_I2C
|
|
|
|
|
help
|
|
|
|
|
Say yes here to enabled the GPIO driver for Technologic's FPGA core.
|
|
|
|
|
Series supported include TS-4100, TS-4900, TS-7970 and TS-7990.
|
|
|
|
|
|
2015-04-08 13:11:16 +00:00
|
|
|
endmenu
|
|
|
|
|
|
|
|
|
|
menu "MFD GPIO expanders"
|
2015-04-08 12:51:23 +00:00
|
|
|
|
|
|
|
|
config GPIO_ADP5520
|
|
|
|
|
tristate "GPIO Support for ADP5520 PMIC"
|
|
|
|
|
depends on PMIC_ADP5520
|
|
|
|
|
help
|
|
|
|
|
This option enables support for on-chip GPIO found
|
|
|
|
|
on Analog Devices ADP5520 PMICs.
|
|
|
|
|
|
2016-06-02 17:52:24 +00:00
|
|
|
config GPIO_ALTERA_A10SR
|
|
|
|
|
tristate "Altera Arria10 System Resource GPIO"
|
|
|
|
|
depends on MFD_ALTERA_A10SR
|
|
|
|
|
help
|
|
|
|
|
Driver for Arria10 Development Kit GPIO expansion which
|
|
|
|
|
includes reads of pushbuttons and DIP switches as well
|
|
|
|
|
as writes to LEDs.
|
|
|
|
|
|
2015-04-08 12:51:23 +00:00
|
|
|
config GPIO_ARIZONA
|
|
|
|
|
tristate "Wolfson Microelectronics Arizona class devices"
|
|
|
|
|
depends on MFD_ARIZONA
|
|
|
|
|
help
|
|
|
|
|
Support for GPIOs on Wolfson Arizona class devices.
|
|
|
|
|
|
2019-06-03 07:26:45 +00:00
|
|
|
config GPIO_BD70528
|
|
|
|
|
tristate "ROHM BD70528 GPIO support"
|
|
|
|
|
depends on MFD_ROHM_BD70528
|
|
|
|
|
help
|
|
|
|
|
Support for GPIOs on ROHM BD70528 PMIC. There are four GPIOs
|
|
|
|
|
available on the ROHM PMIC in total. The GPIOs can also
|
|
|
|
|
generate interrupts.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called gpio-bd70528.
|
|
|
|
|
|
2017-04-25 18:32:09 +00:00
|
|
|
config GPIO_BD9571MWV
|
|
|
|
|
tristate "ROHM BD9571 GPIO support"
|
|
|
|
|
depends on MFD_BD9571MWV
|
|
|
|
|
help
|
|
|
|
|
Support for GPIOs on ROHM BD9571 PMIC. There are two GPIOs
|
|
|
|
|
available on the ROHM PMIC in total, both of which can also
|
|
|
|
|
generate interrupts.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called gpio-bd9571mwv.
|
|
|
|
|
|
2015-04-08 12:51:23 +00:00
|
|
|
config GPIO_CRYSTAL_COVE
|
|
|
|
|
tristate "GPIO support for Crystal Cove PMIC"
|
2016-11-20 17:37:25 +00:00
|
|
|
depends on (X86 || COMPILE_TEST) && INTEL_SOC_PMIC
|
2015-04-08 12:51:23 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Support for GPIO pins on Crystal Cove PMIC.
|
|
|
|
|
|
|
|
|
|
Say Yes if you have a Intel SoC based tablet with Crystal Cove PMIC
|
|
|
|
|
inside.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module will be
|
|
|
|
|
called gpio-crystalcove.
|
|
|
|
|
|
|
|
|
|
config GPIO_CS5535
|
|
|
|
|
tristate "AMD CS5535/CS5536 GPIO support"
|
2016-11-20 17:37:25 +00:00
|
|
|
depends on X86 || MIPS || COMPILE_TEST
|
2015-04-08 12:51:23 +00:00
|
|
|
depends on MFD_CS5535
|
|
|
|
|
help
|
|
|
|
|
The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
|
|
|
|
|
can be used for quite a number of things. The CS5535/6 is found on
|
|
|
|
|
AMD Geode and Lemote Yeeloong devices.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config GPIO_DA9052
|
|
|
|
|
tristate "Dialog DA9052 GPIO"
|
|
|
|
|
depends on PMIC_DA9052
|
|
|
|
|
help
|
|
|
|
|
Say yes here to enable the GPIO driver for the DA9052 chip.
|
|
|
|
|
|
|
|
|
|
config GPIO_DA9055
|
|
|
|
|
tristate "Dialog Semiconductor DA9055 GPIO"
|
|
|
|
|
depends on MFD_DA9055
|
|
|
|
|
help
|
|
|
|
|
Say yes here to enable the GPIO driver for the DA9055 chip.
|
|
|
|
|
|
|
|
|
|
The Dialog DA9055 PMIC chip has 3 GPIO pins that can be
|
|
|
|
|
be controller by this driver.
|
|
|
|
|
|
|
|
|
|
If driver is built as a module it will be called gpio-da9055.
|
|
|
|
|
|
|
|
|
|
config GPIO_DLN2
|
|
|
|
|
tristate "Diolan DLN2 GPIO support"
|
|
|
|
|
depends on MFD_DLN2
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
|
|
|
|
|
help
|
|
|
|
|
Select this option to enable GPIO driver for the Diolan DLN2
|
|
|
|
|
board.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called gpio-dln2.
|
|
|
|
|
|
2016-09-16 11:48:12 +00:00
|
|
|
config HTC_EGPIO
|
|
|
|
|
bool "HTC EGPIO support"
|
|
|
|
|
depends on GPIOLIB && ARM
|
|
|
|
|
help
|
2019-03-05 00:35:31 +00:00
|
|
|
This driver supports the CPLD egpio chip present on
|
|
|
|
|
several HTC phones. It provides basic support for input
|
|
|
|
|
pins, output pins, and irqs.
|
2016-09-16 11:48:12 +00:00
|
|
|
|
2015-04-08 12:51:23 +00:00
|
|
|
config GPIO_JANZ_TTL
|
|
|
|
|
tristate "Janz VMOD-TTL Digital IO Module"
|
|
|
|
|
depends on MFD_JANZ_CMODIO
|
|
|
|
|
help
|
|
|
|
|
This enables support for the Janz VMOD-TTL Digital IO module.
|
|
|
|
|
This driver provides support for driving the pins in output
|
|
|
|
|
mode only. Input mode is not supported.
|
|
|
|
|
|
|
|
|
|
config GPIO_KEMPLD
|
|
|
|
|
tristate "Kontron ETX / COMexpress GPIO"
|
|
|
|
|
depends on MFD_KEMPLD
|
|
|
|
|
help
|
|
|
|
|
This enables support for the PLD GPIO interface on some Kontron ETX
|
|
|
|
|
and COMexpress (ETXexpress) modules.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module will be
|
|
|
|
|
called gpio-kempld.
|
|
|
|
|
|
|
|
|
|
config GPIO_LP3943
|
|
|
|
|
tristate "TI/National Semiconductor LP3943 GPIO expander"
|
|
|
|
|
depends on MFD_LP3943
|
|
|
|
|
help
|
|
|
|
|
GPIO driver for LP3943 MFD.
|
|
|
|
|
LP3943 can be used as a GPIO expander which provides up to 16 GPIOs.
|
|
|
|
|
Open drain outputs are required for this usage.
|
|
|
|
|
|
2016-08-31 08:58:11 +00:00
|
|
|
config GPIO_LP873X
|
|
|
|
|
tristate "TI LP873X GPO"
|
|
|
|
|
depends on MFD_TI_LP873X
|
|
|
|
|
help
|
|
|
|
|
This driver supports the GPO on TI Lp873x PMICs. 2 GPOs are present
|
|
|
|
|
on LP873X PMICs.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module will be
|
2019-03-05 00:35:31 +00:00
|
|
|
called gpio-lp873x.
|
2016-08-31 08:58:11 +00:00
|
|
|
|
2017-06-15 06:33:11 +00:00
|
|
|
config GPIO_LP87565
|
|
|
|
|
tristate "TI LP87565 GPIO"
|
|
|
|
|
depends on MFD_TI_LP87565
|
|
|
|
|
help
|
|
|
|
|
This driver supports the GPIO on TI Lp873565 PMICs. 3 GPIOs are present
|
|
|
|
|
on LP87565 PMICs.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module will be
|
|
|
|
|
called gpio-lp87565.
|
|
|
|
|
|
2018-05-21 10:00:02 +00:00
|
|
|
config GPIO_MADERA
|
|
|
|
|
tristate "Cirrus Logic Madera class codecs"
|
|
|
|
|
depends on PINCTRL_MADERA
|
|
|
|
|
help
|
|
|
|
|
Support for GPIOs on Cirrus Logic Madera class codecs.
|
|
|
|
|
|
2016-05-13 05:19:14 +00:00
|
|
|
config GPIO_MAX77620
|
|
|
|
|
tristate "GPIO support for PMIC MAX77620 and MAX20024"
|
|
|
|
|
depends on MFD_MAX77620
|
|
|
|
|
help
|
|
|
|
|
GPIO driver for MAX77620 and MAX20024 PMIC from Maxim Semiconductor.
|
|
|
|
|
MAX77620 PMIC has 8 pins that can be configured as GPIOs. The
|
|
|
|
|
driver also provides interrupt support for each of the gpios.
|
|
|
|
|
Say yes here to enable the max77620 to be used as gpio controller.
|
|
|
|
|
|
2019-04-23 09:04:48 +00:00
|
|
|
config GPIO_MAX77650
|
|
|
|
|
tristate "Maxim MAX77650/77651 GPIO support"
|
|
|
|
|
depends on MFD_MAX77650
|
|
|
|
|
help
|
|
|
|
|
GPIO driver for MAX77650/77651 PMIC from Maxim Semiconductor.
|
|
|
|
|
These chips have a single pin that can be configured as GPIO.
|
|
|
|
|
|
2015-04-08 12:51:23 +00:00
|
|
|
config GPIO_MSIC
|
|
|
|
|
bool "Intel MSIC mixed signal gpio support"
|
2016-11-20 17:37:25 +00:00
|
|
|
depends on (X86 || COMPILE_TEST) && MFD_INTEL_MSIC
|
2015-04-08 12:51:23 +00:00
|
|
|
help
|
|
|
|
|
Enable support for GPIO on intel MSIC controllers found in
|
|
|
|
|
intel MID devices
|
|
|
|
|
|
|
|
|
|
config GPIO_PALMAS
|
|
|
|
|
bool "TI PALMAS series PMICs GPIO"
|
|
|
|
|
depends on MFD_PALMAS
|
|
|
|
|
help
|
|
|
|
|
Select this option to enable GPIO driver for the TI PALMAS
|
|
|
|
|
series chip family.
|
|
|
|
|
|
2012-05-14 07:16:12 +00:00
|
|
|
config GPIO_RC5T583
|
|
|
|
|
bool "RICOH RC5T583 GPIO"
|
|
|
|
|
depends on MFD_RC5T583
|
|
|
|
|
help
|
|
|
|
|
Select this option to enable GPIO driver for the Ricoh RC5T583
|
|
|
|
|
chip family.
|
|
|
|
|
This driver provides the support for driving/reading the gpio pins
|
|
|
|
|
of RC5T583 device through standard gpio library.
|
|
|
|
|
|
2010-07-02 11:22:09 +00:00
|
|
|
config GPIO_STMPE
|
|
|
|
|
bool "STMPE GPIOs"
|
|
|
|
|
depends on MFD_STMPE
|
2015-01-13 07:00:29 +00:00
|
|
|
depends on OF_GPIO
|
2014-04-15 21:38:56 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2010-07-02 11:22:09 +00:00
|
|
|
help
|
|
|
|
|
This enables support for the GPIOs found on the STMPE I/O
|
|
|
|
|
Expanders.
|
|
|
|
|
|
2010-12-13 04:03:13 +00:00
|
|
|
config GPIO_TC3589X
|
|
|
|
|
bool "TC3589X GPIOs"
|
|
|
|
|
depends on MFD_TC3589X
|
2015-03-19 14:52:45 +00:00
|
|
|
depends on OF_GPIO
|
2014-04-09 11:38:33 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2010-05-10 21:43:47 +00:00
|
|
|
help
|
2010-12-13 04:03:13 +00:00
|
|
|
This enables support for the GPIOs found on the TC3589X
|
2010-05-10 21:43:47 +00:00
|
|
|
I/O Expander.
|
|
|
|
|
|
2015-04-08 12:51:23 +00:00
|
|
|
config GPIO_TIMBERDALE
|
|
|
|
|
bool "Support for timberdale GPIO IP"
|
|
|
|
|
depends on MFD_TIMBERDALE
|
|
|
|
|
---help---
|
|
|
|
|
Add support for the GPIO IP in the timberdale FPGA.
|
|
|
|
|
|
2016-02-06 16:12:10 +00:00
|
|
|
config GPIO_TPS65086
|
|
|
|
|
tristate "TI TPS65086 GPO"
|
|
|
|
|
depends on MFD_TPS65086
|
|
|
|
|
help
|
|
|
|
|
This driver supports the GPO on TI TPS65086x PMICs.
|
|
|
|
|
|
2016-01-30 17:06:44 +00:00
|
|
|
config GPIO_TPS65218
|
|
|
|
|
tristate "TPS65218 GPIO"
|
|
|
|
|
depends on MFD_TPS65218
|
|
|
|
|
help
|
|
|
|
|
Select this option to enable GPIO driver for the TPS65218
|
|
|
|
|
chip family.
|
|
|
|
|
|
2015-04-08 12:51:23 +00:00
|
|
|
config GPIO_TPS6586X
|
|
|
|
|
bool "TPS6586X GPIO"
|
|
|
|
|
depends on MFD_TPS6586X
|
|
|
|
|
help
|
|
|
|
|
Select this option to enable GPIO driver for the TPS6586X
|
|
|
|
|
chip family.
|
|
|
|
|
|
|
|
|
|
config GPIO_TPS65910
|
|
|
|
|
bool "TPS65910 GPIO"
|
|
|
|
|
depends on MFD_TPS65910
|
|
|
|
|
help
|
|
|
|
|
Select this option to enable GPIO driver for the TPS65910
|
|
|
|
|
chip family.
|
|
|
|
|
|
2011-06-09 19:50:19 +00:00
|
|
|
config GPIO_TPS65912
|
|
|
|
|
tristate "TI TPS65912 GPIO"
|
2016-01-25 15:43:47 +00:00
|
|
|
depends on MFD_TPS65912
|
2011-06-09 19:50:19 +00:00
|
|
|
help
|
|
|
|
|
This driver supports TPS65912 gpio chip
|
|
|
|
|
|
2017-07-29 00:30:25 +00:00
|
|
|
config GPIO_TPS68470
|
|
|
|
|
bool "TPS68470 GPIO"
|
|
|
|
|
depends on MFD_TPS68470
|
|
|
|
|
help
|
|
|
|
|
Select this option to enable GPIO driver for the TPS68470
|
|
|
|
|
chip family.
|
|
|
|
|
There are 7 GPIOs and few sensor related GPIOs supported
|
|
|
|
|
by the TPS68470. While the 7 GPIOs can be configured as
|
|
|
|
|
input or output as appropriate, the sensor related GPIOs
|
|
|
|
|
are "output only" GPIOs.
|
|
|
|
|
|
|
|
|
|
This driver config is bool, as the GPIO functionality
|
|
|
|
|
of the TPS68470 must be available before dependent
|
|
|
|
|
drivers are loaded.
|
|
|
|
|
|
2019-01-25 01:09:07 +00:00
|
|
|
config GPIO_TQMX86
|
|
|
|
|
tristate "TQ-Systems QTMX86 GPIO"
|
|
|
|
|
depends on MFD_TQMX86 || COMPILE_TEST
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
This driver supports GPIO on the TQMX86 IO controller.
|
|
|
|
|
|
2008-10-20 21:51:46 +00:00
|
|
|
config GPIO_TWL4030
|
|
|
|
|
tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
|
|
|
|
|
depends on TWL4030_CORE
|
|
|
|
|
help
|
|
|
|
|
Say yes here to access the GPIO signals of various multi-function
|
|
|
|
|
power management chips from Texas Instruments.
|
|
|
|
|
|
2012-08-16 12:13:15 +00:00
|
|
|
config GPIO_TWL6040
|
|
|
|
|
tristate "TWL6040 GPO"
|
|
|
|
|
depends on TWL6040_CORE
|
|
|
|
|
help
|
|
|
|
|
Say yes here to access the GPO signals of twl6040
|
|
|
|
|
audio chip from Texas Instruments.
|
|
|
|
|
|
2015-04-08 12:51:23 +00:00
|
|
|
config GPIO_UCB1400
|
|
|
|
|
tristate "Philips UCB1400 GPIO"
|
|
|
|
|
depends on UCB1400_CORE
|
|
|
|
|
help
|
|
|
|
|
This enables support for the Philips UCB1400 GPIO pins.
|
|
|
|
|
The UCB1400 is an AC97 audio codec.
|
|
|
|
|
|
2016-07-25 21:59:38 +00:00
|
|
|
config GPIO_WHISKEY_COVE
|
|
|
|
|
tristate "GPIO support for Whiskey Cove PMIC"
|
2017-04-04 12:38:56 +00:00
|
|
|
depends on (X86 || COMPILE_TEST) && INTEL_SOC_PMIC_BXTWC
|
2016-07-25 21:59:38 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Support for GPIO pins on Whiskey Cove PMIC.
|
|
|
|
|
|
|
|
|
|
Say Yes if you have a Intel SoC based tablet with Whiskey Cove PMIC
|
|
|
|
|
inside.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module will be
|
|
|
|
|
called gpio-wcove.
|
|
|
|
|
|
2009-07-27 13:46:00 +00:00
|
|
|
config GPIO_WM831X
|
|
|
|
|
tristate "WM831x GPIOs"
|
|
|
|
|
depends on MFD_WM831X
|
|
|
|
|
help
|
|
|
|
|
Say yes here to access the GPIO signals of WM831x power management
|
|
|
|
|
chips from Wolfson Microelectronics.
|
|
|
|
|
|
2010-01-07 16:10:08 +00:00
|
|
|
config GPIO_WM8350
|
|
|
|
|
tristate "WM8350 GPIOs"
|
|
|
|
|
depends on MFD_WM8350
|
|
|
|
|
help
|
|
|
|
|
Say yes here to access the GPIO signals of WM8350 power management
|
|
|
|
|
chips from Wolfson Microelectronics.
|
|
|
|
|
|
2010-01-29 18:20:30 +00:00
|
|
|
config GPIO_WM8994
|
|
|
|
|
tristate "WM8994 GPIOs"
|
|
|
|
|
depends on MFD_WM8994
|
|
|
|
|
help
|
|
|
|
|
Say yes here to access the GPIO signals of WM8994 audio hub
|
|
|
|
|
CODECs from Wolfson Microelectronics.
|
|
|
|
|
|
2015-04-08 13:11:16 +00:00
|
|
|
endmenu
|
2009-09-22 23:46:39 +00:00
|
|
|
|
2015-04-08 13:11:16 +00:00
|
|
|
menu "PCI GPIO expanders"
|
|
|
|
|
depends on PCI
|
2010-10-27 22:33:19 +00:00
|
|
|
|
2015-04-08 12:30:37 +00:00
|
|
|
config GPIO_AMD8111
|
|
|
|
|
tristate "AMD 8111 GPIO driver"
|
2016-11-20 17:37:25 +00:00
|
|
|
depends on X86 || COMPILE_TEST
|
2012-09-18 08:57:10 +00:00
|
|
|
help
|
2015-04-08 12:30:37 +00:00
|
|
|
The AMD 8111 south bridge contains 32 GPIO pins which can be used.
|
2008-07-25 08:46:10 +00:00
|
|
|
|
2015-04-08 12:30:37 +00:00
|
|
|
Note, that usually system firmware/ACPI handles GPIO pins on their
|
|
|
|
|
own and users might easily break their systems with uncarefull usage
|
|
|
|
|
of this driver!
|
2009-12-15 02:00:32 +00:00
|
|
|
|
2015-04-08 12:30:37 +00:00
|
|
|
If unsure, say N
|
2009-12-15 02:00:32 +00:00
|
|
|
|
2008-07-25 08:46:10 +00:00
|
|
|
config GPIO_BT8XX
|
|
|
|
|
tristate "BT8XX GPIO abuser"
|
2015-12-06 20:52:45 +00:00
|
|
|
depends on VIDEO_BT848=n
|
2008-07-25 08:46:10 +00:00
|
|
|
help
|
2014-03-11 10:23:44 +00:00
|
|
|
The BT8xx frame grabber chip has 24 GPIO pins that can be abused
|
2008-07-25 08:46:10 +00:00
|
|
|
as a cheap PCI GPIO card.
|
|
|
|
|
|
|
|
|
|
This chip can be found on Miro, Hauppauge and STB TV-cards.
|
|
|
|
|
|
|
|
|
|
The card needs to be physically altered for using it as a
|
|
|
|
|
GPIO card. For more information on how to build a GPIO card
|
|
|
|
|
from a BT8xx TV card, see the documentation file at
|
2019-10-04 16:40:55 +00:00
|
|
|
Documentation/driver-api/gpio/bt8xxgpio.rst
|
2008-07-25 08:46:10 +00:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2013-10-04 20:01:41 +00:00
|
|
|
config GPIO_INTEL_MID
|
2016-07-07 20:45:08 +00:00
|
|
|
bool "Intel MID GPIO support"
|
|
|
|
|
depends on X86_INTEL_MID
|
2014-05-29 14:52:46 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2009-09-22 23:46:36 +00:00
|
|
|
help
|
2016-07-07 20:45:08 +00:00
|
|
|
Say Y here to support Intel MID GPIO.
|
2009-09-22 23:46:36 +00:00
|
|
|
|
2016-07-08 11:08:23 +00:00
|
|
|
config GPIO_MERRIFIELD
|
|
|
|
|
tristate "Intel Merrifield GPIO support"
|
|
|
|
|
depends on X86_INTEL_MID
|
2014-05-29 14:52:46 +00:00
|
|
|
select GPIOLIB_IRQCHIP
|
2009-09-22 23:46:36 +00:00
|
|
|
help
|
2016-07-08 11:08:23 +00:00
|
|
|
Say Y here to support Intel Merrifield GPIO.
|
2009-09-22 23:46:36 +00:00
|
|
|
|
2019-03-26 14:42:48 +00:00
|
|
|
config GPIO_MLXBF
|
|
|
|
|
tristate "Mellanox BlueField SoC GPIO"
|
2019-03-27 14:15:15 +00:00
|
|
|
depends on (MELLANOX_PLATFORM && ARM64 && ACPI) || (64BIT && COMPILE_TEST)
|
2019-03-26 14:42:48 +00:00
|
|
|
select GPIO_GENERIC
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want GPIO support on Mellanox BlueField SoC.
|
|
|
|
|
|
2015-04-08 12:30:37 +00:00
|
|
|
config GPIO_ML_IOH
|
|
|
|
|
tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
|
2016-11-20 17:37:25 +00:00
|
|
|
depends on X86 || COMPILE_TEST
|
2015-04-08 12:30:37 +00:00
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
help
|
|
|
|
|
ML7213 is companion chip for Intel Atom E6xx series.
|
|
|
|
|
This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
|
|
|
|
|
Hub) which is for IVI(In-Vehicle Infotainment) use.
|
|
|
|
|
This driver can access the IOH's GPIO device.
|
|
|
|
|
|
2010-10-27 22:33:21 +00:00
|
|
|
config GPIO_PCH
|
2011-10-28 00:23:32 +00:00
|
|
|
tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
|
2015-12-06 20:52:45 +00:00
|
|
|
depends on X86_32 || MIPS || COMPILE_TEST
|
2011-07-21 00:19:59 +00:00
|
|
|
select GENERIC_IRQ_CHIP
|
2010-10-27 22:33:21 +00:00
|
|
|
help
|
|
|
|
|
This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
|
|
|
|
|
which is an IOH(Input/Output Hub) for x86 embedded processor.
|
|
|
|
|
This driver can access PCH GPIO device.
|
|
|
|
|
|
2011-10-28 00:23:32 +00:00
|
|
|
This driver also can be used for LAPIS Semiconductor IOH(Input/
|
|
|
|
|
Output Hub), ML7223 and ML7831.
|
2011-05-09 10:58:49 +00:00
|
|
|
ML7223 IOH is for MP(Media Phone) use.
|
2011-10-28 00:23:32 +00:00
|
|
|
ML7831 IOH is for general purpose use.
|
|
|
|
|
ML7223/ML7831 is companion chip for Intel Atom E6xx series.
|
|
|
|
|
ML7223/ML7831 is completely compatible for Intel EG20T PCH.
|
2011-05-09 10:58:49 +00:00
|
|
|
|
2017-02-01 20:37:55 +00:00
|
|
|
config GPIO_PCI_IDIO_16
|
|
|
|
|
tristate "ACCES PCI-IDIO-16 GPIO support"
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Enables GPIO support for the ACCES PCI-IDIO-16. An interrupt is
|
|
|
|
|
generated when any of the inputs change state (low to high or high to
|
|
|
|
|
low). Input filter control is not supported by this driver, and the
|
|
|
|
|
input filters are deactivated by this driver.
|
|
|
|
|
|
2018-01-09 22:21:45 +00:00
|
|
|
config GPIO_PCIE_IDIO_24
|
|
|
|
|
tristate "ACCES PCIe-IDIO-24 GPIO support"
|
|
|
|
|
select GPIOLIB_IRQCHIP
|
|
|
|
|
help
|
|
|
|
|
Enables GPIO support for the ACCES PCIe-IDIO-24 family (PCIe-IDIO-24,
|
|
|
|
|
PCIe-IDI-24, PCIe-IDO-24, PCIe-IDIO-12). An interrupt is generated
|
|
|
|
|
when any of the inputs change state (low to high or high to low).
|
|
|
|
|
Input filter control is not supported by this driver, and the input
|
|
|
|
|
filters are deactivated by this driver.
|
|
|
|
|
|
2015-04-08 12:30:37 +00:00
|
|
|
config GPIO_RDC321X
|
|
|
|
|
tristate "RDC R-321x GPIO support"
|
|
|
|
|
select MFD_CORE
|
|
|
|
|
select MFD_RDC321X
|
2011-01-13 01:00:22 +00:00
|
|
|
help
|
2015-04-08 12:30:37 +00:00
|
|
|
Support for the RDC R321x SoC GPIOs over southbridge
|
|
|
|
|
PCI configuration space.
|
2011-01-13 01:00:22 +00:00
|
|
|
|
2011-06-27 07:26:23 +00:00
|
|
|
config GPIO_SODAVILLE
|
|
|
|
|
bool "Intel Sodaville GPIO support"
|
2015-12-06 20:52:45 +00:00
|
|
|
depends on X86 && OF
|
2011-06-27 07:26:23 +00:00
|
|
|
select GPIO_GENERIC
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
help
|
|
|
|
|
Say Y here to support Intel Sodaville GPIO.
|
|
|
|
|
|
2015-04-08 13:11:16 +00:00
|
|
|
endmenu
|
2009-12-16 00:46:18 +00:00
|
|
|
|
2015-04-08 13:11:16 +00:00
|
|
|
menu "SPI GPIO expanders"
|
|
|
|
|
depends on SPI_MASTER
|
2010-03-21 00:06:09 +00:00
|
|
|
|
2015-04-08 12:34:51 +00:00
|
|
|
config GPIO_74X164
|
|
|
|
|
tristate "74x164 serial-in/parallel-out 8-bits shift register"
|
2016-08-16 10:07:31 +00:00
|
|
|
depends on OF_GPIO
|
2015-04-08 12:34:51 +00:00
|
|
|
help
|
|
|
|
|
Driver for 74x164 compatible serial-in/parallel-out 8-outputs
|
|
|
|
|
shift registers. This driver can be used to provide access
|
|
|
|
|
to more gpio outputs.
|
2008-02-05 06:28:17 +00:00
|
|
|
|
2017-10-12 10:40:10 +00:00
|
|
|
config GPIO_MAX3191X
|
|
|
|
|
tristate "Maxim MAX3191x industrial serializer"
|
|
|
|
|
select CRC8
|
|
|
|
|
help
|
|
|
|
|
GPIO driver for Maxim MAX31910, MAX31911, MAX31912, MAX31913,
|
|
|
|
|
MAX31953 and MAX31963 industrial serializer, a daisy-chainable
|
|
|
|
|
chip to make 8 digital 24V inputs available via SPI. Supports
|
|
|
|
|
CRC checksums to guard against electromagnetic interference,
|
|
|
|
|
as well as undervoltage and overtemperature detection.
|
|
|
|
|
|
2008-07-21 21:21:34 +00:00
|
|
|
config GPIO_MAX7301
|
|
|
|
|
tristate "Maxim MAX7301 GPIO expander"
|
2010-03-05 21:44:33 +00:00
|
|
|
select GPIO_MAX730X
|
2008-07-21 21:21:34 +00:00
|
|
|
help
|
2010-03-05 21:44:33 +00:00
|
|
|
GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
|
2008-07-21 21:21:34 +00:00
|
|
|
|
2009-09-22 23:46:34 +00:00
|
|
|
config GPIO_MC33880
|
|
|
|
|
tristate "Freescale MC33880 high-side/low-side switch"
|
|
|
|
|
help
|
|
|
|
|
SPI driver for Freescale MC33880 high-side/low-side switch.
|
|
|
|
|
This provides GPIO interface supporting inputs and outputs.
|
|
|
|
|
|
2016-01-25 16:37:31 +00:00
|
|
|
config GPIO_PISOSR
|
|
|
|
|
tristate "Generic parallel-in/serial-out shift register"
|
|
|
|
|
help
|
|
|
|
|
GPIO driver for SPI compatible parallel-in/serial-out shift
|
|
|
|
|
registers. These are input only devices.
|
|
|
|
|
|
2017-05-15 05:58:25 +00:00
|
|
|
config GPIO_XRA1403
|
|
|
|
|
tristate "EXAR XRA1403 16-bit GPIO expander"
|
2017-05-30 11:13:17 +00:00
|
|
|
select REGMAP_SPI
|
2017-05-15 05:58:25 +00:00
|
|
|
help
|
|
|
|
|
GPIO driver for EXAR XRA1403 16-bit SPI-based GPIO expander.
|
|
|
|
|
|
2019-08-12 16:11:17 +00:00
|
|
|
config GPIO_MOXTET
|
|
|
|
|
tristate "Turris Mox Moxtet bus GPIO expander"
|
|
|
|
|
depends on MOXTET
|
|
|
|
|
help
|
|
|
|
|
Say yes here if you are building for the Turris Mox router.
|
|
|
|
|
This is the driver needed for configuring the GPIOs via the Moxtet
|
|
|
|
|
bus. For example the Mox module with SFP cage needs this driver
|
|
|
|
|
so that phylink can use corresponding GPIOs.
|
|
|
|
|
|
2015-11-01 09:50:19 +00:00
|
|
|
endmenu
|
|
|
|
|
|
2015-04-08 13:11:16 +00:00
|
|
|
menu "USB GPIO expanders"
|
|
|
|
|
depends on USB
|
2012-11-05 14:48:24 +00:00
|
|
|
|
|
|
|
|
config GPIO_VIPERBOARD
|
|
|
|
|
tristate "Viperboard GPIO a & b support"
|
2015-12-06 20:52:45 +00:00
|
|
|
depends on MFD_VIPERBOARD
|
2012-11-05 14:48:24 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to access the GPIO signals of Nano River
|
|
|
|
|
Technologies Viperboard. There are two GPIO chips on the
|
|
|
|
|
board: gpioa and gpiob.
|
2019-03-05 00:35:31 +00:00
|
|
|
See viperboard API specification and Nano
|
|
|
|
|
River Tech's viperboard.h for detailed meaning
|
|
|
|
|
of the module parameters.
|
2012-11-05 14:48:24 +00:00
|
|
|
|
2015-04-08 13:11:16 +00:00
|
|
|
endmenu
|
2014-11-06 13:48:05 +00:00
|
|
|
|
2019-03-13 10:37:17 +00:00
|
|
|
config GPIO_MOCKUP
|
|
|
|
|
tristate "GPIO Testing Driver"
|
|
|
|
|
select IRQ_SIM
|
|
|
|
|
help
|
|
|
|
|
This enables GPIO Testing driver, which provides a way to test GPIO
|
|
|
|
|
subsystem through sysfs(or char device) and debugfs. GPIO_SYSFS
|
|
|
|
|
must be selected for this test.
|
|
|
|
|
User could use it through the script in
|
|
|
|
|
tools/testing/selftests/gpio/gpio-mockup.sh. Reference the usage in
|
|
|
|
|
it.
|
|
|
|
|
|
2008-07-25 08:46:11 +00:00
|
|
|
endif
|
