Move these over to Kconfig and tidy up/
Signed-off-by: Simon Glass sjg@chromium.org ---
configs/sandbox_defconfig | 1 + drivers/gpio/Kconfig | 21 +++++++++++++++++++++ include/configs/sandbox.h | 2 -- 3 files changed, 22 insertions(+), 2 deletions(-)
diff --git a/configs/sandbox_defconfig b/configs/sandbox_defconfig index 3255003..15d13b5 100644 --- a/configs/sandbox_defconfig +++ b/configs/sandbox_defconfig @@ -13,3 +13,4 @@ CONFIG_CROS_EC_SANDBOX=y CONFIG_CROS_EC_KEYB=y CONFIG_CMD_CROS_EC=y CONFIG_BOOTSTAGE=y +CONFIG_SANDBOX_GPIO=y diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig index b609e73..6a682f2 100644 --- a/drivers/gpio/Kconfig +++ b/drivers/gpio/Kconfig @@ -7,3 +7,24 @@ config DM_GPIO 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 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. diff --git a/include/configs/sandbox.h b/include/configs/sandbox.h index bc8a392..a880acb 100644 --- a/include/configs/sandbox.h +++ b/include/configs/sandbox.h @@ -49,8 +49,6 @@ #define CONFIG_SYS_VSNPRINTF
#define CONFIG_CMD_GPIO -#define CONFIG_SANDBOX_GPIO -#define CONFIG_SANDBOX_GPIO_COUNT 128
#define CONFIG_CMD_GPT #define CONFIG_PARTITION_UUIDS