[net-next-2.6.git] / drivers / gpio / Kconfig

#
# platform-neutral GPIO infrastructure and expanders
#

config ARCH_WANT_OPTIONAL_GPIOLIB
	bool
	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
	help
	  Platforms select gpiolib if they use this infrastructure
	  for all their GPIOs, usually starting with ones integrated
	  into SOC processors.
	  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
	  one or more of the GPIO expansion card drivers below.

	  If unsure, say N.

if GPIOLIB

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.
	  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
	  slower.  The diagnostics help catch the type of setup errors
	  that are most common when setting up new platforms or boards.

config GPIO_SYSFS
	bool "/sys/class/gpio/... (sysfs interface)"
	depends on SYSFS && EXPERIMENTAL
	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.

# put expanders in the right section, in alphabetical order

config GPIO_MAX730X
	tristate

comment "Memory mapped GPIO expanders:"

config GPIO_BASIC_MMIO
	tristate "Basic memory-mapped GPIO controllers support"
	help
	  Say yes here to support basic memory-mapped GPIO controllers.

config GPIO_IT8761E
	tristate "IT8761E GPIO support"
	depends on GPIOLIB
	help
	  Say yes here to support GPIO functionality of IT8761E super I/O chip.

config GPIO_PL061
	bool "PrimeCell PL061 GPIO support"
	depends on ARM_AMBA
	help
	  Say yes here to support the PrimeCell PL061 GPIO device

config GPIO_XILINX
	bool "Xilinx GPIO support"
	depends on PPC_OF || MICROBLAZE
	help
	  Say yes here to support the Xilinx FPGA GPIO device

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_SCH
	tristate "Intel SCH GPIO"
	depends on GPIOLIB && PCI
	select MFD_CORE
	select LPC_SCH
	help
	  Say yes here to support GPIO interface on Intel Poulsbo SCH.
	  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.

	  This driver can also be built as a module. If so, the module
	  will be called sch-gpio.

config GPIO_VX855
	tristate "VIA VX855/VX875 GPIO"
	depends on GPIOLIB
	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.

comment "I2C GPIO expanders:"

config GPIO_MAX7300
	tristate "Maxim MAX7300 GPIO expander"
	depends on I2C
	select GPIO_MAX730X
	help
	  GPIO driver for Maxim MAX7301 I2C-based GPIO expander.

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.

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.

config GPIO_PCA953X
	tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
	depends on I2C
	help
	  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

	  8 bits:	max7310, pca9534, pca9538, pca9554, pca9557,
	  		tca6408

	  16 bits:	pca9535, pca9539, pca9555, tca6416

	  This driver can also be built as a module.  If so, the module
	  will be called pca953x.

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.

config GPIO_PCF857X
	tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
	depends on I2C
	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,
	            pca9670, pca9672, pca9674, pca9674a,
	  	    max7328, max7329

	  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.

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

config GPIO_STMPE
	bool "STMPE GPIOs"
	depends on MFD_STMPE
	help
	  This enables support for the GPIOs found on the STMPE I/O
	  Expanders.

config GPIO_TC35892
	bool "TC35892 GPIOs"
	depends on MFD_TC35892
	help
	  This enables support for the GPIOs found on the TC35892
	  I/O Expander.

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.

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.

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.

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.

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.

	  To compile this driver as a module, choose M here: the module will
	  be called adp5520-gpio.

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.
	  To compile this driver as a module, choose M here: the module will be
	  called adp5588-gpio.

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.

comment "PCI GPIO expanders:"

config GPIO_CS5535
	tristate "AMD CS5535/CS5536 GPIO support"
	depends on PCI && !CS5535_GPIO
	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_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.

config GPIO_LANGWELL
	bool "Intel Langwell/Penwell GPIO support"
	depends on PCI
	help
	  Say Y here to support Intel Langwell/Penwell GPIO.

config GPIO_PCH
	tristate "PCH GPIO of Intel Topcliff"
	depends on PCI
	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.

config GPIO_TIMBERDALE
	bool "Support for timberdale GPIO IP"
	depends on MFD_TIMBERDALE && GPIOLIB && HAS_IOMEM
	---help---
	Add support for the GPIO IP in the timberdale FPGA.

config GPIO_RDC321X
	tristate "RDC R-321x GPIO support"
	depends on PCI && GPIOLIB
	select MFD_CORE
	select MFD_RDC321X
	help
	  Support for the RDC R321x SoC GPIOs over southbridge
	  PCI configuration space.

