[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 "Memory mapped GPIO expanders:"

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

comment "I2C GPIO expanders:"

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

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.

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
a9c5fff5 DB	67
0bcb6069 JL	68	comment "Memory mapped GPIO expanders:"
	69
	70	config GPIO_XILINX
	71	bool "Xilinx GPIO support"
	72	depends on PPC_OF
	73	help
	74	Say yes here to support the Xilinx FPGA GPIO device
	75
a9c5fff5 DB	76	comment "I2C GPIO expanders:"
a9c5fff5 DB	77
bbcd6d54 EM	78	config GPIO_MAX732X
	79	tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
	80	depends on I2C
	81	help
	82	Say yes here to support the MAX7319, MAX7320-7327 series of I2C
	83	Port Expanders. Each IO port on these chips has a fixed role of
	84	Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
	85	Input and Output (designed by 'P'). The combinations are listed
	86	below:
	87
	88	8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
	89	max7322 (4I4O), max7323 (4P4O)
	90
	91	16 bits: max7324 (8I8O), max7325 (8P8O),
	92	max7326 (4I12O), max7327 (4P12O)
	93
	94	Board setup code must specify the model to use, and the start
	95	number for these GPIOs.
	96
f3dc3630	97	config GPIO_PCA953X
7059d4b0	98	tristate "PCA953x, PCA955x, and MAX7310 I/O ports"
9e60fdcf	99	depends on I2C
9e60fdcf	100	help
7059d4b0 DB	101	Say yes here to provide access to several register-oriented
	102	SMBus I/O expanders, made mostly by NXP or TI. Compatible
	103	models include:
	104
	105	4 bits: pca9536, pca9537
	106
	107	8 bits: max7310, pca9534, pca9538, pca9554, pca9557
	108
	109	16 bits: pca9535, pca9539, pca9555
9e60fdcf	110
9e60fdcf	111	This driver can also be built as a module. If so, the module
f3dc3630	112	will be called pca953x.
9e60fdcf	113
15fae37d	114	config GPIO_PCF857X
1673ad52	115	tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
15fae37d DB	116	depends on I2C
	117	help
	118	Say yes here to provide access to most "quasi-bidirectional" I2C
	119	GPIO expanders used for additional digital outputs or inputs.
	120	Most of these parts are from NXP, though TI is a second source for
	121	some of them. Compatible models include:
	122
	123	8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
1673ad52 DB	124	pca9670, pca9672, pca9674, pca9674a,
1673ad52 DB	125	max7328, max7329
15fae37d DB	126
	127	16 bits: pcf8575, pcf8575c, pca8575,
	128	pca9671, pca9673, pca9675
	129
	130	Your board setup code will need to declare the expanders in
	131	use, and assign numbers to the GPIOs they expose. Those GPIOs
	132	can then be used from drivers and other kernel code, just like
	133	other GPIOs, but only accessible from task contexts.
	134
	135	This driver provides an in-kernel interface to those GPIOs using
	136	platform-neutral GPIO calls.
	137
e9d35947 DB	138	config GPIO_TWL4030
	139	tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
	140	depends on TWL4030_CORE
	141	help
	142	Say yes here to access the GPIO signals of various multi-function
	143	power management chips from Texas Instruments.
	144
ff1d5c2f MB	145	comment "PCI GPIO expanders:"
	146
	147	config GPIO_BT8XX
	148	tristate "BT8XX GPIO abuser"
	149	depends on PCI && VIDEO_BT848=n
	150	help
	151	The BT8xx frame grabber chip has 24 GPIO pins than can be abused
	152	as a cheap PCI GPIO card.
	153
	154	This chip can be found on Miro, Hauppauge and STB TV-cards.
	155
	156	The card needs to be physically altered for using it as a
	157	GPIO card. For more information on how to build a GPIO card
	158	from a BT8xx TV card, see the documentation file at
	159	Documentation/bt8xxgpio.txt
	160
	161	If unsure, say N.
	162
a9c5fff5 DB	163	comment "SPI GPIO expanders:"
a9c5fff5 DB	164
0c36ec31 JB	165	config GPIO_MAX7301
	166	tristate "Maxim MAX7301 GPIO expander"
	167	depends on SPI_MASTER
	168	help
	169	gpio driver for Maxim MAX7301 SPI GPIO expander.
	170
e58b9e27 DB	171	config GPIO_MCP23S08
	172	tristate "Microchip MCP23S08 I/O expander"
	173	depends on SPI_MASTER
	174	help
	175	SPI driver for Microchip MCP23S08 I/O expander. This provides
	176	a GPIO interface supporting inputs and outputs.
	177
7444a72e	178	endif