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

#
# GPIO infrastructure and expanders
#

config HAVE_GPIO_LIB
	bool
	help
	  Platforms select gpiolib if they use this infrastructure
	  for all their GPIOs, usually starting with ones integrated
	  into SOC processors.

menu "GPIO Support"
	depends on HAVE_GPIO_LIB

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 "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.

endmenu
Commit	Line	Data
a9c5fff5 DB	1	#
	2	# GPIO infrastructure and expanders
	3	#
	4
	5	config HAVE_GPIO_LIB
	6	bool
	7	help
	8	Platforms select gpiolib if they use this infrastructure
	9	for all their GPIOs, usually starting with ones integrated
	10	into SOC processors.
	11
	12	menu "GPIO Support"
	13	depends on HAVE_GPIO_LIB
	14
	15	config DEBUG_GPIO
	16	bool "Debug GPIO calls"
	17	depends on DEBUG_KERNEL
	18	help
	19	Say Y here to add some extra checks and diagnostics to GPIO calls.
	20	The checks help ensure that GPIOs have been properly initialized
	21	before they are used and that sleeping calls aren not made from
	22	nonsleeping contexts. They can make bitbanged serial protocols
	23	slower. The diagnostics help catch the type of setup errors
	24	that are most common when setting up new platforms or boards.
	25
d8f388d8 DB	26	config GPIO_SYSFS
	27	bool "/sys/class/gpio/... (sysfs interface)"
	28	depends on SYSFS && EXPERIMENTAL
	29	help
	30	Say Y here to add a sysfs interface for GPIOs.
	31
	32	This is mostly useful to work around omissions in a system's
	33	kernel support. Those are common in custom and semicustom
	34	hardware assembled using standard kernels with a minimum of
	35	custom patches. In those cases, userspace code may import
	36	a given GPIO from the kernel, if no kernel driver requested it.
	37
	38	Kernel drivers may also request that a particular GPIO be
	39	exported to userspace; this can be useful when debugging.
	40
a9c5fff5 DB	41	# put expanders in the right section, in alphabetical order
	42
	43	comment "I2C GPIO expanders:"
	44
f3dc3630	45	config GPIO_PCA953X
7059d4b0	46	tristate "PCA953x, PCA955x, and MAX7310 I/O ports"
9e60fdcf	47	depends on I2C
9e60fdcf	48	help
7059d4b0 DB	49	Say yes here to provide access to several register-oriented
	50	SMBus I/O expanders, made mostly by NXP or TI. Compatible
	51	models include:
	52
	53	4 bits: pca9536, pca9537
	54
	55	8 bits: max7310, pca9534, pca9538, pca9554, pca9557
	56
	57	16 bits: pca9535, pca9539, pca9555
9e60fdcf	58
9e60fdcf	59	This driver can also be built as a module. If so, the module
f3dc3630	60	will be called pca953x.
9e60fdcf	61
15fae37d	62	config GPIO_PCF857X
1673ad52	63	tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
15fae37d DB	64	depends on I2C
	65	help
	66	Say yes here to provide access to most "quasi-bidirectional" I2C
	67	GPIO expanders used for additional digital outputs or inputs.
	68	Most of these parts are from NXP, though TI is a second source for
	69	some of them. Compatible models include:
	70
	71	8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
1673ad52 DB	72	pca9670, pca9672, pca9674, pca9674a,
1673ad52 DB	73	max7328, max7329
15fae37d DB	74
	75	16 bits: pcf8575, pcf8575c, pca8575,
	76	pca9671, pca9673, pca9675
	77
	78	Your board setup code will need to declare the expanders in
	79	use, and assign numbers to the GPIOs they expose. Those GPIOs
	80	can then be used from drivers and other kernel code, just like
	81	other GPIOs, but only accessible from task contexts.
	82
	83	This driver provides an in-kernel interface to those GPIOs using
	84	platform-neutral GPIO calls.
	85
a9c5fff5 DB	86	comment "SPI GPIO expanders:"
a9c5fff5 DB	87
0c36ec31 JB	88	config GPIO_MAX7301
	89	tristate "Maxim MAX7301 GPIO expander"
	90	depends on SPI_MASTER
	91	help
	92	gpio driver for Maxim MAX7301 SPI GPIO expander.
	93
e58b9e27 DB	94	config GPIO_MCP23S08
	95	tristate "Microchip MCP23S08 I/O expander"
	96	depends on SPI_MASTER
	97	help
	98	SPI driver for Microchip MCP23S08 I/O expander. This provides
	99	a GPIO interface supporting inputs and outputs.
	100
a9c5fff5	101	endmenu