pw_log_zephyr

Overview

This interrupt backend implements the pw_log facade. Currently, two separate Pigweed backends are implemented. One that uses the plain Zephyr logging framework and routes Pigweed’s logs to Zephyr. While another maps the Zephyr logging macros to Pigweed’s tokenized logging.

Using Zephyr logging

To enable, set CONFIG_PIGWEED_LOG_ZEPHYR=y. After that, logging can be controlled via the standard Kconfig options. All logs made through PW_LOG_* are logged to the Zephyr logging module pigweed. In this model, the Zephyr logging is set as pw_log’s backend.

Using Pigweed tokenized logging

Using the pigweed logging can be done by enabling CONFIG_PIGWEED_LOG_TOKENIZED=y. At that point pw_log_tokenized is set as the backedn for pw_log and all Zephyr logs are routed to Pigweed’s logging facade. This means that any logging statements made in Zephyr itself are also tokenized.

Setting the log level

In order to remain compatible with existing Pigweed code, the logging backend respects PW_LOG_LEVEL. If set, the backend will translate the Pigweed log levels to their closest Zephyr counterparts:

Pigweed	Zephyr
PW_LOG_LEVEL_DEBUG	LOG_LEVEL_DBG
PW_LOG_LEVEL_INFO	LOG_LEVEL_INF
PW_LOG_LEVEL_WARN	LOG_LEVEL_WRN
PW_LOG_LEVEL_ERROR PW_LOG_LEVEL_CRITICAL PW_LOG_LEVEL_FATAL	LOG_LEVEL_ERR

Alternatively, it is also possible to set the Zephyr logging level directly via CONFIG_PIGWEED_LOG_LEVEL.