log: Fix up Kconfig log level names

The log level numbers in the Kconfig are not actually correct. Fix them
and also add a missing space in the header-file comment.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
This commit is contained in:
Simon Glass 2019-02-16 20:24:34 -07:00 committed by Bin Meng
parent 97f9830849
commit 6fc7e93896
2 changed files with 38 additions and 30 deletions

View file

@ -286,14 +286,16 @@ config LOGLEVEL
All Messages with a loglevel smaller than the console loglevel will All Messages with a loglevel smaller than the console loglevel will
be compiled in. The loglevels are defined as follows: be compiled in. The loglevels are defined as follows:
0 (KERN_EMERG) system is unusable 0 - emergency
1 (KERN_ALERT) action must be taken immediately 1 - alert
2 (KERN_CRIT) critical conditions 2 - critical
3 (KERN_ERR) error conditions 3 - error
4 (KERN_WARNING) warning conditions 4 - warning
5 (KERN_NOTICE) normal but significant condition 5 - note
6 (KERN_INFO) informational 6 - info
7 (KERN_DEBUG) debug-level messages 7 - debug
8 - debug content
9 - debug hardware I/O
config SPL_LOGLEVEL config SPL_LOGLEVEL
int int
@ -482,14 +484,16 @@ config LOG_MAX_LEVEL
higher than this will be ignored. If possible log statements below higher than this will be ignored. If possible log statements below
this level will be discarded at build time. Levels: this level will be discarded at build time. Levels:
0 - panic 0 - emergency
1 - critical 1 - alert
2 - error 2 - critical
3 - warning 3 - error
4 - note 4 - warning
5 - info 5 - note
6 - detail 6 - info
7 - debug 7 - debug
8 - debug content
9 - debug hardware I/O
config SPL_LOG_MAX_LEVEL config SPL_LOG_MAX_LEVEL
int "Maximum log level to record in SPL" int "Maximum log level to record in SPL"
@ -500,14 +504,16 @@ config SPL_LOG_MAX_LEVEL
higher than this will be ignored. If possible log statements below higher than this will be ignored. If possible log statements below
this level will be discarded at build time. Levels: this level will be discarded at build time. Levels:
0 - panic 0 - emergency
1 - critical 1 - alert
2 - error 2 - critical
3 - warning 3 - error
4 - note 4 - warning
5 - info 5 - note
6 - detail 6 - info
7 - debug 7 - debug
8 - debug content
9 - debug hardware I/O
config TPL_LOG_MAX_LEVEL config TPL_LOG_MAX_LEVEL
int "Maximum log level to record in TPL" int "Maximum log level to record in TPL"
@ -518,14 +524,16 @@ config TPL_LOG_MAX_LEVEL
higher than this will be ignored. If possible log statements below higher than this will be ignored. If possible log statements below
this level will be discarded at build time. Levels: this level will be discarded at build time. Levels:
0 - panic 0 - emergency
1 - critical 1 - alert
2 - error 2 - critical
3 - warning 3 - error
4 - note 4 - warning
5 - info 5 - note
6 - detail 6 - info
7 - debug 7 - debug
8 - debug content
9 - debug hardware I/O
config LOG_CONSOLE config LOG_CONSOLE
bool "Allow log output to the console" bool "Allow log output to the console"

View file

@ -14,7 +14,7 @@
/** Log levels supported, ranging from most to least important */ /** Log levels supported, ranging from most to least important */
enum log_level_t { enum log_level_t {
LOGL_EMERG = 0, /*U-Boot is unstable */ LOGL_EMERG = 0, /* U-Boot is unstable */
LOGL_ALERT, /* Action must be taken immediately */ LOGL_ALERT, /* Action must be taken immediately */
LOGL_CRIT, /* Critical conditions */ LOGL_CRIT, /* Critical conditions */
LOGL_ERR, /* Error that prevents something from working */ LOGL_ERR, /* Error that prevents something from working */