1menuconfig 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
17if GREYBUS
18
19config 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
30config 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
40config 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
49config GREYBUS_CAMERA
50	tristate "Greybus Camera Class driver"
51	depends on MEDIA_SUPPORT && LEDS_CLASS_FLASH && BROKEN
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
59config 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
69config 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
79config GREYBUS_LIGHT
80	tristate "Greybus LED Class driver"
81	depends on LEDS_CLASS
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
87	  will be called gb-light.ko
88
89config 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
98config 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
107config 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
117config 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
126config 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
135menuconfig 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
146if GREYBUS_BRIDGED_PHY
147
148config GREYBUS_GPIO
149	tristate "Greybus GPIO Bridged PHY driver"
150	depends on GPIOLIB
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
158config 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
168config 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
178config 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
188config 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
198config 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
208config 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
218endif	# GREYBUS_BRIDGED_PHY
219
220config 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
229endif	# GREYBUS
230