/Zephyr-latest/doc/kernel/services/other/ |
D | atomic.rst | 6 An :dfn:`atomic variable` is one that can be read and modified 17 Any number of atomic variables can be defined (limited only by available RAM). 19 Using the kernel's atomic APIs to manipulate an atomic variable 23 The kernel also supports the atomic manipulation of a single bit 24 in an array of atomic variables. 32 An atomic variable is defined using a variable of type :c:type:`atomic_t`. 34 By default an atomic variable is initialized to zero. However, it can be given 44 An atomic variable is manipulated using the APIs listed at the end of 47 The following code shows how an atomic variable can be used to keep track 69 An array of 32-bit atomic variables can be defined in the conventional manner. [all …]
|
/Zephyr-latest/doc/kernel/data_structures/ |
D | spsc_lockfree.rst | 7 atomic ring buffer based queue.
|
D | mpsc_lockfree.rst | 7 intrusive queue based on atomic pointer swaps as described by Dmitry Vyukov
|
/Zephyr-latest/tests/kernel/common/src/ |
D | atomic.c | 97 ZTEST_USER(atomic, test_atomic) in ZTEST_USER() argument 317 ZTEST(atomic, test_threads_access_atomic) in ZTEST() argument 354 ZTEST(atomic, test_atomic_overflow) in ZTEST() argument 387 ZTEST_SUITE(atomic, NULL, common_setup, NULL, NULL, NULL);
|
/Zephyr-latest/tests/kernel/common/ |
D | CMakeLists.txt | 13 src/atomic.c
|
/Zephyr-latest/include/zephyr/drivers/ |
D | dma.h | 303 atomic_t *atomic; member 584 if (!atomic_test_and_set_bit(dma_ctx->atomic, i)) { in z_impl_dma_request_channel() 587 atomic_clear_bit(dma_ctx->atomic, i); in z_impl_dma_request_channel() 630 atomic_clear_bit(dma_ctx->atomic, channel); in z_impl_dma_release_channel()
|
/Zephyr-latest/tests/kernel/context/src/ |
D | main.c | 223 static void _test_kernel_cpu_idle(int atomic) in _test_kernel_cpu_idle() argument 242 if (atomic) { in _test_kernel_cpu_idle() 259 static void _test_kernel_cpu_idle(int atomic) in _test_kernel_cpu_idle() argument 272 if (atomic) { in _test_kernel_cpu_idle()
|
/Zephyr-latest/arch/sparc/ |
D | Kconfig | 38 Use CASA atomic instructions. Defined by SPARC V9 and available
|
/Zephyr-latest/drivers/dma/ |
D | dma_silabs_ldma.c | 403 atomic_set_bit(data->dma_ctx.atomic, channel); in dma_silabs_configure() 452 if (!atomic_test_bit(data->dma_ctx.atomic, channel)) { in dma_silabs_get_status() 518 .dma_ctx.atomic = dma_channels_atomic_##inst, \
|
D | dma_nxp_sof_host_dma.c | 290 data->ctx.atomic = &data->channel_flags; in sof_host_dma_init()
|
D | dma_intel_adsp_hda.c | 408 data->ctx.atomic = data->channels_atomic; in intel_adsp_hda_dma_init() 469 enabled_chs = atomic_get(dma_ctx->atomic); in intel_adsp_hda_dma_isr()
|
D | dma_si32.c | 51 .atomic = dma_si32_atomic,
|
D | dma_smartbond.c | 962 if (atomic_test_bit(data->dma_ctx.atomic, i)) { in dma_smartbond_is_sleep_allowed() 1020 data->dma_ctx.atomic = data->channels_atomic; in dma_smartbond_init()
|
D | dma_rpi_pico.c | 377 .atomic = dma_rpi_pico_atomic##inst, \
|
D | dma_intel_adsp_gpdma.c | 473 dev_data->dma_ctx.atomic = dev_data->channels_atomic; in intel_adsp_gpdma_init()
|
D | dma_nxp_sdma.c | 448 data->dma_ctx.atomic = data->channels_atomic; in dma_nxp_sdma_init()
|
D | dma_xmc4xxx.c | 492 .atomic = dma_xmc4xxx_atomic##inst, \
|
/Zephyr-latest/doc/kernel/services/ |
D | index.rst | 121 other/atomic.rst
|
/Zephyr-latest/doc/hardware/peripherals/edac/ |
D | ibecc.rst | 78 against an NMI is the atomic layer. This also applies to callback function
|
/Zephyr-latest/arch/riscv/ |
D | Kconfig.isa | 39 The standard atomic instruction extension is denoted by instruction
|
/Zephyr-latest/doc/hardware/arch/ |
D | arc-support-status.rst | 50 | Hardware-assisted atomic operations | N/A | Y | …
|
/Zephyr-latest/doc/services/tracing/ |
D | index.rst | 590 Unfortunately, I/O may not be atomic and may, therefore, require locking. 593 - The system has non-atomic write and one shared channel 598 - The system has non-atomic write but many channels 605 - The system has atomic write but one shared channel 612 - The system has atomic write and many channels
|
/Zephyr-latest/doc/security/ |
D | sensor-threat.rst | 57 c. The image update shall be seen as atomic, meaning that when the 60 [th-atomic-update]_. 351 .. [th-atomic-update] 352 Application updates shall be atomic.
|
/Zephyr-latest/kernel/ |
D | Kconfig.smp | 121 atomic variable and doesn't guarantee locking fairness
|
/Zephyr-latest/doc/kernel/services/synchronization/ |
D | mutexes.rst | 174 kernel involvement. Uncontended operation relies only on atomic access
|