summaryrefslogtreecommitdiff
path: root/common/Kconfig
diff options
context:
space:
mode:
authorAdam Ford <aford173@gmail.com>2018-07-08 07:28:10 -0500
committerTom Rini <trini@konsulko.com>2018-07-21 22:26:58 -0400
commit9d04b5fe16018953720ff01eeb7636d9ec31bb36 (patch)
tree3b497658a762dc6756c61ba99ab9eb84cda30360 /common/Kconfig
parenteba7f1ff6c9836931f0ce2812182190862e38b5f (diff)
configs: Make NAND_BOOT and ONENAND_BOOT imply NAND
Some boards indicate support from booting NAND or ONENAND booting, but don't enable the CONFIG_NAND. This makes those boards imply NAND which will make enabling other flags that are dependent on CONFIG_NAND possible and easier to migrate. Signed-off-by: Adam Ford <aford173@gmail.com>
Diffstat (limited to 'common/Kconfig')
-rw-r--r--common/Kconfig2
1 files changed, 2 insertions, 0 deletions
diff --git a/common/Kconfig b/common/Kconfig
index 81e88ea77c..dc2e1c23dd 100644
--- a/common/Kconfig
+++ b/common/Kconfig
@@ -125,6 +125,7 @@ config NOR_BOOT
config NAND_BOOT
bool "Support for booting from NAND flash"
default n
+ imply NAND
help
Enabling this will make a U-Boot binary that is capable of being
booted via NAND flash. This is not a must, some SoCs need this,
@@ -133,6 +134,7 @@ config NAND_BOOT
config ONENAND_BOOT
bool "Support for booting from ONENAND"
default n
+ imply NAND
help
Enabling this will make a U-Boot binary that is capable of being
booted via ONENAND. This is not a must, some SoCs need this,