217 lines · plain
1# SPDX-License-Identifier: GPL-2.02if GREYBUS3 4config GREYBUS_AUDIO5 tristate "Greybus Audio Class driver"6 depends on SOUND && SND_SOC7 help8 Select this option if you have a device that follows the9 Greybus Audio Class specification.10 11 To compile this code as a module, chose M here: the module12 will be called gb-audio.ko13 14config GREYBUS_AUDIO_APB_CODEC15 tristate "Greybus APBridge Audio codec driver"16 depends on SND_SOC && GREYBUS_AUDIO17 help18 Select this option if you have a Toshiba APB device that has I2S19 ports and acts as a Greybus "Dummy codec". This device is a20 bridge from an APB-I2S port to a Unipro network.21 22 To compile this code as a module, chose M here: the module23 will be called gb-audio-codec.ko24 25 26config GREYBUS_BOOTROM27 tristate "Greybus Bootrom Class driver"28 help29 Select this option if you have a device that follows the30 Greybus Bootrom Class specification.31 32 To compile this code as a module, chose M here: the module33 will be called gb-bootrom.ko34 35config GREYBUS_CAMERA36 tristate "Greybus Camera Class driver"37 depends on MEDIA_SUPPORT && LEDS_CLASS_FLASH && BROKEN38 help39 Select this option if you have a device that follows the40 Greybus Camera Class specification.41 42 To compile this code as a module, chose M here: the module43 will be called gb-camera.ko44 45config GREYBUS_FIRMWARE46 tristate "Greybus Firmware Download Class driver"47 depends on SPI48 help49 Select this option if you have a device that follows the50 Greybus Firmware Download Class specification.51 52 To compile this code as a module, chose M here: the module53 will be called gb-firmware.ko54 55config GREYBUS_HID56 tristate "Greybus HID Class driver"57 depends on HID && INPUT58 help59 Select this option if you have a device that follows the60 Greybus HID Class specification.61 62 To compile this code as a module, chose M here: the module63 will be called gb-hid.ko64 65config GREYBUS_LIGHT66 tristate "Greybus LED Class driver"67 depends on LEDS_CLASS_FLASH68 help69 Select this option if you have a device that follows the70 Greybus LED Class specification.71 72 To compile this code as a module, chose M here: the module73 will be called gb-light.ko74 75config GREYBUS_LOG76 tristate "Greybus Debug Log Class driver"77 help78 Select this option if you have a device that follows the79 Greybus Debug Log Class specification.80 81 To compile this code as a module, chose M here: the module82 will be called gb-log.ko83 84config GREYBUS_LOOPBACK85 tristate "Greybus Loopback Class driver"86 help87 Select this option if you have a device that follows the88 Greybus Debug Log Class specification.89 90 To compile this code as a module, chose M here: the module91 will be called gb-log.ko92 93config GREYBUS_POWER94 tristate "Greybus Powersupply Class driver"95 depends on POWER_SUPPLY96 help97 Select this option if you have a device that follows the98 Greybus Powersupply Class specification.99 100 To compile this code as a module, chose M here: the module101 will be called gb-power-supply.ko102 103config GREYBUS_RAW104 tristate "Greybus Raw Class driver"105 help106 Select this option if you have a device that follows the107 Greybus Raw Class specification.108 109 To compile this code as a module, chose M here: the module110 will be called gb-raw.ko111 112config GREYBUS_VIBRATOR113 tristate "Greybus Vibrator Motor Class driver"114 help115 Select this option if you have a device that follows the116 Greybus Vibrator Motor Class specification.117 118 To compile this code as a module, chose M here: the module119 will be called gb-vibrator.ko120 121menuconfig GREYBUS_BRIDGED_PHY122 tristate "Greybus Bridged PHY Class drivers"123 help124 Select this option to pick from a variety of Greybus Bridged125 PHY class drivers. These drivers emulate a number of126 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 module130 will be called gb-phy.ko131 132if GREYBUS_BRIDGED_PHY133 134config GREYBUS_GPIO135 tristate "Greybus GPIO Bridged PHY driver"136 depends on GPIOLIB137 select GPIOLIB_IRQCHIP138 help139 Select this option if you have a device that follows the140 Greybus GPIO Bridged PHY Class specification.141 142 To compile this code as a module, chose M here: the module143 will be called gb-gpio.ko144 145config GREYBUS_I2C146 tristate "Greybus I2C Bridged PHY driver"147 depends on I2C148 help149 Select this option if you have a device that follows the150 Greybus I2C Bridged PHY Class specification.151 152 To compile this code as a module, chose M here: the module153 will be called gb-i2c.ko154 155config GREYBUS_PWM156 tristate "Greybus PWM Bridged PHY driver"157 depends on PWM158 help159 Select this option if you have a device that follows the160 Greybus PWM Bridged PHY Class specification.161 162 To compile this code as a module, chose M here: the module163 will be called gb-pwm.ko164 165config GREYBUS_SDIO166 tristate "Greybus SDIO Bridged PHY driver"167 depends on MMC168 help169 Select this option if you have a device that follows the170 Greybus SDIO Bridged PHY Class specification.171 172 To compile this code as a module, chose M here: the module173 will be called gb-sdio.ko174 175config GREYBUS_SPI176 tristate "Greybus SPI Bridged PHY driver"177 depends on SPI178 help179 Select this option if you have a device that follows the180 Greybus SPI Bridged PHY Class specification.181 182 To compile this code as a module, chose M here: the module183 will be called gb-spi.ko184 185config GREYBUS_UART186 tristate "Greybus UART Bridged PHY driver"187 depends on TTY188 help189 Select this option if you have a device that follows the190 Greybus UART Bridged PHY Class specification.191 192 To compile this code as a module, chose M here: the module193 will be called gb-uart.ko194 195config GREYBUS_USB196 tristate "Greybus USB Host Bridged PHY driver"197 depends on USB198 help199 Select this option if you have a device that follows the200 Greybus USB Host Bridged PHY Class specification.201 202 To compile this code as a module, chose M here: the module203 will be called gb-usb.ko204 205endif # GREYBUS_BRIDGED_PHY206 207config GREYBUS_ARCHE208 tristate "Greybus Arche Platform driver"209 depends on USB_HSIC_USB3613 || COMPILE_TEST210 help211 Select this option if you have an Arche device.212 213 To compile this code as a module, chose M here: the module214 will be called gb-arche.ko215 216endif # GREYBUS217