comment "SPI GPIO expanders:"

config GPIO_MAX7301
	tristate "Maxim MAX7301 GPIO expander"
	depends on SPI_MASTER
	select GPIO_MAX730X
	help
	  GPIO driver for Maxim MAX7301 SPI-based GPIO expander.

config GPIO_MCP23S08
	tristate "Microchip MCP23S08 I/O expander"
	depends on SPI_MASTER
	help
	  SPI driver for Microchip MCP23S08 I/O expander.  This provides
	  a GPIO interface supporting inputs and outputs.

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.

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.

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.

	  To compile this driver as a module, choose M here: the
	  module will be called ucb1400_gpio.

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.

endif
Commit	Line	Data
a9c5fff5	1	#
926b1e2c	2	# platform-neutral GPIO infrastructure and expanders
a9c5fff5 DB	3	#
a9c5fff5 DB	4
7444a72e	5	config ARCH_WANT_OPTIONAL_GPIOLIB
a9c5fff5	6	bool
7444a72e MB	7	help
	8	Select this config option from the architecture Kconfig, if
	9	it is possible to use gpiolib on the architecture, but let the
	10	user decide whether to actually build it or not.
	11	Select this instead of ARCH_REQUIRE_GPIOLIB, if your architecture does
	12	not depend on GPIOs being available, but rather let the user
	13	decide whether he needs it or not.
	14
	15	config ARCH_REQUIRE_GPIOLIB
	16	bool
	17	select GPIOLIB
a9c5fff5 DB	18	help
	19	Platforms select gpiolib if they use this infrastructure
	20	for all their GPIOs, usually starting with ones integrated
	21	into SOC processors.
7444a72e MB	22	Selecting this from the architecture code will cause the gpiolib
	23	code to always get built in.
	24
	25
	26
	27	menuconfig GPIOLIB
	28	bool "GPIO Support"
	29	depends on ARCH_WANT_OPTIONAL_GPIOLIB \|\| ARCH_REQUIRE_GPIOLIB
	30	select GENERIC_GPIO
	31	help
	32	This enables GPIO support through the generic GPIO library.
	33	You only need to enable this, if you also want to enable
	34	one or more of the GPIO expansion card drivers below.
	35
	36	If unsure, say N.
a9c5fff5	37
7444a72e	38	if GPIOLIB
a9c5fff5 DB	39
	40	config DEBUG_GPIO
	41	bool "Debug GPIO calls"
	42	depends on DEBUG_KERNEL
	43	help
	44	Say Y here to add some extra checks and diagnostics to GPIO calls.
692105b8 ML	45	These checks help ensure that GPIOs have been properly initialized
	46	before they are used, and that sleeping calls are not made from
	47	non-sleeping contexts. They can make bitbanged serial protocols
a9c5fff5 DB	48	slower. The diagnostics help catch the type of setup errors
	49	that are most common when setting up new platforms or boards.
	50
d8f388d8 DB	51	config GPIO_SYSFS
	52	bool "/sys/class/gpio/... (sysfs interface)"
	53	depends on SYSFS && EXPERIMENTAL
	54	help
	55	Say Y here to add a sysfs interface for GPIOs.
	56
	57	This is mostly useful to work around omissions in a system's
	58	kernel support. Those are common in custom and semicustom
	59	hardware assembled using standard kernels with a minimum of
	60	custom patches. In those cases, userspace code may import
	61	a given GPIO from the kernel, if no kernel driver requested it.
	62
	63	Kernel drivers may also request that a particular GPIO be
	64	exported to userspace; this can be useful when debugging.
	65
a9c5fff5 DB	66	# put expanders in the right section, in alphabetical order
a9c5fff5 DB	67
e952805d WS	68	config GPIO_MAX730X
	69	tristate
	70
0bcb6069 JL	71	comment "Memory mapped GPIO expanders:"
0bcb6069 JL	72
aeec56e3 AV	73	config GPIO_BASIC_MMIO
	74	tristate "Basic memory-mapped GPIO controllers support"
	75	help
	76	Say yes here to support basic memory-mapped GPIO controllers.
	77
9cc0cb3c DT	78	config GPIO_IT8761E
	79	tristate "IT8761E GPIO support"
	80	depends on GPIOLIB
	81	help
	82	Say yes here to support GPIO functionality of IT8761E super I/O chip.
	83
