A few reset drivers cannot build without access to some platform
specific header files. Express those requirements in Kconfig as well.
Signed-off-by: Tom Rini <tr...@konsulko.com>
---
drivers/reset/Kconfig | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/reset/Kconfig b/drivers/reset/Kconfig
index e92bb8a7c39d..74c267dfc4e5 100644
--- a/drivers/reset/Kconfig
+++ b/drivers/reset/Kconfig
@@ -74,8 +74,8 @@ config RESET_UNIPHIER
config RESET_AST2500
bool "Reset controller driver for AST2500 SoCs"
- depends on DM_RESET
- default y if ASPEED_AST2500
+ depends on DM_RESET && ASPEED_AST2500
+ default y
help
Support for reset controller on AST2500 SoC.
Say Y if you want to control reset signals of different peripherals
@@ -83,8 +83,8 @@ config RESET_AST2500
config RESET_AST2600
bool "Reset controller driver for AST2600 SoCs"
- depends on DM_RESET
- default y if ASPEED_AST2600
+ depends on DM_RESET && ASPEED_AST2600
+ default y
help
Support for reset controller on AST2600 SoC.
Say Y if you want to control reset signals of different peripherals
@@ -223,7 +223,7 @@ config RESET_ZYNQMP
config RESET_DRA7
bool "Support for TI's DRA7 Reset driver"
- depends on DM_RESET
+ depends on DM_RESET && ARCH_OMAP2PLUS
help
Support for TI DRA7-RESET subsystem. Basic Assert/Deassert
is supported.
--
2.43.0
