1 # SPDX-License-Identifier: GPL-2.0
5 tristate "Greybus Audio Class driver"
6 depends on SOUND && SND_SOC
8 Select this option if you have a device that follows the
9 Greybus Audio Class specification.
11 To compile this code as a module, chose M here: the module
12 will be called gb-audio.ko
14 config GREYBUS_AUDIO_APB_CODEC
15 tristate "Greybus APBridge Audio codec driver"
16 depends on SND_SOC && GREYBUS_AUDIO
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.
22 To compile this code as a module, chose M here: the module
23 will be called gb-audio-codec.ko
26 config GREYBUS_BOOTROM
27 tristate "Greybus Bootrom Class driver"
29 Select this option if you have a device that follows the
30 Greybus Bootrom Class specification.
32 To compile this code as a module, chose M here: the module
33 will be called gb-bootrom.ko
36 tristate "Greybus Camera Class driver"
37 depends on MEDIA_SUPPORT && LEDS_CLASS_FLASH && BROKEN
39 Select this option if you have a device that follows the
40 Greybus Camera Class specification.
42 To compile this code as a module, chose M here: the module
43 will be called gb-camera.ko
45 config GREYBUS_FIRMWARE
46 tristate "Greybus Firmware Download Class driver"
49 Select this option if you have a device that follows the
50 Greybus Firmware Download Class specification.
52 To compile this code as a module, chose M here: the module
53 will be called gb-firmware.ko
56 tristate "Greybus HID Class driver"
57 depends on HID && INPUT
59 Select this option if you have a device that follows the
60 Greybus HID Class specification.
62 To compile this code as a module, chose M here: the module
63 will be called gb-hid.ko
66 tristate "Greybus LED Class driver"
67 depends on LEDS_CLASS_FLASH
69 Select this option if you have a device that follows the
70 Greybus LED Class specification.
72 To compile this code as a module, chose M here: the module
73 will be called gb-light.ko
76 tristate "Greybus Debug Log Class driver"
78 Select this option if you have a device that follows the
79 Greybus Debug Log Class specification.
81 To compile this code as a module, chose M here: the module
82 will be called gb-log.ko
84 config GREYBUS_LOOPBACK
85 tristate "Greybus Loopback Class driver"
87 Select this option if you have a device that follows the
88 Greybus Debug Log Class specification.
90 To compile this code as a module, chose M here: the module
91 will be called gb-log.ko
94 tristate "Greybus Powersupply Class driver"
95 depends on POWER_SUPPLY
97 Select this option if you have a device that follows the
98 Greybus Powersupply Class specification.
100 To compile this code as a module, chose M here: the module
101 will be called gb-power-supply.ko
104 tristate "Greybus Raw Class driver"
106 Select this option if you have a device that follows the
107 Greybus Raw Class specification.
109 To compile this code as a module, chose M here: the module
110 will be called gb-raw.ko
112 config GREYBUS_VIBRATOR
113 tristate "Greybus Vibrator Motor Class driver"
115 Select this option if you have a device that follows the
116 Greybus Vibrator Motor Class specification.
118 To compile this code as a module, chose M here: the module
119 will be called gb-vibrator.ko
121 menuconfig GREYBUS_BRIDGED_PHY
122 tristate "Greybus Bridged PHY Class drivers"
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.
129 To compile this code as a module, chose M here: the module
130 will be called gb-phy.ko
132 if GREYBUS_BRIDGED_PHY
135 tristate "Greybus GPIO Bridged PHY driver"
137 select GPIOLIB_IRQCHIP
139 Select this option if you have a device that follows the
140 Greybus GPIO Bridged PHY Class specification.
142 To compile this code as a module, chose M here: the module
143 will be called gb-gpio.ko
146 tristate "Greybus I2C Bridged PHY driver"
149 Select this option if you have a device that follows the
150 Greybus I2C Bridged PHY Class specification.
152 To compile this code as a module, chose M here: the module
153 will be called gb-i2c.ko
156 tristate "Greybus PWM Bridged PHY driver"
159 Select this option if you have a device that follows the
160 Greybus PWM Bridged PHY Class specification.
162 To compile this code as a module, chose M here: the module
163 will be called gb-pwm.ko
166 tristate "Greybus SDIO Bridged PHY driver"
169 Select this option if you have a device that follows the
170 Greybus SDIO Bridged PHY Class specification.
172 To compile this code as a module, chose M here: the module
173 will be called gb-sdio.ko
176 tristate "Greybus SPI Bridged PHY driver"
179 Select this option if you have a device that follows the
180 Greybus SPI Bridged PHY Class specification.
182 To compile this code as a module, chose M here: the module
183 will be called gb-spi.ko
186 tristate "Greybus UART Bridged PHY driver"
189 Select this option if you have a device that follows the
190 Greybus UART Bridged PHY Class specification.
192 To compile this code as a module, chose M here: the module
193 will be called gb-uart.ko
196 tristate "Greybus USB Host Bridged PHY driver"
199 Select this option if you have a device that follows the
200 Greybus USB Host Bridged PHY Class specification.
202 To compile this code as a module, chose M here: the module
203 will be called gb-usb.ko
205 endif # GREYBUS_BRIDGED_PHY
208 tristate "Greybus Arche Platform driver"
209 depends on USB_HSIC_USB3613 || COMPILE_TEST
211 Select this option if you have an Arche device.
213 To compile this code as a module, chose M here: the module
214 will be called gb-arche.ko