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