1e9c2859 BS	84	config GPIO_PL061
	85	bool "PrimeCell PL061 GPIO support"
	86	depends on ARM_AMBA
	87	help
	88	Say yes here to support the PrimeCell PL061 GPIO device
	89
0bcb6069 JL	90	config GPIO_XILINX
0bcb6069 JL	91	bool "Xilinx GPIO support"
6fa612b5	92	depends on PPC_OF \|\| MICROBLAZE
0bcb6069 JL	93	help
	94	Say yes here to support the Xilinx FPGA GPIO device
	95
27fdd325 YY	96	config GPIO_VR41XX
	97	tristate "NEC VR4100 series General-purpose I/O Uint support"
	98	depends on CPU_VR41XX
	99	help
	100	Say yes here to support the NEC VR4100 series General-purpose I/O Uint
	101
be9b06b2 DT	102	config GPIO_SCH
be9b06b2 DT	103	tristate "Intel SCH GPIO"
860fb8c1 RD	104	depends on GPIOLIB && PCI
860fb8c1 RD	105	select MFD_CORE
be9b06b2 DT	106	select LPC_SCH
	107	help
	108	Say yes here to support GPIO interface on Intel Poulsbo SCH.
	109	The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
	110	powered by the core power rail and are turned off during sleep
	111	modes (S3 and higher). The remaining four GPIOs are powered by
	112	the Intel SCH suspend power supply. These GPIOs remain
	113	active during S3. The suspend powered GPIOs can be used to wake the
	114	system from the Suspend-to-RAM state.
	115
	116	This driver can also be built as a module. If so, the module
	117	will be called sch-gpio.
	118
99ea2626 DD	119	config GPIO_VX855
	120	tristate "VIA VX855/VX875 GPIO"
	121	depends on GPIOLIB
	122	select MFD_CORE
	123	select MFD_VX855
	124	help
	125	Support access to the VX855/VX875 GPIO lines through the gpio library.
	126
	127	This driver provides common support for accessing the device,
	128	additional drivers must be enabled in order to use the
	129	functionality of the device.
	130
a9c5fff5 DB	131	comment "I2C GPIO expanders:"
a9c5fff5 DB	132
e952805d WS	133	config GPIO_MAX7300
	134	tristate "Maxim MAX7300 GPIO expander"
	135	depends on I2C
	136	select GPIO_MAX730X
	137	help
	138	GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
	139
bbcd6d54 EM	140	config GPIO_MAX732X
	141	tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
	142	depends on I2C
	143	help
	144	Say yes here to support the MAX7319, MAX7320-7327 series of I2C
	145	Port Expanders. Each IO port on these chips has a fixed role of
	146	Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
	147	Input and Output (designed by 'P'). The combinations are listed
	148	below:
	149
	150	8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
	151	max7322 (4I4O), max7323 (4P4O)
	152
	153	16 bits: max7324 (8I8O), max7325 (8P8O),
	154	max7326 (4I12O), max7327 (4P12O)
	155
	156	Board setup code must specify the model to use, and the start
	157	number for these GPIOs.
	158
a80a0bbe MZ	159	config GPIO_MAX732X_IRQ
	160	bool "Interrupt controller support for MAX732x"
	161	depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
	162	help
	163	Say yes here to enable the max732x to be used as an interrupt
	164	controller. It requires the driver to be built in the kernel.
	165
f3dc3630	166	config GPIO_PCA953X
ab5dc372	167	tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
9e60fdcf	168	depends on I2C
9e60fdcf	169	help
7059d4b0 DB	170	Say yes here to provide access to several register-oriented
	171	SMBus I/O expanders, made mostly by NXP or TI. Compatible
	172	models include:
	173
	174	4 bits: pca9536, pca9537
	175
ab5dc372 DB	176	8 bits: max7310, pca9534, pca9538, pca9554, pca9557,
ab5dc372 DB	177	tca6408
7059d4b0	178
ab5dc372	179	16 bits: pca9535, pca9539, pca9555, tca6416
9e60fdcf	180
9e60fdcf	181	This driver can also be built as a module. If so, the module
f3dc3630	182	will be called pca953x.
9e60fdcf	183
89ea8bbe MZ	184	config GPIO_PCA953X_IRQ
	185	bool "Interrupt controller support for PCA953x"
	186	depends on GPIO_PCA953X=y
	187	help
	188	Say yes here to enable the pca953x to be used as an interrupt
	189	controller. It requires the driver to be built in the kernel.
	190
