log: Add a Kconfig option to set the default log level

At present the default log level is set to LOGL_INFO on start-up. Allow
this to be controlled from Kconfig.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>

diff --git a/common/Kconfig b/common/Kconfig
index 849d8ff90ad29d3108d4bd99adc270885245a0c6..e100c2294961944fcfbaeb9d174b79fe9a2b6812 100644 (file)
--- a/common/Kconfig
+++ b/common/Kconfig
@@ -535,6 +535,26 @@ config TPL_LOG_MAX_LEVEL
            8 - debug content
            9 - debug hardware I/O
 
+config LOG_DEFAULT_LEVEL
+       int "Default logging level to display"
+       default 6
+       help
+         This is the default logging level set when U-Boot starts. It can
+         be adjusted later using the 'log level' command. Note that setting
+         this to a value abnove LOG_MAX_LEVEL will be ineffective, since the
+         higher levels are not compiled in to U-Boot.
+
+           0 - emergency
+           1 - alert
+           2 - critical
+           3 - error
+           4 - warning
+           5 - note
+           6 - info
+           7 - debug
+           8 - debug content
+           9 - debug hardware I/O
+
 config LOG_CONSOLE
        bool "Allow log output to the console"
        depends on LOG

diff --git a/common/log.c b/common/log.c
index ec14644516c14d70bcd4d94438a42653f2cd4cc5..ffb3cd6933223a1622e2cc7e2543f3f5a86586c8 100644 (file)
--- a/common/log.c
+++ b/common/log.c
@@ -316,7 +316,7 @@ int log_init(void)
        }
        gd->flags |= GD_FLG_LOG_READY;
        if (!gd->default_log_level)
-               gd->default_log_level = LOGL_INFO;
+               gd->default_log_level = CONFIG_LOG_DEFAULT_LEVEL;
        gd->log_fmt = LOGF_DEFAULT;
 
        return 0;