From: Chris Packham <judge.packham@gmail.com>
Date: Sat, 13 Apr 2019 08:35:23 +0000 (+1200)
Subject: sysreset: select DM_GPIO instead of GPIO
X-Git-Url: http://git.lede-project.org./?a=commitdiff_plain;h=26680b9f3a874c0f7010cb239db0c6fa76d9a400;p=project%2Fbcm63xx%2Fu-boot.git

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>
---

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