summaryrefslogtreecommitdiff
path: root/configs/sandbox_defconfig
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2017-12-28 13:14:23 -0700
committerSimon Glass <sjg@chromium.org>2018-02-03 10:09:27 -0700
commit3707c6ee0d1f939130a62c945b56045d9a83fafc (patch)
tree86b7c70cf64113d77001fed0b2a57396aa3439a2 /configs/sandbox_defconfig
parent8cb7c04248c9f0c3b79325b82844d79a680ef2eb (diff)
log: Add a way to log error-return values
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 <sjg@chromium.org>
Diffstat (limited to 'configs/sandbox_defconfig')
-rw-r--r--configs/sandbox_defconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/configs/sandbox_defconfig b/configs/sandbox_defconfig
index 7efb4ebf11..41a2e34235 100644
--- a/configs/sandbox_defconfig
+++ b/configs/sandbox_defconfig
@@ -18,6 +18,7 @@ CONFIG_PRE_CONSOLE_BUFFER=y
CONFIG_PRE_CON_BUF_ADDR=0x100000
CONFIG_LOG=y
CONFIG_LOG_MAX_LEVEL=6
+CONFIG_LOG_ERROR_RETURN=y
CONFIG_CMD_CPU=y
CONFIG_CMD_LICENSE=y
CONFIG_CMD_BOOTZ=y