:orphan:

.. title:: CONFIG_SPIN_VALIDATE

.. kconfig:: CONFIG_SPIN_VALIDATE

CONFIG_SPIN_VALIDATE
####################

*Enable spinlock validation*

Type: ``bool``

Help
====

.. code-block:: none

    There's a spinlock validation framework available when asserts are
    enabled. It adds a relatively hefty overhead (about 3k or so) to
    kernel code size, don't use on platforms known to be small.

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

\ :kconfig:`ASSERT <CONFIG_ASSERT>` && \ :kconfig:`MULTITHREADING <CONFIG_MULTITHREADING>` && \ :kconfig:`MP_NUM_CPUS <CONFIG_MP_NUM_CPUS>` <= 4

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

Default
=======

- y if !\ :kconfig:`FLASH <CONFIG_FLASH>` || \ :kconfig:`FLASH_SIZE <CONFIG_FLASH_SIZE>` > 32

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



At ``<Zephyr Subsystem>/debug/Kconfig:217``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:44`` → ``<Zephyr Subsystem>/Kconfig:17``

Menu path: (Top) → Sub Systems and OS Services → Debugging Options → Enable __ASSERT() macro

.. code-block:: kconfig

    config SPIN_VALIDATE
    	bool "Enable spinlock validation"
    	default y if !FLASH || FLASH_SIZE > 32
    	depends on ASSERT && MULTITHREADING && MP_NUM_CPUS <= 4
    	help
    	  There's a spinlock validation framework available when asserts are
    	  enabled. It adds a relatively hefty overhead (about 3k or so) to
    	  kernel code size, don't use on platforms known to be small.

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