menuconfig [31mCONFIG_GREYBUS[0m
tristate "Greybus support"
depends on [31mCONFIG_SYSFS[0m
---help---
This option enables the Greybus driver core. Greybus is an
hardware protocol that was designed to provide Unipro with a
sane application layer. It was originally designed for the
ARA project, a module phone system, but has shown up in other
phones, and can be tunneled over other busses in order to
control hardware devices.
Say Y here to enable support for these types of drivers.
To compile this code as a module, chose [31mCONFIG_M[0m here: the module
will be called greybus.ko
if [31mCONFIG_GREYBUS[0m
config [31mCONFIG_GREYBUS_ES2[0m
tristate "Greybus ES3 USB host controller"
depends on [31mCONFIG_USB[0m
---help---
Select this option if you have a Toshiba ES3 [31mCONFIG_USB[0m device that
acts as a Greybus "host controller". This device is a bridge
from a [31mCONFIG_USB[0m device to a Unipro network.
To compile this code as a module, chose [31mCONFIG_M[0m here: the module
will be called gb-es2.ko
config [31mCONFIG_GREYBUS_AUDIO[0m
tristate "Greybus Audio Class driver"
depends on [31mCONFIG_SOUND[0m
---help---
Select this option if you have a device that follows the
Greybus Audio Class specification.
To compile this code as a module, chose [31mCONFIG_M[0m here: the module
will be called gb-audio.ko
config [31mCONFIG_GREYBUS_BOOTROM[0m
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 [31mCONFIG_M[0m here: the module
will be called gb-bootrom.ko
config [31mCONFIG_GREYBUS_CAMERA[0m
tristate "Greybus Camera Class driver"
depends on [31mCONFIG_MEDIA_SUPPORT[0m && [31mCONFIG_LEDS_CLASS_FLASH[0m && [31mCONFIG_BROKEN[0m
---help---
Select this option if you have a device that follows the
Greybus Camera Class specification.
To compile this code as a module, chose [31mCONFIG_M[0m here: the module
will be called gb-camera.ko
config [31mCONFIG_GREYBUS_FIRMWARE[0m
tristate "Greybus Firmware Download Class driver"
depends on [31mCONFIG_SPI[0m
---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 [31mCONFIG_M[0m here: the module
will be called gb-firmware.ko
config [31mCONFIG_GREYBUS_HID[0m
tristate "Greybus HID Class driver"
depends on [31mCONFIG_HID[0m && [31mCONFIG_INPUT[0m
---help---
Select this option if you have a device that follows the
Greybus [31mCONFIG_HID[0m Class specification.
To compile this code as a module, chose [31mCONFIG_M[0m here: the module
will be called gb-hid.ko
config [31mCONFIG_GREYBUS_LIGHT[0m
tristate "Greybus LED Class driver"
depends on [31mCONFIG_LEDS_CLASS[0m
---help---
Select this option if you have a device that follows the
Greybus LED Class specification.
To compile this code as a module, chose [31mCONFIG_M[0m here: the module
will be called gb-light.ko
config [31mCONFIG_GREYBUS_LOG[0m
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 [31mCONFIG_M[0m here: the module
will be called gb-log.ko
config [31mCONFIG_GREYBUS_LOOPBACK[0m
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 [31mCONFIG_M[0m here: the module
will be called gb-log.ko
config [31mCONFIG_GREYBUS_POWER[0m
tristate "Greybus Powersupply Class driver"
depends on [31mCONFIG_POWER_SUPPLY[0m
---help---
Select this option if you have a device that follows the
Greybus Powersupply Class specification.
To compile this code as a module, chose [31mCONFIG_M[0m here: the module
will be called gb-power-supply.ko
config [31mCONFIG_GREYBUS_RAW[0m
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 [31mCONFIG_M[0m here: the module
will be called gb-raw.ko
config [31mCONFIG_GREYBUS_VIBRATOR[0m
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 [31mCONFIG_M[0m here: the module
will be called gb-vibrator.ko
menuconfig [31mCONFIG_GREYBUS_BRIDGED_PHY[0m
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, [31mCONFIG_SPI[0m, [31mCONFIG_USB[0m, and others.
To compile this code as a module, chose [31mCONFIG_M[0m here: the module
will be called gb-phy.ko
if [31mCONFIG_GREYBUS_BRIDGED_PHY[0m
config [31mCONFIG_GREYBUS_GPIO[0m
tristate "Greybus GPIO Bridged PHY driver"
depends on [31mCONFIG_GPIOLIB[0m
---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 [31mCONFIG_M[0m here: the module
will be called gb-gpio.ko
config [31mCONFIG_GREYBUS_I2C[0m
tristate "Greybus I2C Bridged PHY driver"
depends on [31mCONFIG_I2C[0m
---help---
Select this option if you have a device that follows the
Greybus [31mCONFIG_I2C[0m Bridged PHY Class specification.
To compile this code as a module, chose [31mCONFIG_M[0m here: the module
will be called gb-i2c.ko
config [31mCONFIG_GREYBUS_PWM[0m
tristate "Greybus PWM Bridged PHY driver"
depends on [31mCONFIG_PWM[0m
---help---
Select this option if you have a device that follows the
Greybus [31mCONFIG_PWM[0m Bridged PHY Class specification.
To compile this code as a module, chose [31mCONFIG_M[0m here: the module
will be called gb-pwm.ko
config [31mCONFIG_GREYBUS_SDIO[0m
tristate "Greybus SDIO Bridged PHY driver"
depends on [31mCONFIG_MMC[0m
---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 [31mCONFIG_M[0m here: the module
will be called gb-sdio.ko
config [31mCONFIG_GREYBUS_SPI[0m
tristate "Greybus SPI Bridged PHY driver"
depends on [31mCONFIG_SPI[0m
---help---
Select this option if you have a device that follows the
Greybus [31mCONFIG_SPI[0m Bridged PHY Class specification.
To compile this code as a module, chose [31mCONFIG_M[0m here: the module
will be called gb-spi.ko
config [31mCONFIG_GREYBUS_UART[0m
tristate "Greybus UART Bridged PHY driver"
depends on [31mCONFIG_TTY[0m
---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 [31mCONFIG_M[0m here: the module
will be called gb-uart.ko
config [31mCONFIG_GREYBUS_USB[0m
tristate "Greybus USB Host Bridged PHY driver"
depends on [31mCONFIG_USB[0m
---help---
Select this option if you have a device that follows the
Greybus [31mCONFIG_USB[0m Host Bridged PHY Class specification.
To compile this code as a module, chose [31mCONFIG_M[0m here: the module
will be called gb-usb.ko
endif # [31mCONFIG_GREYBUS_BRIDGED_PHY[0m
endif # [31mCONFIG_GREYBUS[0m