15fae37d	191	config GPIO_PCF857X
1673ad52	192	tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
15fae37d DB	193	depends on I2C
	194	help
	195	Say yes here to provide access to most "quasi-bidirectional" I2C
	196	GPIO expanders used for additional digital outputs or inputs.
	197	Most of these parts are from NXP, though TI is a second source for
	198	some of them. Compatible models include:
	199
	200	8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
1673ad52 DB	201	pca9670, pca9672, pca9674, pca9674a,
1673ad52 DB	202	max7328, max7329
15fae37d DB	203
	204	16 bits: pcf8575, pcf8575c, pca8575,
	205	pca9671, pca9673, pca9675
	206
	207	Your board setup code will need to declare the expanders in
	208	use, and assign numbers to the GPIOs they expose. Those GPIOs
	209	can then be used from drivers and other kernel code, just like
	210	other GPIOs, but only accessible from task contexts.
	211
	212	This driver provides an in-kernel interface to those GPIOs using
	213	platform-neutral GPIO calls.
	214
c34f16b7 GB	215	config GPIO_SX150X
	216	bool "Semtech SX150x I2C GPIO expander"
	217	depends on I2C=y
	218	default n
	219	help
	220	Say yes here to provide support for Semtech SX150-series I2C
	221	GPIO expanders. Compatible models include:
	222
	223	8 bits: sx1508q
	224	16 bits: sx1509q
	225
03f822f5 RV	226	config GPIO_STMPE
	227	bool "STMPE GPIOs"
	228	depends on MFD_STMPE
	229	help
	230	This enables support for the GPIOs found on the STMPE I/O
	231	Expanders.
	232
d88b25be RV	233	config GPIO_TC35892
	234	bool "TC35892 GPIOs"
	235	depends on MFD_TC35892
	236	help
	237	This enables support for the GPIOs found on the TC35892
	238	I/O Expander.
	239
e9d35947 DB	240	config GPIO_TWL4030
	241	tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
	242	depends on TWL4030_CORE
	243	help
	244	Say yes here to access the GPIO signals of various multi-function
	245	power management chips from Texas Instruments.
	246
e4b736f1 MB	247	config GPIO_WM831X
	248	tristate "WM831x GPIOs"
	249	depends on MFD_WM831X
	250	help
	251	Say yes here to access the GPIO signals of WM831x power management
	252	chips from Wolfson Microelectronics.
	253
38f6ce45 MB	254	config GPIO_WM8350
	255	tristate "WM8350 GPIOs"
	256	depends on MFD_WM8350
	257	help
	258	Say yes here to access the GPIO signals of WM8350 power management
	259	chips from Wolfson Microelectronics.
	260
2955c309 MB	261	config GPIO_WM8994
	262	tristate "WM8994 GPIOs"
	263	depends on MFD_WM8994
	264	help
	265	Say yes here to access the GPIO signals of WM8994 audio hub
	266	CODECs from Wolfson Microelectronics.
	267
ef72af40 MH	268	config GPIO_ADP5520
	269	tristate "GPIO Support for ADP5520 PMIC"
	270	depends on PMIC_ADP5520
	271	help
	272	This option enables support for on-chip GPIO found
	273	on Analog Devices ADP5520 PMICs.
	274
	275	To compile this driver as a module, choose M here: the module will
	276	be called adp5520-gpio.
	277
80884094 MH	278	config GPIO_ADP5588
	279	tristate "ADP5588 I2C GPIO expander"
	280	depends on I2C
	281	help
	282	This option enables support for 18 GPIOs found
	283	on Analog Devices ADP5588 GPIO Expanders.
	284	To compile this driver as a module, choose M here: the module will be
	285	called adp5588-gpio.
	286
459773ae MH	287	config GPIO_ADP5588_IRQ
	288	bool "Interrupt controller support for ADP5588"
	289	depends on GPIO_ADP5588=y
	290	help
	291	Say yes here to enable the adp5588 to be used as an interrupt
	292	controller. It requires the driver to be built in the kernel.
	293
ff1d5c2f MB	294	comment "PCI GPIO expanders:"
ff1d5c2f MB	295
5f0a96b0 AS	296	config GPIO_CS5535
5f0a96b0 AS	297	tristate "AMD CS5535/CS5536 GPIO support"
c95d1e53	298	depends on PCI && !CS5535_GPIO
5f0a96b0 AS	299	help
	300	The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
	301	can be used for quite a number of things. The CS5535/6 is found on
	302	AMD Geode and Lemote Yeeloong devices.
	303
	304	If unsure, say N.
	305
