Searched refs:lock (Results 451 – 475 of 483) sorted by relevance
1...<<11121314151617181920
| /Zephyr-latest/drivers/usb/udc/ |
| D | udc_stm32.c | 811 .lock = udc_stm32_lock,
|
| D | udc_kinetis.c | 1153 .lock = usbfsotg_lock,
|
| D | udc_rpi_pico.c | 1064 .lock = udc_rpi_pico_lock,
|
| D | udc_numaker.c | 1719 .lock = udc_numaker_lock,
|
| D | udc_it82xx2.c | 1522 .lock = it82xx2_lock,
|
| D | udc_smartbond.c | 1709 .lock = udc_smartbond_lock,
|
| D | udc_dwc2.c | 2972 .lock = udc_dwc2_lock,
|
| /Zephyr-latest/modules/trusted-firmware-m/ |
| D | CMakeLists.txt | 291 # file lock mechanism. To ensure correct behaviour in all cases, limit
|
| /Zephyr-latest/arch/riscv/ |
| D | Kconfig | 144 writing the mstatus register to lock and unlock the IRQs.
|
| /Zephyr-latest/dts/arm/microchip/ |
| D | mec172x_common.dtsi | 24 pll-lock-timeout-ms = <30>;
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | clocks.rst | 248 minimizes the chance that an errant ISR or interrupt lock will delay
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.9.rst | 331 * ``ZEP-2445`` - nrf52: CPU lock-up when using Bluetooth + Flash driver + CONFIG_ASSERT
|
| D | release-notes-3.0.rst | 790 :c:func:`pm_device_state_is_locked`) to lock a device pm
913 * :github:`42353` - LwM2M not pass official LightweightM2M-1.1-int-256 and stack enter dead lock
1174 * :github:`40107` - lwm2m: if network drops during firmware update, lock occurs
|
| D | release-notes-1.7.rst | 389 * ``ZEP-1619`` - Default value of NET_NBUF_RX_COUNT is too low, causes lock up on startup
|
| D | release-notes-3.6.rst | 1020 * Fixed an issue in MCUmgr FS management whereby the semaphore lock would not be given if an
1191 …* Replaced mutexes with semaphores to lock channels and implement the Highest Locker Protocol (HLP)
|
| D | release-notes-3.3.rst | 1080 * Added shell command to lock/unlock LwM2M registry.
1631 - new property: ``pll-lock-timeout-ms``
2785 - :github:`54411` - mgmt: mcumgr: Shell transport can lock shell up until device is rebooted
2808 - :github:`54668` - shell: "log backend" command causes shell to lock up
3309 * :github:`51827` - picolibc heap lock recursion mismatch
|
| D | release-notes-2.6.rst | 1384 * :github:`34369` - Driver esp for wifi got a dead lock.
1648 * :github:`33319` - Kernel doesn't validate lock state on swap
2065 * :github:`29610` - documentation says giving a semaphore can release IRQ lock
|
| D | release-notes-3.7.rst | 1087 …* Move lock-free queues out of RTIO into lib, dropping the ``rtio_`` prefix to SPSC and MPSC queue…
1733 to lock and unlock all power states that cause power loss in a device.
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 374 …Therefore, it is recommended to simply always lock the binding, whether or not the resource being …
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | index.rst | 283 scheduler lock. Meta-IRQ threads are still threads, however,
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | lwm2m.rst | 790 lock :Lock the LwM2M registry
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | arm_cortex_m.rst | 355 interrupts unconditionally, that is, regardless of the interrupt lock
|
| /Zephyr-latest/arch/ |
| D | Kconfig | 866 supports DCLS, but is configured in split-lock mode (by default or
|
| /Zephyr-latest/kernel/ |
| D | Kconfig | 99 otherwise cooperative and/or have taken a scheduler lock.
|
| /Zephyr-latest/subsys/net/lib/lwm2m/ |
| D | lwm2m_message_handling.c | 487 k_mutex_init(&client_ctx->lock); in lwm2m_engine_context_init()
|
1...<<11121314151617181920
