Loading...
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 | # SPDX-License-Identifier: GPL-2.0 if GREYBUS config GREYBUS_AUDIO tristate "Greybus Audio Class driver" depends on SOUND && SND_SOC 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_AUDIO_APB_CODEC tristate "Greybus APBridge Audio codec driver" depends on SND_SOC && GREYBUS_AUDIO help Select this option if you have a Toshiba APB device that has I2S ports and acts as a Greybus "Dummy codec". This device is a bridge from an APB-I2S port to a Unipro network. To compile this code as a module, chose M here: the module will be called gb-audio-codec.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 select GPIOLIB_IRQCHIP 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 |