ff1d5c2f MB	306	config GPIO_BT8XX
	307	tristate "BT8XX GPIO abuser"
	308	depends on PCI && VIDEO_BT848=n
	309	help
	310	The BT8xx frame grabber chip has 24 GPIO pins than can be abused
	311	as a cheap PCI GPIO card.
	312
	313	This chip can be found on Miro, Hauppauge and STB TV-cards.
	314
	315	The card needs to be physically altered for using it as a
	316	GPIO card. For more information on how to build a GPIO card
	317	from a BT8xx TV card, see the documentation file at
	318	Documentation/bt8xxgpio.txt
	319
	320	If unsure, say N.
	321
8bf02617	322	config GPIO_LANGWELL
8081c84c	323	bool "Intel Langwell/Penwell GPIO support"
8bf02617 AD	324	depends on PCI
8bf02617 AD	325	help
8081c84c	326	Say Y here to support Intel Langwell/Penwell GPIO.
8bf02617	327
04c17aa8 TM	328	config GPIO_PCH
	329	tristate "PCH GPIO of Intel Topcliff"
	330	depends on PCI
	331	help
	332	This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
	333	which is an IOH(Input/Output Hub) for x86 embedded processor.
	334	This driver can access PCH GPIO device.
	335
35570ac6 RR	336	config GPIO_TIMBERDALE
	337	bool "Support for timberdale GPIO IP"
	338	depends on MFD_TIMBERDALE && GPIOLIB && HAS_IOMEM
	339	---help---
	340	Add support for the GPIO IP in the timberdale FPGA.
	341
9956d02d FF	342	config GPIO_RDC321X
	343	tristate "RDC R-321x GPIO support"
	344	depends on PCI && GPIOLIB
e4be3cb7	345	select MFD_CORE
9956d02d FF	346	select MFD_RDC321X
	347	help
	348	Support for the RDC R321x SoC GPIOs over southbridge
	349	PCI configuration space.
	350
a9c5fff5 DB	351	comment "SPI GPIO expanders:"
a9c5fff5 DB	352
0c36ec31 JB	353	config GPIO_MAX7301
	354	tristate "Maxim MAX7301 GPIO expander"
	355	depends on SPI_MASTER
e952805d	356	select GPIO_MAX730X
0c36ec31	357	help
e952805d	358	GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
0c36ec31	359
e58b9e27 DB	360	config GPIO_MCP23S08
	361	tristate "Microchip MCP23S08 I/O expander"
	362	depends on SPI_MASTER
	363	help
	364	SPI driver for Microchip MCP23S08 I/O expander. This provides
	365	a GPIO interface supporting inputs and outputs.
	366
1e5db006 RR	367	config GPIO_MC33880
	368	tristate "Freescale MC33880 high-side/low-side switch"
	369	depends on SPI_MASTER
	370	help
	371	SPI driver for Freescale MC33880 high-side/low-side switch.
	372	This provides GPIO interface supporting inputs and outputs.
	373
ead6db08 MG	374	config GPIO_74X164
	375	tristate "74x164 serial-in/parallel-out 8-bits shift register"
	376	depends on SPI_MASTER
	377	help
	378	Platform driver for 74x164 compatible serial-in/parallel-out
	379	8-outputs shift registers. This driver can be used to provide access
	380	to more gpio outputs.
	381
4cf8e53b MV	382	comment "AC97 GPIO expanders:"
	383
	384	config GPIO_UCB1400
	385	bool "Philips UCB1400 GPIO"
	386	depends on UCB1400_CORE
	387	help
	388	This enables support for the Philips UCB1400 GPIO pins.
	389	The UCB1400 is an AC97 audio codec.
	390
	391	To compile this driver as a module, choose M here: the
	392	module will be called ucb1400_gpio.
	393
800e69fb IS	394	comment "MODULbus GPIO expanders:"
	395
	396	config GPIO_JANZ_TTL
	397	tristate "Janz VMOD-TTL Digital IO Module"
	398	depends on MFD_JANZ_CMODIO
	399	help
	400	This enables support for the Janz VMOD-TTL Digital IO module.
	401	This driver provides support for driving the pins in output
	402	mode only. Input mode is not supported.
	403
7444a72e	404	endif