Home
last modified time | relevance | path

Searched refs:likely (Results 1 – 25 of 82) sorted by relevance

1234

/Zephyr-latest/drivers/entropy/
Dentropy_nrf5.c151 while (likely(len--)) { in rng_pool_get()
161 if (likely(!other_read_in_progress)) { in rng_pool_get()
261 if (likely((flags & ENTROPY_BUSYWAIT) == 0U)) { in entropy_nrf5_get_entropy_isr()
Dentropy_smartbond.c168 while (likely(len--)) { in rng_pool_get()
178 if (likely(!other_read_in_progress)) { in rng_pool_get()
306 if (likely((flags & ENTROPY_BUSYWAIT) == 0U)) { in entropy_smartbond_get_entropy_isr()
Dentropy_stm32.c478 while (likely(len--)) { in rng_pool_get()
488 if (likely(!other_read_in_progress)) { in rng_pool_get()
609 if (likely((flags & ENTROPY_BUSYWAIT) == 0U)) { in entropy_stm32_rng_get_entropy_isr()
/Zephyr-latest/kernel/
Dmutex.c117 if (likely((mutex->lock_count == 0U) || (mutex->owner == arch_current_thread()))) { in z_impl_k_mutex_lock()
178 if (likely(mutex->owner != NULL)) { in z_impl_k_mutex_lock()
Dsem.c143 if (likely(sem->count > 0U)) { in z_impl_k_sem_take()
Dstack.c158 if (likely(stack->next > stack->base)) { in z_impl_k_stack_pop()
/Zephyr-latest/drivers/sensor/st/lis2dh/
Dlis2dh_trigger.c451 if (likely(lis2dh->handler_drdy != NULL)) { in lis2dh_thread_cb()
458 if (likely(lis2dh->handler_drdy != NULL)) { in lis2dh_thread_cb()
481 if (likely(lis2dh->handler_anymotion != NULL) && in lis2dh_thread_cb()
496 if (likely(lis2dh->handler_tap != NULL) && in lis2dh_thread_cb()
/Zephyr-latest/doc/hardware/peripherals/sensor/
Dpower_management.rst14 Most likely the API sensors should use for their fully suspended/resume power states is
Dread_and_decode.rst54 * Far less likely triggers are missed due to long held interrupt masks from
74 Polling a temperature sensor and printing its readout is likely the simplest
Dfetch_and_get.rst69 In all cases it's very likely there will be variable delays from the actual
/Zephyr-latest/drivers/display/
DKconfig.mcux_dcnano_lcdif23 Note that hardware will likely perform best if zero driver
DKconfig.mcux_elcdif24 Note that hardware will likely perform best if zero driver
/Zephyr-latest/include/zephyr/net/
Dieee802154_pkt.h173 if (likely(rssi >= IEEE802154_MAC_RSSI_DBM_MIN && rssi <= IEEE802154_MAC_RSSI_DBM_MAX)) { in net_pkt_set_ieee802154_rssi_dbm()
/Zephyr-latest/drivers/counter/
Dcounter_renesas_ra_agt.c76 while (!(reg->AGTCR & BIT(R_AGTX0_AGT16_CTRL_AGTCR_TCSTF_Pos)) && likely(--timeout)) in counter_ra_agt_start()
89 while ((reg->AGTCR & BIT(R_AGTX0_AGT16_CTRL_AGTCR_TCSTF_Pos)) && likely(--timeout)) in counter_ra_agt_stop()
514 if (likely(IS_BIT_MASK(top))) { in r_agt_ticks_sub()
Dcounter_nxp_s32_sys_timer.c87 if (likely(IS_BIT_MASK(top))) { in ticks_add()
99 if (likely(IS_BIT_MASK(top))) { in ticks_sub()
Dcounter_ifx_cat1.c329 if (likely(counter_is_bit_mask(top))) { in ifx_cat1_counter_ticks_add()
341 if (likely(counter_is_bit_mask(top))) { in ifx_cat1_counter_ticks_sub()
Dcounter_nrfx_timer.c107 if (likely(IS_BIT_MASK(top))) { in ticks_add()
118 if (likely(IS_BIT_MASK(top))) { in ticks_sub()
Dcounter_gd32_timer.c179 if (likely(IS_BIT_MASK(top))) { in ticks_add()
190 if (likely(IS_BIT_MASK(top))) { in ticks_sub()
Dcounter_ll_stm32_timer.c162 if (likely(IS_BIT_MASK(top))) { in counter_stm32_ticks_add()
173 if (likely(IS_BIT_MASK(top))) { in counter_stm32_ticks_sub()
/Zephyr-latest/drivers/interrupt_controller/
Dintc_loapic.c320 for (block = 7; likely(block > 0); block--) { in z_irq_controller_isr_vector_get()
/Zephyr-latest/cmake/usage/
Dusage.cmake46 message(" 3: more obscure warnings, can most likely be ignored")
/Zephyr-latest/doc/services/dsp/
Dindex.rst11 Currently, the API will work on any architecture but will likely not be
/Zephyr-latest/drivers/sensor/honeywell/sm351lt/
Dsm351lt.c71 if (likely(data->changed_handler != NULL)) { in sm351lt_thread_cb()
/Zephyr-latest/doc/develop/west/
Dtroubleshooting.rst142 The most likely cause is that you're running the command outside of a
217 then it's likely that west is using the :envvar:`ZEPHYR_BASE` :ref:`environment
/Zephyr-latest/arch/arm/core/mpu/
DKconfig91 SoC definition should likely provide its own custom MPU regions.

1234