subsys/shell/Kconfig.template.shell_log_queue_timeout

# SPDX-License-Identifier: Apache-2.0

config $(module)_LOG_MESSAGE_QUEUE_TIMEOUT
	int "Log message drop timeout (in milliseconds)"
	default $(default-timeout)
	range -1 10000
	help
	  If queue with pending log messages is full, oldest log message is
	  dropped if queue is still full after requested time (-1 is forever).
	  Logger thread is blocked for that period, thus long timeout impacts
	  other logger  backends and must be used with care.
license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-04-06 09:08:09 -04:00			`# SPDX-License-Identifier: Apache-2.0`

shell: Improve handling of log messages If burst of log messages was passed to the shell log backend, it was likely that messages were lost because shell had no means to control arrivals of log messages. Added log message enqueueing timeout to the shell instance to allow blocking logger thread if short-term arrival rate exceeded shell capabilities. Added kconfig option for setting log message queue size and timeout in RTT and UART instances. Added section in shell documentation which explains interaction between the logger and shell instance acting as a logger backend. Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no> 2018-12-17 10:43:58 +01:00			`config $(module)_LOG_MESSAGE_QUEUE_TIMEOUT`
			`int "Log message drop timeout (in milliseconds)"`
			`default $(default-timeout)`
			`range -1 10000`
			`help`
			`If queue with pending log messages is full, oldest log message is`
			`dropped if queue is still full after requested time (-1 is forever).`
			`Logger thread is blocked for that period, thus long timeout impacts`
			`other logger backends and must be used with care.`