zephyr/include/logging
Krzysztof Chruscinski 6b01c89935 logging: Add log initialization to system startup
Log API can be used before user can explicitly initialize the logger.
In order to ensure that logger core is ready to buffer log messages
it must be initialize as early as possible. Initialization does not
include initialization of default backend since driver may not be
ready and backend is needed only when log messages are processed.

Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
2018-07-14 08:32:44 -04:00
..
event_logger.h
kernel_event_logger.h subsys: kernel_event_logger: change kernel event values 2018-02-23 07:29:29 -05:00
log_backend_uart.h logging: subsystem major redesign 2018-06-29 10:16:45 +02:00
log_backend.h doc: subsys: logging: Add documentation for new logger 2018-07-06 19:18:19 -04:00
log_core.h logging: Ensure constant side effects of log API 2018-07-11 10:56:36 -04:00
log_ctrl.h logging: Add log initialization to system startup 2018-07-14 08:32:44 -04:00
log_instance.h logging: Fix fail when log locally disabled 2018-07-11 10:31:59 -04:00
log_msg.h logging: Add log initialization to system startup 2018-07-14 08:32:44 -04:00
log_output.h doc: subsys: logging: Add documentation for new logger 2018-07-06 19:18:19 -04:00
log.h logging: Fix fail when log locally disabled 2018-07-11 10:31:59 -04:00
sys_log.h include: logging: clean up of sys_log.h 2018-02-09 10:11:52 -05:00