/nrf52832-nimble/rt-thread/documentation/doxygen/ |
H A D | kernel.h | 27 * scheduling. 28 * - The scheduling is a full preemptive priority-based scheduling algorithm. 32 * round-robin scheduling is used for this case. 46 * RT-Thread uses clock tick to implement shared time-slice scheduling.
|
/nrf52832-nimble/packages/NimBLE-latest/nimble/controller/ |
H A D | syscfg.yml | 135 This is the number of "slots" allocated to a connection when scheduling 154 # Strict scheduling 166 scheduling. The total # of periods allocated for strict scheduling
|
/nrf52832-nimble/rt-thread/components/net/uip/doc/ |
H A D | pt-doc.txt | 127 \section pt-scheduling Scheduling 131 protothread will run until it blocks or exits. Thus the scheduling of
|
/nrf52832-nimble/rt-thread/components/libc/libdl/ |
H A D | dlmodule.c | 198 /* lock scheduler to prevent scheduling in cleanup function. */ in dlmodule_destroy_subthread() 567 /* disable scheduling */ in dlmodule_exit() 573 /* restore scheduling */ in dlmodule_exit() 597 /* enable scheduling */ in dlmodule_exit()
|
/nrf52832-nimble/packages/NimBLE-latest/nimble/controller/include/controller/ |
H A D | ble_ll_sched.h | 87 * Strict connection scheduling (for the master) is different than how 88 * connections are normally scheduled. With strict connection scheduling we
|
H A D | ble_ll_conn.h | 303 /* For scheduling connections */
|
/nrf52832-nimble/rt-thread/components/libc/pthreads/ |
H A D | sched.h | 16 /* Thread scheduling policies */
|
/nrf52832-nimble/rt-thread/components/libc/aio/ |
H A D | posix_aio.c | 186 * shall be submitted at a priority equal to a base scheduling priority minus 187 * aiocbp->aio_reqprio. If Thread Execution Scheduling is not supported, then 188 * the base scheduling priority is that of the calling process; 190 * otherwise, the base scheduling priority is that of the calling thread.
|
/nrf52832-nimble/rt-thread/src/ |
H A D | scheduler.c | 289 * This function will handle IPI interrupt and do a scheduling in system; 291 * @param vector, the number of IPI interrupt for system scheduling 302 * This function will perform one scheduling. It will select one thread 503 * This function checks if a scheduling is needed after IRQ context. If yes,
|
H A D | Kconfig | 273 And developer also can call memcheck() in each of scheduling
|
H A D | idle.c | 182 /* lock scheduler to prevent scheduling in cleanup function. */ in rt_thread_idle_excute()
|
H A D | thread.c | 22 * 2011-09-08 Bernard fixed the scheduling issue in rt_thread_startup. 313 /* do a scheduling */ in rt_thread_startup()
|
H A D | signal.c | 246 /* do thread scheduling */ in rt_signal_wait()
|
H A D | ipc.c | 1094 /* need do a scheduling */ in rt_event_send()
|
/nrf52832-nimble/packages/NimBLE-latest/docs/ble_setup/ |
H A D | ble_lp_clock.rst | 4 The NimBLE stack uses OS cputime for scheduling various events inside
|
/nrf52832-nimble/rt-thread/components/vmm/ |
H A D | vmm.c | 183 rt_kprintf("do the first scheduling...\n"); in vmm_entry()
|
/nrf52832-nimble/rt-thread/ |
H A D | README.md | 16 …tional real-time operating system. The kernel has real-time multi-task scheduling, semaphore, mute…
|
/nrf52832-nimble/rt-thread/components/net/lwip-2.1.0/src/core/ |
H A D | sys.c | 59 * functionality. Timer scheduling is implemented in lwIP, but can be implemented
|
/nrf52832-nimble/rt-thread/components/CMSIS/Include/ |
H A D | core_cmFunc.h | 592 /* Empty asm statement works as a scheduling barrier */ in __get_FPSCR() 612 /* Empty asm statement works as a scheduling barrier */ in __set_FPSCR()
|
/nrf52832-nimble/nordic/cmsis/include/ |
H A D | cmsis_armcc_V6.h | 661 …__ASM volatile (""); /* Empty asm statement works as a scheduling … 682 …__ASM volatile (""); /* Empty asm statement works as a scheduling … in __TZ_get_FPSCR_NS() 703 …__ASM volatile (""); /* Empty asm statement works as a scheduling … 719 …__ASM volatile (""); /* Empty asm statement works as a scheduling … in __TZ_set_FPSCR_NS()
|
H A D | cmsis_gcc.h | 319 /* Empty asm statement works as a scheduling barrier */ in __get_FPSCR() 338 /* Empty asm statement works as a scheduling barrier */ in __set_FPSCR()
|
/nrf52832-nimble/rt-thread/components/net/lwip-1.4.1/doc/ |
H A D | sys_arch.txt | 16 implement timer scheduling as well but as of lwIP 0.5 this is
|
/nrf52832-nimble/rt-thread/components/net/lwip-2.0.2/doc/ |
H A D | sys_arch.txt | 16 functionality. Timer scheduling is implemented in lwIP, but can be implemented
|
/nrf52832-nimble/packages/NimBLE-latest/nimble/controller/src/ |
H A D | ble_ll_adv.c | 55 /* Scheduling data for secondary channel */ 1186 * do not have reference time for scheduling. in ble_ll_adv_aux_schedule_next() 1307 * on 1M, but it can vary a bit due to scheduling which we can't really in ble_ll_adv_aux_set_start_time() 1334 * For secondary channel we always start by scheduling two consecutive in ble_ll_adv_aux_schedule() 3165 * add the random advDelay as the scheduling code will do that. in ble_ll_adv_done()
|
/nrf52832-nimble/rt-thread/components/net/uip/doc/html/ |
H A D | a00142.html | 66 <h2><a class="anchor" name="pt-scheduling"> 67 Scheduling</a></h2> 68 …is called, the protothread will run until it blocks or exits. Thus the scheduling of protothreads …
|