diff options
| author | Fabio Estevam <festevam@gmail.com> | 2020-01-29 14:45:33 -0300 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2020-02-05 19:33:46 -0700 |
| commit | 1d6a0c9503f221df0e46564bfcf96a16095a0ca7 (patch) | |
| tree | d88bfaa85c377ed612caec96a309e810c1294f63 /doc/driver-model | |
| parent | 5ed2dc5623b45ebd51d71f7daffd0cbcbc441186 (diff) | |
| download | u-boot-1d6a0c9503f221df0e46564bfcf96a16095a0ca7.zip u-boot-1d6a0c9503f221df0e46564bfcf96a16095a0ca7.tar.gz u-boot-1d6a0c9503f221df0e46564bfcf96a16095a0ca7.tar.bz2 | |
doc: dm: debugging: Fix the steps for activating debug
Following the recommendation of adding '#define DEBUG' at the top
of drivers/core/lists.c does not cause the debug messages to be
shown. Change it to '#define LOG_DEBUG' instead, which actually
makes it work as per doc/README.log.
While at it, provide the full path to lists.c to in order to make
the instructions clearer.
Signed-off-by: Fabio Estevam <festevam@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc/driver-model')
| -rw-r--r-- | doc/driver-model/debugging.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/driver-model/debugging.rst b/doc/driver-model/debugging.rst index 4f4a8d4..c59bf67 100644 --- a/doc/driver-model/debugging.rst +++ b/doc/driver-model/debugging.rst @@ -58,5 +58,5 @@ If you are using of-platdata (e.g. CONFIG_SPL_OF_PLATDATA), check that the driver name is the same as the first compatible string in the device tree (with invalid-variable characters converted to underscore). -If you are really stuck, #define DEBUG at the top of lists.c should show you -what is going on. +If you are really stuck, putting '#define LOG_DEBUG' at the top of +drivers/core/lists.c should show you what is going on. |