michaelh/zephyr
1
0
Fork 0
Code Releases Activity

logging: Internal processing thread enabled by default

Browse source 
Enabling internal processing thread allows implicit initialization
and processing log messages in case mutlithreading is enabled.

Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
This commit is contained in:
Krzysztof Chruscinski 2018-07-19 14:27:07 +02:00 • committed by Anas Nashif
commit 86b5edc4d0
2 changed files with 3 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
samples/subsys/logging/logger/prj.conf
View file

@ -2,4 +2,4 @@ CONFIG_LOG=y
CONFIG_LOG_RUNTIME_FILTERING=y
CONFIG_LOG_BUFFER_SIZE=2048
CONFIG_LOG_PRINTK=y
CONFIG_LOG_PROCESS_THREAD=y
CONFIG_LOG_PROCESS_TRIGGER_THRESHOLD=0

3
subsys/logging/Kconfig
View file

@ -210,7 +210,7 @@ config LOG_INPLACE_PROCESS
config LOG_PROCESS_TRIGGER_THRESHOLD
int "Amount of buffered logs which triggers processing thread."
default 0
default 10
help
When number of buffered messages reaches the threshold thread is waken
up. Log processing thread ID is provided during log initialization.
@ -220,6 +220,7 @@ config LOG_PROCESS_TRIGGER_THRESHOLD
config LOG_PROCESS_THREAD
bool "Enable internal thread for log processing"
depends on MULTITHREADING
default y
help
When enabled thread is created by the logger subsystem. Thread is
waken up periodically (see LOG_PROCESS_THREAD_SLEEP_MS) and whenever