[linux-2.6-block.git] / drivers / staging / greybus / Kconfig

menuconfig GREYBUS
	tristate "Greybus support"
	depends on SYSFS
	---help---
	  This option enables the Greybus driver core.  Greybus is an
	  hardware protocol that was designed to provide Unipro with a
	  sane application layer.  It was originally designed for the
	  ARA project, a module phone system, but has shown up in other
	  phones, and can be tunneled over other busses in order to
	  control hardware devices.

	  Say Y here to enable support for these types of drivers.

	  To compile this code as a module, chose M here: the module
	  will be called greybus.ko

if GREYBUS

config GREYBUS_ES2
	tristate "Greybus ES3 USB host controller"
	depends on USB
	---help---
	  Select this option if you have a Toshiba ES3 USB device that
	  acts as a Greybus "host controller".  This device is a bridge
	  from a USB device to a Unipro network.

	  To compile this code as a module, chose M here: the module
	  will be called gb-es2.ko

config GREYBUS_AUDIO
	tristate "Greybus Audio Class driver"
	depends on SOUND
	---help---
	  Select this option if you have a device that follows the
	  Greybus Audio Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-audio.ko

config GREYBUS_BOOTROM
	tristate "Greybus Bootrom Class driver"
	---help---
	  Select this option if you have a device that follows the
	  Greybus Bootrom Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-bootrom.ko

config GREYBUS_CAMERA
	tristate "Greybus Camera Class driver"
	depends on MEDIA_SUPPORT && LEDS_CLASS_FLASH && BROKEN
	---help---
	  Select this option if you have a device that follows the
	  Greybus Camera Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-camera.ko

config GREYBUS_FIRMWARE
	tristate "Greybus Firmware Download Class driver"
	depends on SPI
	---help---
	  Select this option if you have a device that follows the
	  Greybus Firmware Download Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-firmware.ko

config GREYBUS_HID
	tristate "Greybus HID Class driver"
	depends on HID && INPUT
	---help---
	  Select this option if you have a device that follows the
	  Greybus HID Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-hid.ko

config GREYBUS_LIGHT
	tristate "Greybus LED Class driver"
	depends on LEDS_CLASS
	---help---
	  Select this option if you have a device that follows the
	  Greybus LED Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-light.ko

config GREYBUS_LOG
	tristate "Greybus Debug Log Class driver"
	---help---
	  Select this option if you have a device that follows the
	  Greybus Debug Log Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-log.ko

config GREYBUS_LOOPBACK
	tristate "Greybus Loopback Class driver"
	---help---
	  Select this option if you have a device that follows the
	  Greybus Debug Log Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-log.ko

config GREYBUS_POWER
	tristate "Greybus Powersupply Class driver"
	depends on POWER_SUPPLY
	---help---
	  Select this option if you have a device that follows the
	  Greybus Powersupply Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-power-supply.ko

config GREYBUS_RAW
	tristate "Greybus Raw Class driver"
	---help---
	  Select this option if you have a device that follows the
	  Greybus Raw Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-raw.ko

config GREYBUS_VIBRATOR
	tristate "Greybus Vibrator Motor Class driver"
	---help---
	  Select this option if you have a device that follows the
	  Greybus Vibrator Motor Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-vibrator.ko

menuconfig GREYBUS_BRIDGED_PHY
	tristate "Greybus Bridged PHY Class drivers"
	---help---
	  Select this option to pick from a variety of Greybus Bridged
	  PHY class drivers.  These drivers emulate a number of
	  different "traditional" busses by tunneling them over Greybus.
	  Examples of this include serial, SPI, USB, and others.

	  To compile this code as a module, chose M here: the module
	  will be called gb-phy.ko

if GREYBUS_BRIDGED_PHY

config GREYBUS_GPIO
	tristate "Greybus GPIO Bridged PHY driver"
	depends on GPIOLIB
	---help---
	  Select this option if you have a device that follows the
	  Greybus GPIO Bridged PHY Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-gpio.ko

config GREYBUS_I2C
	tristate "Greybus I2C Bridged PHY driver"
	depends on I2C
	---help---
	  Select this option if you have a device that follows the
	  Greybus I2C Bridged PHY Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-i2c.ko

config GREYBUS_PWM
	tristate "Greybus PWM Bridged PHY driver"
	depends on PWM
	---help---
	  Select this option if you have a device that follows the
	  Greybus PWM Bridged PHY Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-pwm.ko

config GREYBUS_SDIO
	tristate "Greybus SDIO Bridged PHY driver"
	depends on MMC
	---help---
	  Select this option if you have a device that follows the
	  Greybus SDIO Bridged PHY Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-sdio.ko

