Help¶

Using atomic operations is the fastest way to ensure mutually exclusive access to the ARM CryptoCell hardware.

Warning: If this configuration is set, every execution requiring use of the ARM CryptoCell hardware must happen in the same priority. Calling into mbed TLS APIs from a higher priority while an ongoing operation will lead to undefined behavior. It is highy recommended to to do all cryptographic operations in one single thread if this configuration is set.

Direct dependencies¶

(Includes any dependencies from ifs and menus.)

Kconfig definition¶

At <nrfxlib>/crypto/Kconfig:50

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:23 → <Zephyr>/modules/Kconfig:6 → <BuildDir>/Kconfig/Kconfig.modules:14 → <nrfxlib>/Kconfig.nrfxlib:12

Menu path: (Top) → Modules → nrfxlib (/home/runner/work/sdk-nrf/sdk-nrf/ncs/nrfxlib) → Nordic nrfxlib → Crypto libraries for nRF5x SOCs. → nrf_cc3xx_platform HW crypto library for nRF devices with CryptoCell CC3xx. → CC3XX lock variant

config CC3XX_ATOMIC_LOCK
    bool "Use atomic variables for mutually exclusive access to CC3XX resources"
    depends on <choice CC3XX_LOCK_VARIANT: CC3XX lock variant>
    help
      Using atomic operations is the fastest way to ensure mutually exclusive
      access to the ARM CryptoCell hardware.

      Warning: If this configuration is set, every execution requiring use of
      the ARM CryptoCell hardware must happen in the same priority. Calling into
      mbed TLS APIs from a higher priority while an ongoing operation will lead
      to undefined behavior. It is highy recommended to to do all cryptographic
      operations in one single thread if this configuration is set.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)