u-boot/drivers/gpio/Kconfig
Masahiro Yamada 0b11dbf705 drivers: hierarchize drivers Kconfig menu
The menuconfig for drivers are getting more and more cluttered
and unreadable because too many entries are displayed in a single
flat menu.  Use hierarchic menu for each category.

Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
[trini: Update to apply again in a few places, drop USB hunk]
Signed-off-by: Tom Rini <trini@konsulko.com>
2015-08-12 20:47:44 -04:00

52 lines
1.5 KiB
Text

#
# GPIO infrastructure and drivers
#
menu "GPIO Support"
config DM_GPIO
bool "Enable Driver Model for GPIO drivers"
depends on DM
help
Enable driver model for GPIO access. The standard GPIO
interface (gpio_get_value(), etc.) is then implemented by
the GPIO uclass. Drivers provide methods to query the
particular GPIOs that they provide. The uclass interface
is defined in include/asm-generic/gpio.h.
config LPC32XX_GPIO
bool "LPC32XX GPIO driver"
depends on DM
default n
help
Support for the LPC32XX GPIO driver.
config SANDBOX_GPIO
bool "Enable sandbox GPIO driver"
depends on SANDBOX && DM && DM_GPIO
help
This driver supports some simulated GPIOs which can be adjusted
using 'back door' functions like sandbox_gpio_set_value(). Then the
GPIOs can be inspected through the normal get_get_value()
interface. The purpose of this is to allow GPIOs to be used as
normal in sandbox, perhaps with test code actually driving the
behaviour of those GPIOs.
config SANDBOX_GPIO_COUNT
int "Number of sandbox GPIOs"
depends on SANDBOX_GPIO
default 128
help
The sandbox driver can support any number of GPIOs. Generally these
are specified using the device tree. But you can also have a number
of 'anonymous' GPIOs that do not belong to any device or bank.
Select a suitable value depending on your needs.
config VYBRID_GPIO
bool "Vybrid GPIO driver"
depends on DM
default n
help
Say yes here to support Vybrid vf610 GPIOs.
endmenu