[GitHub/mt8127/android_kernel_alcatel_ttab.git] / drivers / gpio / Kconfig

#
# 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.
	  The checks help ensure that GPIOs have been properly initialized
	  before they are used and that sleeping calls aren not made from
	  nonsleeping 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

comment "I2C GPIO expanders:"

config GPIO_PCA953X
	tristate "PCA953x, PCA955x, 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

	  16 bits:	pca9535, pca9539, pca9555

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

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.

comment "PCI GPIO expanders:"

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.

comment "SPI GPIO expanders:"

config GPIO_MAX7301
	tristate "Maxim MAX7301 GPIO expander"
	depends on SPI_MASTER
	help
	  gpio driver for Maxim MAX7301 SPI 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.

endif
Commit	Line	Data
a9c5fff5 DB	1	#
	2	# GPIO infrastructure and expanders
	3	#
	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.
	45	The checks help ensure that GPIOs have been properly initialized
	46	before they are used and that sleeping calls aren not made from
	47	nonsleeping contexts. They can make bitbanged serial protocols
	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
	67
	68	comment "I2C GPIO expanders:"
	69
f3dc3630	70	config GPIO_PCA953X
7059d4b0	71	tristate "PCA953x, PCA955x, and MAX7310 I/O ports"
9e60fdcf	72	depends on I2C
9e60fdcf	73	help
7059d4b0 DB	74	Say yes here to provide access to several register-oriented
	75	SMBus I/O expanders, made mostly by NXP or TI. Compatible
	76	models include:
	77
	78	4 bits: pca9536, pca9537
	79
	80	8 bits: max7310, pca9534, pca9538, pca9554, pca9557
	81
	82	16 bits: pca9535, pca9539, pca9555
9e60fdcf	83
9e60fdcf	84	This driver can also be built as a module. If so, the module
f3dc3630	85	will be called pca953x.
9e60fdcf	86
15fae37d	87	config GPIO_PCF857X
1673ad52	88	tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
15fae37d DB	89	depends on I2C
	90	help
	91	Say yes here to provide access to most "quasi-bidirectional" I2C
	92	GPIO expanders used for additional digital outputs or inputs.
	93	Most of these parts are from NXP, though TI is a second source for
	94	some of them. Compatible models include:
	95
	96	8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
1673ad52 DB	97	pca9670, pca9672, pca9674, pca9674a,
1673ad52 DB	98	max7328, max7329
15fae37d DB	99
	100	16 bits: pcf8575, pcf8575c, pca8575,
	101	pca9671, pca9673, pca9675
	102
	103	Your board setup code will need to declare the expanders in
	104	use, and assign numbers to the GPIOs they expose. Those GPIOs
	105	can then be used from drivers and other kernel code, just like
	106	other GPIOs, but only accessible from task contexts.
	107
	108	This driver provides an in-kernel interface to those GPIOs using
	109	platform-neutral GPIO calls.
	110
ff1d5c2f MB	111	comment "PCI GPIO expanders:"
	112
	113	config GPIO_BT8XX
	114	tristate "BT8XX GPIO abuser"
	115	depends on PCI && VIDEO_BT848=n
	116	help
	117	The BT8xx frame grabber chip has 24 GPIO pins than can be abused
	118	as a cheap PCI GPIO card.
	119
	120	This chip can be found on Miro, Hauppauge and STB TV-cards.
	121
	122	The card needs to be physically altered for using it as a
	123	GPIO card. For more information on how to build a GPIO card
	124	from a BT8xx TV card, see the documentation file at
	125	Documentation/bt8xxgpio.txt
	126
	127	If unsure, say N.
	128
a9c5fff5 DB	129	comment "SPI GPIO expanders:"
a9c5fff5 DB	130
0c36ec31 JB	131	config GPIO_MAX7301
	132	tristate "Maxim MAX7301 GPIO expander"
	133	depends on SPI_MASTER
	134	help
	135	gpio driver for Maxim MAX7301 SPI GPIO expander.
	136
e58b9e27 DB	137	config GPIO_MCP23S08
	138	tristate "Microchip MCP23S08 I/O expander"
	139	depends on SPI_MASTER
	140	help
	141	SPI driver for Microchip MCP23S08 I/O expander. This provides
	142	a GPIO interface supporting inputs and outputs.
	143
7444a72e	144	endif