aboutsummaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2019-07-20 20:51:21 -0600
committerTom Rini <trini@konsulko.com>2019-08-02 11:19:14 -0400
commit8fc31e23aa83dfe9a01bec5738ccbed7d4ad442e (patch)
tree50379cccc118437797e13565a9899591c726d687 /scripts
parent2452bb7636beb5eeae29185518a899349289c609 (diff)
downloadu-boot-8fc31e23aa83dfe9a01bec5738ccbed7d4ad442e.zip
u-boot-8fc31e23aa83dfe9a01bec5738ccbed7d4ad442e.tar.gz
u-boot-8fc31e23aa83dfe9a01bec5738ccbed7d4ad442e.tar.bz2
autoboot: Rename CONFIG_MENUKEY to CONFIG_AUTOBOOT_MENUKEY
Since this is part of the autoboot functionality, it makes sense to name it with an AUTOBOOT prefix. No mainline boards use it so this should be safe, and downstream boards will need to adjust. Since this option is just an integer value, it really needs another option to control whether the feature is enabled or not. Add a new CONFIG_USE_AUTOBOOT_MENUKEY for that. This fits better with how things are done with Kconfig, avoiding the need to use a specific value to disable the feature. Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'scripts')
-rw-r--r--scripts/config_whitelist.txt1
1 files changed, 0 insertions, 1 deletions
diff --git a/scripts/config_whitelist.txt b/scripts/config_whitelist.txt
index 2849441..3de5021 100644
--- a/scripts/config_whitelist.txt
+++ b/scripts/config_whitelist.txt
@@ -1140,7 +1140,6 @@ CONFIG_MEMSIZE_MASK
CONFIG_MEM_HOLE_16M
CONFIG_MEM_INIT_VALUE
CONFIG_MEM_REMAP
-CONFIG_MENUKEY
CONFIG_MENU_SHOW
CONFIG_MFG_ENV_SETTINGS
CONFIG_MIIM_ADDRESS