Kconfig 6.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220
  1. menuconfig 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. Say Y here to enable support for these types of drivers.
  12. To compile this code as a module, chose M here: the module
  13. will be called greybus.ko
  14. if GREYBUS
  15. config GREYBUS_ES2
  16. tristate "Greybus ES3 USB host controller"
  17. depends on USB
  18. ---help---
  19. Select this option if you have a Toshiba ES3 USB device that
  20. acts as a Greybus "host controller". This device is a bridge
  21. from a USB device to a Unipro network.
  22. To compile this code as a module, chose M here: the module
  23. will be called gb-es2.ko
  24. config GREYBUS_AUDIO
  25. tristate "Greybus Audio Class driver"
  26. depends on SOUND
  27. ---help---
  28. Select this option if you have a device that follows the
  29. Greybus Audio Class specification.
  30. To compile this code as a module, chose M here: the module
  31. will be called gb-audio.ko
  32. config GREYBUS_BOOTROM
  33. tristate "Greybus Bootrom Class driver"
  34. ---help---
  35. Select this option if you have a device that follows the
  36. Greybus Bootrom Class specification.
  37. To compile this code as a module, chose M here: the module
  38. will be called gb-bootrom.ko
  39. config GREYBUS_CAMERA
  40. tristate "Greybus Camera Class driver"
  41. depends on MEDIA_SUPPORT && LEDS_CLASS_FLASH && BROKEN
  42. ---help---
  43. Select this option if you have a device that follows the
  44. Greybus Camera Class specification.
  45. To compile this code as a module, chose M here: the module
  46. will be called gb-camera.ko
  47. config GREYBUS_FIRMWARE
  48. tristate "Greybus Firmware Download Class driver"
  49. depends on SPI
  50. ---help---
  51. Select this option if you have a device that follows the
  52. Greybus Firmware Download Class specification.
  53. To compile this code as a module, chose M here: the module
  54. will be called gb-firmware.ko
  55. config 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. To compile this code as a module, chose M here: the module
  62. will be called gb-hid.ko
  63. config GREYBUS_LIGHT
  64. tristate "Greybus LED Class driver"
  65. depends on LEDS_CLASS
  66. ---help---
  67. Select this option if you have a device that follows the
  68. Greybus LED Class specification.
  69. To compile this code as a module, chose M here: the module
  70. will be called gb-light.ko
  71. config GREYBUS_LOG
  72. tristate "Greybus Debug Log Class driver"
  73. ---help---
  74. Select this option if you have a device that follows the
  75. Greybus Debug Log Class specification.
  76. To compile this code as a module, chose M here: the module
  77. will be called gb-log.ko
  78. config GREYBUS_LOOPBACK
  79. tristate "Greybus Loopback Class driver"
  80. ---help---
  81. Select this option if you have a device that follows the
  82. Greybus Debug Log Class specification.
  83. To compile this code as a module, chose M here: the module
  84. will be called gb-log.ko
  85. config GREYBUS_POWER
  86. tristate "Greybus Powersupply Class driver"
  87. depends on POWER_SUPPLY
  88. ---help---
  89. Select this option if you have a device that follows the
  90. Greybus Powersupply Class specification.
  91. To compile this code as a module, chose M here: the module
  92. will be called gb-power-supply.ko
  93. config GREYBUS_RAW
  94. tristate "Greybus Raw Class driver"
  95. ---help---
  96. Select this option if you have a device that follows the
  97. Greybus Raw Class specification.
  98. To compile this code as a module, chose M here: the module
  99. will be called gb-raw.ko
  100. config GREYBUS_VIBRATOR
  101. tristate "Greybus Vibrator Motor Class driver"
  102. ---help---
  103. Select this option if you have a device that follows the
  104. Greybus Vibrator Motor Class specification.
  105. To compile this code as a module, chose M here: the module
  106. will be called gb-vibrator.ko
  107. menuconfig GREYBUS_BRIDGED_PHY
  108. tristate "Greybus Bridged PHY Class drivers"
  109. ---help---
  110. Select this option to pick from a variety of Greybus Bridged
  111. PHY class drivers. These drivers emulate a number of
  112. different "traditional" busses by tunneling them over Greybus.
  113. Examples of this include serial, SPI, USB, and others.
  114. To compile this code as a module, chose M here: the module
  115. will be called gb-phy.ko
  116. if GREYBUS_BRIDGED_PHY
  117. config GREYBUS_GPIO
  118. tristate "Greybus GPIO Bridged PHY driver"
  119. depends on GPIOLIB
  120. ---help---
  121. Select this option if you have a device that follows the
  122. Greybus GPIO Bridged PHY Class specification.
  123. To compile this code as a module, chose M here: the module
  124. will be called gb-gpio.ko
  125. config GREYBUS_I2C
  126. tristate "Greybus I2C Bridged PHY driver"
  127. depends on I2C
  128. ---help---
  129. Select this option if you have a device that follows the
  130. Greybus I2C Bridged PHY Class specification.
  131. To compile this code as a module, chose M here: the module
  132. will be called gb-i2c.ko
  133. config GREYBUS_PWM
  134. tristate "Greybus PWM Bridged PHY driver"
  135. depends on PWM
  136. ---help---
  137. Select this option if you have a device that follows the
  138. Greybus PWM Bridged PHY Class specification.
  139. To compile this code as a module, chose M here: the module
  140. will be called gb-pwm.ko
  141. config GREYBUS_SDIO
  142. tristate "Greybus SDIO Bridged PHY driver"
  143. depends on MMC
  144. ---help---
  145. Select this option if you have a device that follows the
  146. Greybus SDIO Bridged PHY Class specification.
  147. To compile this code as a module, chose M here: the module
  148. will be called gb-sdio.ko
  149. config GREYBUS_SPI
  150. tristate "Greybus SPI Bridged PHY driver"
  151. depends on SPI
  152. ---help---
  153. Select this option if you have a device that follows the
  154. Greybus SPI Bridged PHY Class specification.
  155. To compile this code as a module, chose M here: the module
  156. will be called gb-spi.ko
  157. config GREYBUS_UART
  158. tristate "Greybus UART Bridged PHY driver"
  159. depends on TTY
  160. ---help---
  161. Select this option if you have a device that follows the
  162. Greybus UART Bridged PHY Class specification.
  163. To compile this code as a module, chose M here: the module
  164. will be called gb-uart.ko
  165. config GREYBUS_USB
  166. tristate "Greybus USB Host Bridged PHY driver"
  167. depends on USB
  168. ---help---
  169. Select this option if you have a device that follows the
  170. Greybus USB Host Bridged PHY Class specification.
  171. To compile this code as a module, chose M here: the module
  172. will be called gb-usb.ko
  173. endif # GREYBUS_BRIDGED_PHY
  174. endif # GREYBUS