config GREYBUS_SPI
	tristate "Greybus SPI Bridged PHY driver"
	depends on SPI
	---help---
	  Select this option if you have a device that follows the
	  Greybus SPI Bridged PHY Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-spi.ko

config GREYBUS_UART
	tristate "Greybus UART Bridged PHY driver"
	depends on TTY
	---help---
	  Select this option if you have a device that follows the
	  Greybus UART Bridged PHY Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-uart.ko

config GREYBUS_USB
	tristate "Greybus USB Host Bridged PHY driver"
	depends on USB
	---help---
	  Select this option if you have a device that follows the
	  Greybus USB Host Bridged PHY Class specification.

	  To compile this code as a module, chose M here: the module
	  will be called gb-usb.ko

endif	# GREYBUS_BRIDGED_PHY

config GREYBUS_ARCHE
	tristate "Greybus Arche Platform driver"
	depends on USB_HSIC_USB3613 || COMPILE_TEST
	---help---
	  Select this option if you have an Arche device.

	  To compile this code as a module, chose M here: the module
	  will be called gb-arche.ko

endif	# GREYBUS
Commit	Line	Data
d4f56b47 GKH	1	menuconfig GREYBUS
	2	tristate "Greybus support"
	3	depends on SYSFS
	4	---help---
	5	This option enables the Greybus driver core. Greybus is an
	6	hardware protocol that was designed to provide Unipro with a
	7	sane application layer. It was originally designed for the
	8	ARA project, a module phone system, but has shown up in other
	9	phones, and can be tunneled over other busses in order to
	10	control hardware devices.
	11
	12	Say Y here to enable support for these types of drivers.
	13
	14	To compile this code as a module, chose M here: the module
	15	will be called greybus.ko
	16
	17	if GREYBUS
	18
	19	config GREYBUS_ES2
	20	tristate "Greybus ES3 USB host controller"
	21	depends on USB
	22	---help---
	23	Select this option if you have a Toshiba ES3 USB device that
	24	acts as a Greybus "host controller". This device is a bridge
	25	from a USB device to a Unipro network.
	26
	27	To compile this code as a module, chose M here: the module
	28	will be called gb-es2.ko
	29
	30	config GREYBUS_AUDIO
	31	tristate "Greybus Audio Class driver"
	32	depends on SOUND
	33	---help---
	34	Select this option if you have a device that follows the
	35	Greybus Audio Class specification.
	36
	37	To compile this code as a module, chose M here: the module
	38	will be called gb-audio.ko
	39
	40	config GREYBUS_BOOTROM
	41	tristate "Greybus Bootrom Class driver"
	42	---help---
	43	Select this option if you have a device that follows the
	44	Greybus Bootrom Class specification.
	45
	46	To compile this code as a module, chose M here: the module
	47	will be called gb-bootrom.ko
	48
	49	config GREYBUS_CAMERA
	50	tristate "Greybus Camera Class driver"
abf095b5	51	depends on MEDIA_SUPPORT && LEDS_CLASS_FLASH && BROKEN
d4f56b47 GKH	52	---help---
	53	Select this option if you have a device that follows the
	54	Greybus Camera Class specification.
	55
	56	To compile this code as a module, chose M here: the module
	57	will be called gb-camera.ko
	58
	59	config GREYBUS_FIRMWARE
	60	tristate "Greybus Firmware Download Class driver"
	61	depends on SPI
	62	---help---
	63	Select this option if you have a device that follows the
	64	Greybus Firmware Download Class specification.
	65
	66	To compile this code as a module, chose M here: the module
	67	will be called gb-firmware.ko
	68
	69	config GREYBUS_HID
	70	tristate "Greybus HID Class driver"
	71	depends on HID && INPUT
	72	---help---
	73	Select this option if you have a device that follows the
	74	Greybus HID Class specification.
	75
	76	To compile this code as a module, chose M here: the module
	77	will be called gb-hid.ko
	78
	79	config GREYBUS_LIGHT
	80	tristate "Greybus LED Class driver"
a0cf5951	81	depends on LEDS_CLASS
d4f56b47 GKH	82	---help---
	83	Select this option if you have a device that follows the
	84	Greybus LED Class specification.
	85
	86	To compile this code as a module, chose M here: the module
