summaryrefslogtreecommitdiff
path: root/include
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 /include
parent2452bb7636beb5eeae29185518a899349289c609 (diff)
downloadu-boot-8fc31e23aa83dfe9a01bec5738ccbed7d4ad442e.tar.gz
u-boot-8fc31e23aa83dfe9a01bec5738ccbed7d4ad442e.tar.bz2
u-boot-8fc31e23aa83dfe9a01bec5738ccbed7d4ad442e.zip
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 'include')
-rw-r--r--include/autoboot.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/autoboot.h b/include/autoboot.h
index 3ebd6f90e3..ac8157e570 100644
--- a/include/autoboot.h
+++ b/include/autoboot.h
@@ -27,7 +27,7 @@ const char *bootdelay_process(void);
* autoboot_command() - run the autoboot command
*
* If enabled, run the autoboot command returned from bootdelay_process().
- * Also do the CONFIG_MENUKEY processing if enabled.
+ * Also do the CONFIG_AUTOBOOT_MENUKEY processing if enabled.
*
* @cmd: Command to run
*/