Home
last modified time | relevance | path

Searched refs:schedule (Results 1 – 20 of 20) sorted by relevance

/Zephyr-Core-3.7.0/drivers/usb/uhc/
Duhc_virtual.c318 bool schedule = false; in xfer_work_handler() local
328 schedule = true; in xfer_work_handler()
332 schedule = true; in xfer_work_handler()
349 if (schedule && !priv->busy) { in xfer_work_handler()
Duhc_max3421e.c666 bool schedule = false; in uhc_max3421e_thread() local
685 schedule = true; in uhc_max3421e_thread()
690 schedule = HRSLT_IS_BUSY(priv->hrsl) ? false : true; in uhc_max3421e_thread()
707 if (schedule) { in uhc_max3421e_thread()
/Zephyr-Core-3.7.0/arch/arc/
DCMakeLists.txt22 # If thread local storage isn't used - we can safely schedule thread pointer register
/Zephyr-Core-3.7.0/kernel/
DKconfig.smp12 more than one CPU to schedule Zephyr tasks at a time.
82 to check if schedule IPI has called or not, for testing
Dwork.c1004 SYS_PORT_TRACING_OBJ_FUNC_ENTER(k_work, schedule, dwork, delay); in k_work_schedule()
1008 SYS_PORT_TRACING_OBJ_FUNC_EXIT(k_work, schedule, dwork, delay, ret); in k_work_schedule()
/Zephyr-Core-3.7.0/samples/subsys/debug/fuzz/
DREADME.rst40 INFO: Running with entropic power schedule (0xFF, 100).
/Zephyr-Core-3.7.0/samples/subsys/zbus/work_queue/
DREADME.rst9 …server can react "instantaneously" by using a listener callback. It can schedule a job, pushing th…
/Zephyr-Core-3.7.0/subsys/net/ip/
DKconfig.mgmt36 Submit work to the system work queue to schedule calling network
/Zephyr-Core-3.7.0/doc/services/pm/
Ddevice_runtime.rst109 :c:func:`pm_device_runtime_put_async` function. This function will schedule
226 /* "put" device (decreases usage count, schedule suspend if no more users) */
Dsystem.rst9 The kernel enters the idle state when it has nothing to schedule.
/Zephyr-Core-3.7.0/samples/drivers/counter/maxim_ds3231/
DREADME.rst88 latency). The callback uses the counter alarm API to schedule a second
/Zephyr-Core-3.7.0/doc/kernel/services/threads/
Dworkqueue.rst136 An ISR or a thread may need to schedule a work item that is to be processed
146 the schedule request is made the kernel initiates a timeout mechanism that is
351 attempts to schedule the same item with this API before the delay completes
457 external lock just to submit or schedule them. Even if you use external state
Dindex.rst167 schedule state that only applies to **Ready** threads.
301 threads by the Zephyr API (namely that the OS won't schedule other
/Zephyr-Core-3.7.0/doc/connectivity/bluetooth/api/mesh/
Daccess.rst155 schedule a work item with delay defined by the
/Zephyr-Core-3.7.0/doc/kernel/services/smp/
Dsmp.rst347 to schedule, and follow through with their own :c:func:`arch_switch` or
/Zephyr-Core-3.7.0/doc/releases/
Drelease-notes-2.1.rst716 * :github:`19437` - tests/kernel/sched/schedule\_api tests fail to build
826 * :github:`18282` - tests/kernel/sched/schedule\_api/ fails on LPC54114\_m4
Drelease-notes-2.7.rst1881 * :github:`30245` - Bluetooth: controller: event scheduling pipeline preemption by short schedule
Drelease-notes-3.1.rst308 schedule points, and not synchronously when the scheduler state
Drelease-notes-2.6.rst1638 * :github:`33353` - work: k_work_schedule from running work item does not schedule
/Zephyr-Core-3.7.0/scripts/
Dspelling.txt1389 schdule||schedule