summaryrefslogtreecommitdiff
path: root/drivers/sysreset
diff options
context:
space:
mode:
authorChris Packham <judge.packham@gmail.com>2019-04-13 20:35:23 +1200
committerTom Rini <trini@konsulko.com>2019-05-10 07:18:13 -0400
commit26680b9f3a874c0f7010cb239db0c6fa76d9a400 (patch)
tree59c4a38f622a67a74396fa90211766267ad373cf /drivers/sysreset
parent927a37df9f5ed33fc350b9cc509d9f50ffaf5cd2 (diff)
sysreset: select DM_GPIO instead of GPIO
CONFIG_GPIO does not exist. sysreset_gpio.c uses the DM gpio APIs so the correct option to select is DM_GPIO. Reported-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Chris Packham <judge.packham@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'drivers/sysreset')
-rw-r--r--drivers/sysreset/Kconfig2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/sysreset/Kconfig b/drivers/sysreset/Kconfig
index d456f0ce36..30aed2c4c1 100644
--- a/drivers/sysreset/Kconfig
+++ b/drivers/sysreset/Kconfig
@@ -35,7 +35,7 @@ if SYSRESET
config SYSRESET_GPIO
bool "Enable support for GPIO reset driver"
- select GPIO
+ select DM_GPIO
help
Reset support via GPIO pin connected reset logic. This is used for
example on Microblaze where reset logic can be controlled via GPIO