a0cf5951	87	will be called gb-light.ko
d4f56b47 GKH	88
	89	config GREYBUS_LOG
	90	tristate "Greybus Debug Log Class driver"
	91	---help---
	92	Select this option if you have a device that follows the
	93	Greybus Debug Log Class specification.
	94
	95	To compile this code as a module, chose M here: the module
	96	will be called gb-log.ko
	97
	98	config GREYBUS_LOOPBACK
	99	tristate "Greybus Loopback Class driver"
	100	---help---
	101	Select this option if you have a device that follows the
	102	Greybus Debug Log Class specification.
	103
	104	To compile this code as a module, chose M here: the module
	105	will be called gb-log.ko
	106
	107	config GREYBUS_POWER
	108	tristate "Greybus Powersupply Class driver"
	109	depends on POWER_SUPPLY
	110	---help---
	111	Select this option if you have a device that follows the
	112	Greybus Powersupply Class specification.
	113
	114	To compile this code as a module, chose M here: the module
	115	will be called gb-power-supply.ko
	116
	117	config GREYBUS_RAW
	118	tristate "Greybus Raw Class driver"
	119	---help---
	120	Select this option if you have a device that follows the
	121	Greybus Raw Class specification.
	122
	123	To compile this code as a module, chose M here: the module
	124	will be called gb-raw.ko
	125
	126	config GREYBUS_VIBRATOR
	127	tristate "Greybus Vibrator Motor Class driver"
	128	---help---
	129	Select this option if you have a device that follows the
	130	Greybus Vibrator Motor Class specification.
	131
	132	To compile this code as a module, chose M here: the module
	133	will be called gb-vibrator.ko
	134
	135	menuconfig GREYBUS_BRIDGED_PHY
	136	tristate "Greybus Bridged PHY Class drivers"
	137	---help---
	138	Select this option to pick from a variety of Greybus Bridged
	139	PHY class drivers. These drivers emulate a number of
	140	different "traditional" busses by tunneling them over Greybus.
	141	Examples of this include serial, SPI, USB, and others.
	142
	143	To compile this code as a module, chose M here: the module
	144	will be called gb-phy.ko
	145
	146	if GREYBUS_BRIDGED_PHY
	147
	148	config GREYBUS_GPIO
	149	tristate "Greybus GPIO Bridged PHY driver"
3e4b5b88	150	depends on GPIOLIB
d4f56b47 GKH	151	---help---
	152	Select this option if you have a device that follows the
	153	Greybus GPIO Bridged PHY Class specification.
	154
	155	To compile this code as a module, chose M here: the module
	156	will be called gb-gpio.ko
	157
	158	config GREYBUS_I2C
	159	tristate "Greybus I2C Bridged PHY driver"
	160	depends on I2C
	161	---help---
	162	Select this option if you have a device that follows the
	163	Greybus I2C Bridged PHY Class specification.
	164
	165	To compile this code as a module, chose M here: the module
	166	will be called gb-i2c.ko
	167
	168	config GREYBUS_PWM
	169	tristate "Greybus PWM Bridged PHY driver"
	170	depends on PWM
	171	---help---
	172	Select this option if you have a device that follows the
	173	Greybus PWM Bridged PHY Class specification.
	174
	175	To compile this code as a module, chose M here: the module
	176	will be called gb-pwm.ko
	177
	178	config GREYBUS_SDIO
	179	tristate "Greybus SDIO Bridged PHY driver"
	180	depends on MMC
	181	---help---
	182	Select this option if you have a device that follows the
	183	Greybus SDIO Bridged PHY Class specification.
	184
	185	To compile this code as a module, chose M here: the module
	186	will be called gb-sdio.ko
	187
	188	config GREYBUS_SPI
	189	tristate "Greybus SPI Bridged PHY driver"
	190	depends on SPI
	191	---help---
	192	Select this option if you have a device that follows the
	193	Greybus SPI Bridged PHY Class specification.
	194
	195	To compile this code as a module, chose M here: the module
	196	will be called gb-spi.ko
	197
	198	config GREYBUS_UART
	199	tristate "Greybus UART Bridged PHY driver"
	200	depends on TTY
	201	---help---
	202	Select this option if you have a device that follows the
	203	Greybus UART Bridged PHY Class specification.
	204
	205	To compile this code as a module, chose M here: the module
	206	will be called gb-uart.ko
	207
	208	config GREYBUS_USB
	209	tristate "Greybus USB Host Bridged PHY driver"
	210	depends on USB
	211	---help---
	212	Select this option if you have a device that follows the
	213	Greybus USB Host Bridged PHY Class specification.
	214
215	To compile this code as a module, chose M here: the module
216	will be called gb-usb.ko
217
218	endif # GREYBUS_BRIDGED_PHY
2eccd4aa JH	219
	220	config GREYBUS_ARCHE
	221	tristate "Greybus Arche Platform driver"
	222	depends on USB_HSIC_USB3613 \|\| COMPILE_TEST
	223	---help---
	224	Select this option if you have an Arche device.
	225
	226	To compile this code as a module, chose M here: the module
	227	will be called gb-arche.ko
	228
d4f56b47	229	endif # GREYBUS