| commit | 57e8d5ecfb4dcba2e19b87c9d1b048e6b1090584 | [log] [tgz] |
|---|---|---|
| author | Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com> | Fri Feb 28 16:43:08 2025 +0100 |
| committer | Alberto Escolar <alberto.escolar.piedras@nordicsemi.no> | Fri Mar 07 20:20:00 2025 +0100 |
| tree | 36932ba8b150ecb2e1dcd8c43385ff083928a586 | |
| parent | 4eb917f884a861c70faf1553156ff96e58c5272f [diff] |
log: fix log_flush() The logging thread is usually woken up by a timer, if the timer period is longer than 10ms, log_flush() can iterate multiple times needlessly, while waiting for the next timer. Instead wake up the logging thread to let it flush the queue immediately. Besides a hard-coded polling period of 10ms is too long for some applications, make it a Kconfig parameter. Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>