:orphan:

.. title:: LOG_IMMEDIATE_CLEAN_OUTPUT

.. option:: CONFIG_LOG_IMMEDIATE_CLEAN_OUTPUT

*Clean log output*

Type: ``bool``

Help
====

If enabled, interrupts are locked during whole log message processing.
As a result, processing on one log message cannot be interrupted by
another one and output is clean, not interleaved. However, enabling
this option is causing interrupts locking for significant amount of
time (up to multiple milliseconds).

Direct dependencies
===================

\ :option:`LOG_IMMEDIATE <CONFIG_LOG_IMMEDIATE>` && !\ :option:`LOG_FRONTEND <CONFIG_LOG_FRONTEND>` && !\ :option:`LOG_MINIMAL <CONFIG_LOG_MINIMAL>` && \ :option:`LOG <CONFIG_LOG>`

*(Includes any dependencies from ifs and menus.)*

Defaults
========

No defaults. Implicitly defaults to ``n``.

Kconfig definition
==================

.. highlight:: kconfig

At ``subsys/logging/Kconfig.formatting:30``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:34`` → ``subsys/Kconfig:31`` → ``subsys/logging/Kconfig:21``

Menu path: (Top) → Sub Systems and OS Services → Logging → Output Formatting

.. parsed-literal::

    config LOG_IMMEDIATE_CLEAN_OUTPUT
    	bool "Clean log output"
    	depends on \ :option:`LOG_IMMEDIATE <CONFIG_LOG_IMMEDIATE>` && !\ :option:`LOG_FRONTEND <CONFIG_LOG_FRONTEND>` && !\ :option:`LOG_MINIMAL <CONFIG_LOG_MINIMAL>` && \ :option:`LOG <CONFIG_LOG>`
    	help
    	  If enabled, interrupts are locked during whole log message processing.
    	  As a result, processing on one log message cannot be interrupted by
    	  another one and output is clean, not interleaved. However, enabling
    	  this option is causing interrupts locking for significant amount of
    	  time (up to multiple milliseconds).

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*