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
|
|
|
config ARCH_WANT_OPTIONAL_GPIOLIB
|
2008-02-05 06:28:17 +00:00
|
|
|
bool
|
2008-07-25 08:46:11 +00:00
|
|
|
help
|
|
|
|
|
Select this config option from the architecture Kconfig, if
|
|
|
|
|
it is possible to use gpiolib on the architecture, but let the
|
|
|
|
|
user decide whether to actually build it or not.
|
|
|
|
|
Select this instead of ARCH_REQUIRE_GPIOLIB, if your architecture does
|
|
|
|
|
not depend on GPIOs being available, but rather let the user
|
|
|
|
|
decide whether he needs it or not.
|
|
|
|
|
|
|
|
|
|
config ARCH_REQUIRE_GPIOLIB
|
|
|
|
|
bool
|
|
|
|
|
select GPIOLIB
|
2008-02-05 06:28:17 +00:00
|
|
|
help
|
|
|
|
|
Platforms select gpiolib if they use this infrastructure
|
|
|
|
|
for all their GPIOs, usually starting with ones integrated
|
|
|
|
|
into SOC processors.
|
2008-07-25 08:46:11 +00:00
|
|
|
Selecting this from the architecture code will cause the gpiolib
|
|
|
|
|
code to always get built in.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
menuconfig GPIOLIB
|
|
|
|
|
bool "GPIO Support"
|
|
|
|
|
depends on ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB
|
|
|
|
|
select GENERIC_GPIO
|
|
|
|
|
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
|
|
|
|
2012-04-07 20:31:33 +00:00
|
|
|
config OF_GPIO
|
|
|
|
|
def_bool y
|
2012-11-06 23:33:33 +00:00
|
|
|
depends on OF
|
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
|
|
|
|
|
|
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
|
|
|
|
|
Say Y here to add a sysfs interface for GPIOs.
|
|
|
|
|
|
|
|
|
|
This is mostly useful to work around omissions in a system's
|
|
|
|
|
kernel support. Those are common in custom and semicustom
|
|
|
|
|
hardware assembled using standard kernels with a minimum of
|
|
|
|
|
custom patches. In those cases, userspace code may import
|
|
|
|
|
a given GPIO from the kernel, if no kernel driver requested it.
|
|
|
|
|
|
|
|
|
|
Kernel drivers may also request that a particular GPIO be
|
|
|
|
|
exported to userspace; this can be useful when debugging.
|
|
|
|
|
|
2011-06-05 00:38:28 +00:00
|
|
|
config GPIO_GENERIC
|
|
|
|
|
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
|
|
|
|
2011-07-06 10:32:13 +00:00
|
|
|
config GPIO_DA9052
|
|
|
|
|
tristate "Dialog DA9052 GPIO"
|
2012-08-29 06:57:46 +00:00
|
|
|
depends on PMIC_DA9052
|
2011-07-06 10:32:13 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to enable the GPIO driver for the DA9052 chip.
|
|
|
|
|
|
2012-09-14 13:30:16 +00:00
|
|
|
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.
|
|
|
|
|
|
2010-03-05 21:44:33 +00:00
|
|
|
config GPIO_MAX730X
|
|
|
|
|
tristate
|
|
|
|
|
|
2011-05-20 06:40:19 +00:00
|
|
|
comment "Memory mapped GPIO drivers:"
|
2008-11-12 21:25:38 +00:00
|
|
|
|
2012-10-09 16:05:56 +00:00
|
|
|
config GPIO_CLPS711X
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on ARCH_CLPS711X
|
|
|
|
|
|
2011-06-05 00:38:28 +00:00
|
|
|
config GPIO_GENERIC_PLATFORM
|
|
|
|
|
tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
|
|
|
|
|
select GPIO_GENERIC
|
2010-10-27 22:33:15 +00:00
|
|
|
help
|
2011-06-05 00:38:28 +00:00
|
|
|
Say yes here to support basic platform_device memory-mapped GPIO controllers.
|
2010-10-27 22:33:15 +00:00
|
|
|
|
2010-03-05 21:44:39 +00:00
|
|
|
config GPIO_IT8761E
|
|
|
|
|
tristate "IT8761E GPIO support"
|
2012-01-11 18:03:41 +00:00
|
|
|
depends on X86 # unconditional access to IO space.
|
2010-03-05 21:44:39 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to support GPIO functionality of IT8761E super I/O chip.
|
|
|
|
|
|
2012-05-17 06:22:23 +00:00
|
|
|
config GPIO_EM
|
|
|
|
|
tristate "Emma Mobile GPIO"
|
|
|
|
|
depends on ARM
|
|
|
|
|
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
|
2011-06-01 17:09:19 +00:00
|
|
|
|
2012-05-11 16:48:39 +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
|
|
|
|
|
bool "MPC512x/MPC8xxx GPIO support"
|
|
|
|
|
depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
|
|
|
|
|
FSL_SOC_BOOKE || PPC_86xx
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you're going to use hardware that connects to the
|
|
|
|
|
MPC512x/831x/834x/837x/8572/8610 GPIOs.
|
|
|
|
|
|
2011-05-16 20:57:39 +00:00
|
|
|
config GPIO_MSM_V1
|
|
|
|
|
tristate "Qualcomm MSM GPIO v1"
|
2012-05-31 11:12:57 +00:00
|
|
|
depends on GPIOLIB && ARCH_MSM && (ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50)
|
2011-05-16 20:57:39 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to support the GPIO interface on ARM v6 based
|
|
|
|
|
Qualcomm MSM chips. Most of the pins on the MSM can be
|
|
|
|
|
selected for GPIO, and are controlled by this driver.
|
|
|
|
|
|
2011-05-16 22:53:38 +00:00
|
|
|
config GPIO_MSM_V2
|
|
|
|
|
tristate "Qualcomm MSM GPIO v2"
|
|
|
|
|
depends on GPIOLIB && ARCH_MSM
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support the GPIO interface on ARM v7 based
|
|
|
|
|
Qualcomm MSM chips. Most of the pins on the MSM can be
|
|
|
|
|
selected for GPIO, and are controlled by this driver.
|
|
|
|
|
|
2012-09-19 20:52:58 +00:00
|
|
|
config GPIO_MVEBU
|
|
|
|
|
def_bool y
|
2012-11-17 16:00:43 +00:00
|
|
|
depends on PLAT_ORION
|
2012-12-19 11:31:11 +00:00
|
|
|
depends on OF
|
2012-09-19 20:52:58 +00:00
|
|
|
select GPIO_GENERIC
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
|
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
|
|
|
|
2009-06-18 23:48:58 +00:00
|
|
|
config GPIO_PL061
|
|
|
|
|
bool "PrimeCell PL061 GPIO support"
|
2012-11-23 15:08:24 +00:00
|
|
|
depends on ARM && ARM_AMBA
|
2011-10-21 13:05:53 +00:00
|
|
|
select GENERIC_IRQ_CHIP
|
2009-06-18 23:48:58 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to support the PrimeCell PL061 GPIO 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
|
|
|
|
|
|
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
|
|
|
|
|
|
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.
|
|
|
|
|
|
2012-12-08 02:36:34 +00:00
|
|
|
config GPIO_TS5500
|
|
|
|
|
tristate "TS-5500 DIO blocks and compatibles"
|
|
|
|
|
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.
|
|
|
|
|
|
2012-08-08 01:05:55 +00:00
|
|
|
config GPIO_VT8500
|
|
|
|
|
bool "VIA/Wondermedia SoC GPIO Support"
|
|
|
|
|
depends on ARCH_VT8500
|
|
|
|
|
help
|
|
|
|
|
Say yes here to support the VT8500/WM8505/WM8650 GPIO controller.
|
|
|
|
|
|
2008-11-12 21:25:38 +00:00
|
|
|
config GPIO_XILINX
|
|
|
|
|
bool "Xilinx GPIO support"
|
2009-05-11 13:49:12 +00:00
|
|
|
depends on PPC_OF || MICROBLAZE
|
2008-11-12 21:25:38 +00:00
|
|
|
help
|
|
|
|
|
Say yes here to support the Xilinx FPGA GPIO device
|
|
|
|
|
|
2009-06-29 02:11:05 +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
|
|
|
|
|
|
2010-03-02 09:48:55 +00:00
|
|
|
config GPIO_SCH
|
2012-05-22 20:54:20 +00:00
|
|
|
tristate "Intel SCH/TunnelCreek/Centerton GPIO"
|
2011-05-20 06:40:17 +00:00
|
|
|
depends on PCI && X86
|
2010-03-05 17:43:06 +00:00
|
|
|
select MFD_CORE
|
2010-03-02 09:48:55 +00:00
|
|
|
select LPC_SCH
|
|
|
|
|
help
|
2012-05-22 20:54:20 +00:00
|
|
|
Say yes here to support GPIO interface on Intel Poulsbo SCH,
|
|
|
|
|
Intel Tunnel Creek processor or Intel Centerton processor.
|
2010-03-02 09:48:55 +00:00
|
|
|
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.
|
2011-03-14 10:53:05 +00:00
|
|
|
The Intel Tunnel Creek processor has 5 GPIOs powered by the
|
|
|
|
|
core power rail and 9 from suspend power supply.
|
2012-05-22 20:54:20 +00:00
|
|
|
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.
|
2010-03-02 09:48:55 +00:00
|
|
|
|
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
|
|
|
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.
|
2010-03-02 09:48:55 +00:00
|
|
|
|
2010-09-30 20:55:48 +00:00
|
|
|
config GPIO_VX855
|
|
|
|
|
tristate "VIA VX855/VX875 GPIO"
|
2011-09-02 14:43:36 +00:00
|
|
|
depends on PCI
|
2010-09-30 20:55:48 +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.
|
|
|
|
|
|
2012-03-12 17:12:58 +00:00
|
|
|
config GPIO_GE_FPGA
|
|
|
|
|
bool "GE FPGA based GPIO"
|
|
|
|
|
depends on GE_FPGA
|
|
|
|
|
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.
|
|
|
|
|
|
2008-02-05 06:28:17 +00:00
|
|
|
comment "I2C GPIO expanders:"
|
|
|
|
|
|
2012-06-23 12:29:25 +00:00
|
|
|
config GPIO_ARIZONA
|
|
|
|
|
tristate "Wolfson Microelectronics Arizona class devices"
|
|
|
|
|
depends on MFD_ARIZONA
|
|
|
|
|
help
|
|
|
|
|
Support for GPIOs on Wolfson Arizona class devices.
|
|
|
|
|
|
2010-03-05 21:44:33 +00:00
|
|
|
config GPIO_MAX7300
|
|
|
|
|
tristate "Maxim MAX7300 GPIO expander"
|
|
|
|
|
depends on I2C
|
|
|
|
|
select GPIO_MAX730X
|
|
|
|
|
help
|
|
|
|
|
GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
|
|
|
|
|
|
2008-07-25 08:46:14 +00:00
|
|
|
config GPIO_MAX732X
|
|
|
|
|
tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
|
|
|
|
|
depends on I2C
|
|
|
|
|
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:
|
|
|
|
|
|
|
|
|
|
8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
|
|
|
|
|
max7322 (4I4O), max7323 (4P4O)
|
|
|
|
|
|
|
|
|
|
16 bits: max7324 (8I8O), max7325 (8P8O),
|
|
|
|
|
max7326 (4I12O), max7327 (4P12O)
|
|
|
|
|
|
|
|
|
|
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"
|
|
|
|
|
depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
|
|
|
|
|
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
|
2012-04-06 09:11:46 +00:00
|
|
|
tristate "PCA953x, PCA955x, PCA957x, TCA64xx, and MAX7310 I/O ports"
|
2008-02-05 06:28:26 +00:00
|
|
|
depends on I2C
|
|
|
|
|
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:
|
|
|
|
|
|
|
|
|
|
4 bits: pca9536, pca9537
|
|
|
|
|
|
2012-04-06 09:11:46 +00:00
|
|
|
8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
|
|
|
|
|
pca9556, pca9557, pca9574, tca6408
|
2008-07-04 16:59:37 +00:00
|
|
|
|
2012-04-06 09:11:46 +00:00
|
|
|
16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
|
|
|
|
|
tca6416
|
2008-02-05 06:28:26 +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
|
|
|
|
|
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"
|
2008-02-05 06:28:24 +00:00
|
|
|
depends on I2C
|
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,
|
|
|
|
|
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.
|
|
|
|
|
|
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-08-11 01:02:27 +00:00
|
|
|
config GPIO_SX150X
|
|
|
|
|
bool "Semtech SX150x I2C GPIO expander"
|
|
|
|
|
depends on I2C=y
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Say yes here to provide support for Semtech SX150-series I2C
|
|
|
|
|
GPIO expanders. Compatible models include:
|
|
|
|
|
|
|
|
|
|
8 bits: sx1508q
|
|
|
|
|
16 bits: sx1509q
|
|
|
|
|
|
2010-07-02 11:22:09 +00:00
|
|
|
config GPIO_STMPE
|
|
|
|
|
bool "STMPE GPIOs"
|
|
|
|
|
depends on MFD_STMPE
|
|
|
|
|
help
|
|
|
|
|
This enables support for the GPIOs found on the STMPE I/O
|
|
|
|
|
Expanders.
|
|
|
|
|
|
2012-05-11 16:48:39 +00:00
|
|
|
config GPIO_STP_XWAY
|
|
|
|
|
bool "XWAY STP GPIOs"
|
|
|
|
|
depends on SOC_XWAY
|
|
|
|
|
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.
|
|
|
|
|
|
2010-12-13 04:03:13 +00:00
|
|
|
config GPIO_TC3589X
|
|
|
|
|
bool "TC3589X GPIOs"
|
|
|
|
|
depends on MFD_TC3589X
|
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.
|
|
|
|
|
|
2011-06-09 19:50:19 +00:00
|
|
|
config GPIO_TPS65912
|
|
|
|
|
tristate "TI TPS65912 GPIO"
|
|
|
|
|
depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
|
|
|
|
|
help
|
|
|
|
|
This driver supports TPS65912 gpio chip
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
2009-09-22 23:46:39 +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.
|
|
|
|
|
|
2010-01-08 22:43:08 +00:00
|
|
|
config GPIO_ADP5588
|
|
|
|
|
tristate "ADP5588 I2C GPIO expander"
|
|
|
|
|
depends on I2C
|
|
|
|
|
help
|
|
|
|
|
This option enables support for 18 GPIOs found
|
|
|
|
|
on Analog Devices ADP5588 GPIO Expanders.
|
|
|
|
|
|
2010-10-27 22:33:19 +00:00
|
|
|
config GPIO_ADP5588_IRQ
|
|
|
|
|
bool "Interrupt controller support for ADP5588"
|
|
|
|
|
depends on GPIO_ADP5588=y
|
|
|
|
|
help
|
|
|
|
|
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-09-18 08:57:10 +00:00
|
|
|
config GPIO_ADNP
|
|
|
|
|
tristate "Avionic Design N-bit GPIO expander"
|
2012-11-01 10:22:11 +00:00
|
|
|
depends on I2C && OF_GPIO
|
2012-09-18 08:57:10 +00:00
|
|
|
help
|
|
|
|
|
This option enables support for N GPIOs found on Avionic Design
|
|
|
|
|
I2C GPIO expanders. The register space will be extended by powers
|
2012-11-30 07:44:39 +00:00
|
|
|
of two, so the controller will need to accommodate for that. For
|
2012-09-18 08:57:10 +00:00
|
|
|
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).
|
|
|
|
|
|
2008-07-25 08:46:10 +00:00
|
|
|
comment "PCI GPIO expanders:"
|
|
|
|
|
|
2009-12-15 02:00:32 +00:00
|
|
|
config GPIO_CS5535
|
|
|
|
|
tristate "AMD CS5535/CS5536 GPIO support"
|
2011-11-23 10:44:24 +00:00
|
|
|
depends on PCI && X86 && MFD_CS5535
|
2009-12-15 02:00:32 +00:00
|
|
|
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.
|
|
|
|
|
|
2008-07-25 08:46:10 +00:00
|
|
|
config GPIO_BT8XX
|
|
|
|
|
tristate "BT8XX GPIO abuser"
|
|
|
|
|
depends on PCI && VIDEO_BT848=n
|
|
|
|
|
help
|
|
|
|
|
The BT8xx frame grabber chip has 24 GPIO pins than can be abused
|
|
|
|
|
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
|
|
|
|
|
Documentation/bt8xxgpio.txt
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2012-06-01 13:36:31 +00:00
|
|
|
config GPIO_AMD8111
|
|
|
|
|
tristate "AMD 8111 GPIO driver"
|
|
|
|
|
depends on PCI
|
|
|
|
|
help
|
|
|
|
|
The AMD 8111 south bridge contains 32 GPIO pins which can be used.
|
|
|
|
|
|
|
|
|
|
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!
|
|
|
|
|
|
|
|
|
|
If unsure, say N
|
|
|
|
|
|
2009-09-22 23:46:36 +00:00
|
|
|
config GPIO_LANGWELL
|
2010-05-26 21:42:25 +00:00
|
|
|
bool "Intel Langwell/Penwell GPIO support"
|
2011-03-17 19:32:46 +00:00
|
|
|
depends on PCI && X86
|
2012-05-02 08:15:50 +00:00
|
|
|
select IRQ_DOMAIN
|
2009-09-22 23:46:36 +00:00
|
|
|
help
|
2010-05-26 21:42:25 +00:00
|
|
|
Say Y here to support Intel Langwell/Penwell GPIO.
|
2009-09-22 23:46:36 +00:00
|
|
|
|
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"
|
2011-03-17 19:32:46 +00:00
|
|
|
depends on PCI && X86
|
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
|
|
|
|
2011-01-13 01:00:22 +00:00
|
|
|
config GPIO_ML_IOH
|
|
|
|
|
tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
|
|
|
|
|
depends on PCI
|
2011-08-05 04:04:21 +00:00
|
|
|
select GENERIC_IRQ_CHIP
|
2011-01-13 01:00:22 +00:00
|
|
|
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.
|
|
|
|
|
|
2011-06-27 07:26:23 +00:00
|
|
|
config GPIO_SODAVILLE
|
|
|
|
|
bool "Intel Sodaville GPIO support"
|
2012-03-28 20:55:04 +00:00
|
|
|
depends on X86 && PCI && 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.
|
|
|
|
|
|
2009-12-16 00:46:18 +00:00
|
|
|
config GPIO_TIMBERDALE
|
|
|
|
|
bool "Support for timberdale GPIO IP"
|
2011-05-20 06:40:17 +00:00
|
|
|
depends on MFD_TIMBERDALE && HAS_IOMEM
|
2009-12-16 00:46:18 +00:00
|
|
|
---help---
|
|
|
|
|
Add support for the GPIO IP in the timberdale FPGA.
|
|
|
|
|
|
2010-03-21 00:06:09 +00:00
|
|
|
config GPIO_RDC321X
|
|
|
|
|
tristate "RDC R-321x GPIO support"
|
2011-05-20 06:40:17 +00:00
|
|
|
depends on PCI
|
2010-05-11 20:24:20 +00:00
|
|
|
select MFD_CORE
|
2010-03-21 00:06:09 +00:00
|
|
|
select MFD_RDC321X
|
|
|
|
|
help
|
|
|
|
|
Support for the RDC R321x SoC GPIOs over southbridge
|
|
|
|
|
PCI configuration space.
|
|
|
|
|
|
2008-02-05 06:28:17 +00:00
|
|
|
comment "SPI GPIO expanders:"
|
|
|
|
|
|
2008-07-21 21:21:34 +00:00
|
|
|
config GPIO_MAX7301
|
|
|
|
|
tristate "Maxim MAX7301 GPIO expander"
|
|
|
|
|
depends on SPI_MASTER
|
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
|
|
|
|
2008-02-05 06:28:25 +00:00
|
|
|
config GPIO_MCP23S08
|
mcp23s08: add i2c support
Add i2c bindings for the mcp230xx devices. This is quite a lot simpler
than the spi one as there's no funky sub addressing done (one struct
i2c_client per struct gpio_chip).
The mcp23s08_platform_data structure is reused for i2c, even though
only a single mcp23s08_chip_info structure is needed.
To use, simply fill out a platform_data structure and pass it in
i2c_board_info, E.G.:
static const struct mcp23s08_platform_data mcp23017_data = {
.chip[0] = {
.pullups = 0x00ff,
},
.base = 240,
};
static struct i2c_board_info __initdata i2c_devs[] = {
{ I2C_BOARD_INFO("mcp23017", 0x20),
.platform_data = &smartview_mcp23017_data, },
...
};
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
2011-07-15 08:25:32 +00:00
|
|
|
tristate "Microchip MCP23xxx I/O expander"
|
|
|
|
|
depends on SPI_MASTER || I2C
|
2008-02-05 06:28:25 +00:00
|
|
|
help
|
mcp23s08: add i2c support
Add i2c bindings for the mcp230xx devices. This is quite a lot simpler
than the spi one as there's no funky sub addressing done (one struct
i2c_client per struct gpio_chip).
The mcp23s08_platform_data structure is reused for i2c, even though
only a single mcp23s08_chip_info structure is needed.
To use, simply fill out a platform_data structure and pass it in
i2c_board_info, E.G.:
static const struct mcp23s08_platform_data mcp23017_data = {
.chip[0] = {
.pullups = 0x00ff,
},
.base = 240,
};
static struct i2c_board_info __initdata i2c_devs[] = {
{ I2C_BOARD_INFO("mcp23017", 0x20),
.platform_data = &smartview_mcp23017_data, },
...
};
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
2011-07-15 08:25:32 +00:00
|
|
|
SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
|
|
|
|
|
I/O expanders.
|
2011-03-09 16:56:30 +00:00
|
|
|
This provides a GPIO interface supporting inputs and outputs.
|
2008-02-05 06:28:25 +00:00
|
|
|
|
2009-09-22 23:46:34 +00:00
|
|
|
config GPIO_MC33880
|
|
|
|
|
tristate "Freescale MC33880 high-side/low-side switch"
|
|
|
|
|
depends on SPI_MASTER
|
|
|
|
|
help
|
|
|
|
|
SPI driver for Freescale MC33880 high-side/low-side switch.
|
|
|
|
|
This provides GPIO interface supporting inputs and outputs.
|
|
|
|
|
|
2010-10-27 22:33:18 +00:00
|
|
|
config GPIO_74X164
|
|
|
|
|
tristate "74x164 serial-in/parallel-out 8-bits shift register"
|
|
|
|
|
depends on SPI_MASTER
|
|
|
|
|
help
|
|
|
|
|
Platform driver for 74x164 compatible serial-in/parallel-out
|
|
|
|
|
8-outputs shift registers. This driver can be used to provide access
|
|
|
|
|
to more gpio outputs.
|
|
|
|
|
|
2009-09-22 23:46:35 +00:00
|
|
|
comment "AC97 GPIO expanders:"
|
|
|
|
|
|
|
|
|
|
config GPIO_UCB1400
|
|
|
|
|
bool "Philips UCB1400 GPIO"
|
|
|
|
|
depends on UCB1400_CORE
|
|
|
|
|
help
|
|
|
|
|
This enables support for the Philips UCB1400 GPIO pins.
|
|
|
|
|
The UCB1400 is an AC97 audio codec.
|
|
|
|
|
|
2010-04-07 08:08:01 +00:00
|
|
|
comment "MODULbus GPIO expanders:"
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
2012-07-18 06:20:48 +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.
|
|
|
|
|
|
2011-05-16 23:35:37 +00:00
|
|
|
config GPIO_TPS65910
|
|
|
|
|
bool "TPS65910 GPIO"
|
|
|
|
|
depends on MFD_TPS65910
|
|
|
|
|
help
|
|
|
|
|
Select this option to enable GPIO driver for the TPS65910
|
|
|
|
|
chip family.
|
2012-04-24 10:02:49 +00:00
|
|
|
|
|
|
|
|
config GPIO_MSIC
|
|
|
|
|
bool "Intel MSIC mixed signal gpio support"
|
|
|
|
|
depends on MFD_INTEL_MSIC
|
|
|
|
|
help
|
|
|
|
|
Enable support for GPIO on intel MSIC controllers found in
|
|
|
|
|
intel MID devices
|
|
|
|
|
|
2012-11-05 14:48:24 +00:00
|
|
|
comment "USB GPIO expanders:"
|
|
|
|
|
|
|
|
|
|
config GPIO_VIPERBOARD
|
|
|
|
|
tristate "Viperboard GPIO a & b support"
|
|
|
|
|
depends on MFD_VIPERBOARD && USB
|
|
|
|
|
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.
|
|
|
|
|
See viperboard API specification and Nano
|
|
|
|
|
River Tech's viperboard.h for detailed meaning
|
|
|
|
|
of the module parameters.
|
|
|
|
|
|
2008-07-25 08:46:11 +00:00
|
|
|
endif
|
