Searched refs:reschedule (Results 1 – 17 of 17) sorted by relevance
| /Zephyr-latest/doc/develop/api/ |
| D | terminology.rst | 11 if executing the function reaches a reschedule point
37 reschedule section in API Terminology
40 The reschedule attribute is used on a function that can reach a
41 :ref:`reschedule point <scheduling_v2>` within its execution.
50 reschedule point and the relative priorities of the invoking thread and argument
53 Note that in the case of timeslicing, or reschedule points executed from
56 Functions that are not **reschedule** may be invoked from either thread
59 Functions that are **reschedule** may be invoked from thread context.
61 Functions that are **reschedule** but not **sleep** may be invoked from
77 will not replace a running cooperative-only thread at a reschedule point
[all …]
|
| /Zephyr-latest/soc/st/stm32/stm32wbax/hci_if/ |
| D | linklayer_plat_adapt.c | 96 ARM_IRQ_DIRECT_DYNAMIC_CONNECT(RADIO_INTR_NUM, 0, 0, reschedule); in link_layer_register_isr()
106 ARM_IRQ_DIRECT_DYNAMIC_CONNECT(RADIO_SW_LOW_INTR_NUM, 0, 0, reschedule); in link_layer_register_isr()
|
| /Zephyr-latest/subsys/net/lib/trickle/ |
| D | trickle.c | 88 static inline void reschedule(struct net_trickle *trickle) in reschedule() function
119 reschedule(trickle); in interval_timeout()
|
| /Zephyr-latest/arch/mips/core/ |
| D | isr.S | 162 j reschedule
212 reschedule: label
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_timeout.rst | 42 additional time remaining. If the latter, reschedule the callback.
|
| /Zephyr-latest/arch/riscv/core/ |
| D | isr.S | 442 j reschedule
700 reschedule: label
|
| /Zephyr-latest/kernel/ |
| D | pipes.c | 327 sys_dlist_t *dest_list, bool *reschedule) in pipe_write() argument
365 *reschedule = true; in pipe_write()
|
| D | work.c | 1071 SYS_PORT_TRACING_OBJ_FUNC_ENTER(k_work, reschedule, dwork, delay); in k_work_reschedule()
1075 SYS_PORT_TRACING_OBJ_FUNC_EXIT(k_work, reschedule, dwork, delay, ret); in k_work_reschedule()
|
| D | Kconfig.smp | 86 set of CPUs that need an IPI to trigger a reschedule in response to
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | message_queues.rst | 111 Note that this api will trigger reschedule.
|
| /Zephyr-latest/doc/kernel/services/scheduling/ |
| D | index.rst | 17 are called **reschedule points**. Some potential reschedule points are:
|
| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | transport.c | 931 goto reschedule; in trans_ack()
945 reschedule: in trans_ack()
|
| /Zephyr-latest/doc/kernel/services/smp/ |
| D | smp.rst | 233 sufficient to trigger a reschedule on the N CPUs that results with them
|
| /Zephyr-latest/doc/kernel/services/ |
| D | interrupts.rst | 154 occur. Thread B will not run until the next :ref:`reschedule point
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-3.4.rst | 488 * Modified the ticker implementation to reschedule unreserved tickers that use
|
| D | release-notes-2.2.rst | 1068 * :github:`20802` - reschedule not done after mutex unlock
|
| /Zephyr-latest/doc/ |
| D | zephyr.doxyfile.in | 290 "reschedule=\qualifier reschedule" \
|
