af37c09440
So far LOG_DBG() was used inside debug hook for mbedTLS library. This meant that it was hard to distinct log messages by simply looking at the log level number, even though Zephyr logging subsystem supports colorful logs depending on log level. Choose an appropriate Zephyr LOG_*() macro based on log level coming from mbedTLS library. Remove log level number from formatted log messages, as it is now redundant. One controversial thing about this change is that mbedTLS' "2 State change" log level is mapped to Zephyr's "warning" log level. Those are not really warnings in real life, but rather informational messages. However, using "warning" log level for those allows to clearly distinguish between "2 State change" and "3 Informational" debug messages from mbedTLS. Additionally, mbedTLS debug message implementation does not seem to be safe to use in production, so keeping in mind MBEDTLS_DEBUG will be enabled just during debugging phase, printing "2 State change" logs as warnings should not be a big deal. Set default MBEDTLS_DEBUG_LEVEL value depending on selected Zephyr logging module level, so that only single option needs to be configured in application project. Remove prompt for MBEDTLS_DEBUG_LEVEL, so that interactively (e.g. via menuconfig) adjusting MBEDTLS_LOG_LEVEL will always result in automatically updating MBEDTLS_DEBUG_LEVEL option. This is to prevent so called "stuck symbol syndrome". Signed-off-by: Marcin Niestroj <m.niestroj@emb.dev> |
||
|---|---|---|
| .. | ||
| application_development | ||
| arch | ||
| benchmarks | ||
| bluetooth | ||
| boards | ||
| boot/uefi | ||
| cmake/config_dir | ||
| crypto | ||
| drivers | ||
| kernel | ||
| lib | ||
| misc | ||
| net | ||
| posix | ||
| subsys | ||
| unit | ||
| ztest | ||