diff options
| author | Simon Glass <sjg@chromium.org> | 2020-09-12 11:13:34 -0600 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2020-10-10 16:49:58 -0400 |
| commit | 52d3df7fefe30b05677db9055e68c666a071d89a (patch) | |
| tree | 949ff257975a134f8fbf923debec6f8bd013cce6 /dts | |
| parent | 0437cc415517c06c864bee5dbce3001d70b2c2cb (diff) | |
| download | u-boot-52d3df7fefe30b05677db9055e68c666a071d89a.zip u-boot-52d3df7fefe30b05677db9055e68c666a071d89a.tar.gz u-boot-52d3df7fefe30b05677db9055e68c666a071d89a.tar.bz2 | |
log: Allow LOG_DEBUG to always enable log output
At present if CONFIG_LOG enabled, putting LOG_DEBUG at the top of a file
(before log.h inclusion) causes _log() to be executed for every log()
call, regardless of the build- or run-time logging level.
However there is no guarantee that the log record will actually be
displayed. If the current log level is lower than LOGL_DEBUG then it will
not be.
Add a way to signal that the log record should always be displayed and
update log_passes_filters() to handle this.
With the new behaviour, log_debug() will always log if LOG_DEBUG is
enabled.
Move log_test_syslog_nodebug() into its own file since it cannot be made
to work where it is, with LOG_DEBUG defined.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'dts')
0 files changed, 0 insertions, 0 deletions