20 Feb, 2019
2 commits
-
At present it is possible to '#define DEBUG' at the top of a file which
causes all debug() statements in that file to become active. There is
currently no equivalent with logging, but this is a useful function.Add a LOG_DEBUG define along with documentation.
Signed-off-by: Simon Glass
Reviewed-by: Bin Meng -
The log_debug(), etc. function are documented only in the header file at
present. Add a section to README.log also.Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
10 Apr, 2018
1 commit
-
Without the units these numbers are confusing. Add a comment about the
unit being 'bytes' and mention 'buildman' as the source.Suggested-by: Lukasz Majewski
Signed-off-by: Simon Glass
04 Feb, 2018
3 commits
-
The EFI implementation does not fit into any of the existing categories.
Provide LOGC_EFI so that EFI related message can be filtered.
Signed-off-by: Heinrich Schuchardt
Reviewed-by: Simon Glass -
When functions return an error it propagates up the stack to the point
where it is reported. Often the error code provides enough information
about the root cause of the error that this is obvious what went wrong.However in some cases the error may be hard to trace. For example if a
driver uses several devices to perform an operation, it may not be
obvious which one failed.Add a log_ret() macro to help with this. This can be used to wrap any
error-return value. The logging system will then output a log record when
the original error is generated, making it easy to trace the call stack
of the error.This macro can significantly impact code size, so its use is controlled
by a Kconfig option, which is enabled for sandbox.Signed-off-by: Simon Glass
-
Add some notes about recent new features.
Signed-off-by: Simon Glass
08 Dec, 2017
1 commit
-
Add documentation for the log system.
Signed-off-by: Simon Glass
Reviewed-by: Bin Meng