Home
last modified time | relevance | path

Searched refs:lock (Results 401 – 425 of 483) sorted by relevance

1...<<11121314151617181920

/Zephyr-latest/doc/hardware/peripherals/edac/
Dibecc.rst76 "protected" by a lock with an NMI, because the protection does not work. The
/Zephyr-latest/samples/bluetooth/eddystone/src/
Dmain.c143 uint8_t lock[16]; member
153 .lock = { 'Z', 'e', 'p', 'h', 'y', 'r', ' ', 'E', 'd', 'd',
/Zephyr-latest/drivers/dma/
Ddma_iproc_pax.h478 struct k_mutex lock; member
/Zephyr-latest/drivers/eeprom/
Deeprom_mchp_xec.c60 uint32_t lock; member
/Zephyr-latest/boards/mikroe/mini_m4_for_stm32/doc/
Dmikroe_mini_m4_for_stm32.rst99 The initial state of the board is set to lock.
/Zephyr-latest/boards/mikroe/clicker_2/doc/
Dmikroe_clicker_2.rst69 The initial state of the board is set to lock.
/Zephyr-latest/drivers/ethernet/
Deth_xmc4xxx.c558 uint32_t lock; in eth_xmc4xxx_isr() local
562 lock = irq_lock(); in eth_xmc4xxx_isr()
585 irq_unlock(lock); in eth_xmc4xxx_isr()
Deth_adin2111.c120 return k_mutex_lock(&ctx->lock, timeout); in eth_adin2111_lock()
127 return k_mutex_unlock(&ctx->lock); in eth_adin2111_unlock()
1562 .lock = Z_MUTEX_INITIALIZER(name##_data_##inst.lock), \
/Zephyr-latest/include/zephyr/portability/
Dcmsis_os2.h334 int32_t osKernelRestoreLock(int32_t lock);
/Zephyr-latest/include/zephyr/drivers/
Dregulator.h240 struct k_mutex lock; member
/Zephyr-latest/drivers/adc/
Dadc_stm32wb0.c949 res = k_sem_take(&data->ctx.lock, K_NO_WAIT); in adc_stm32wb0_channel_setup()
1005 k_sem_give(&data->ctx.lock); in adc_stm32wb0_channel_setup()
/Zephyr-latest/tests/benchmarks/latency_measure/
DREADME.rst13 * Times to lock a mutex then unlock that mutex
104 …mutex.lock.immediate.recursive.kernel - Lock a mutex : …
157 …mutex.lock.immediate.recursive.kernel - Lock a mutex : …
214 …mutex.lock.immediate.recursive.kernel - Lock a mutex : …
348 …mutex.lock.immediate.recursive.kernel - Lock a mutex : …
350 …mutex.lock.immediate.recursive.user - Lock a mutex : …
/Zephyr-latest/kernel/
Dmmu.c524 bool lock = (flags & K_MEM_MAP_LOCK) != 0U; in map_anon_page() local
554 if (lock) { in map_anon_page()
559 if (IS_ENABLED(CONFIG_EVICTION_TRACKING) && (!lock)) { in map_anon_page()
/Zephyr-latest/include/zephyr/net/
Dlwm2m.h221 struct k_mutex lock; member
Dnet_if.h717 struct k_mutex lock; member
743 (void)k_mutex_lock(&iface->lock, K_FOREVER); in net_if_lock()
750 k_mutex_unlock(&iface->lock); in net_if_unlock()
/Zephyr-latest/tests/benchmarks/app_kernel/
DREADME.txt35 | average lock and unlock mutex | NNNNNN|
/Zephyr-latest/doc/services/pm/
Ddevice.rst323 To avoid this sort of problem, devices must :ref:`get and release lock <pm-policy-power-states>`
327 loss and an API that automatically get and put lock on them. This feature is
371 After that devices can lock these state calling
/Zephyr-latest/subsys/fs/
Dfuse_fs_access.c453 .lock = NULL,
/Zephyr-latest/drivers/disk/nvme/
Dnvme_controller.c423 k_mutex_init(&nvme_ctrlr->lock); in nvme_controller_init()
/Zephyr-latest/subsys/bluetooth/audio/shell/
Dcsip_set_coordinator.c580 SHELL_CMD_ARG(lock, NULL,
/Zephyr-latest/boards/amd/kv260_r5/doc/
Dindex.rst9 * Or as a single dual lock step unit with double the TCM size.
/Zephyr-latest/include/zephyr/
Dnet_buf.h1083 struct k_spinlock lock; member
1123 .lock = { }, \
/Zephyr-latest/subsys/net/lib/lwm2m/
Dlwm2m_engine.c1331 (void)k_mutex_lock(&ctx->lock, K_FOREVER); in lwm2m_client_lock()
1336 k_mutex_unlock(&ctx->lock); in lwm2m_client_unlock()
/Zephyr-latest/doc/services/zbus/
Dindex.rst151 * The channel lock is acquired;
247 (as simple as lock, memory copy, unlock), continues its execution and goes out of the CPU.
299 (as simple as lock, memory copy, unlock), continues its execution, and goes out the CPU.
372 lock mechanism;
522 It is unnecessary to claim/lock a channel before accessing the message inside the listener since
524 however, must claim/lock that or use regular read operations to access the message after being
/Zephyr-latest/drivers/usb/uhc/
Duhc_virtual.c512 .lock = uhc_vrt_lock,

1...<<11121314151617181920