Searched refs:schedule (Results 1 – 20 of 20) sorted by relevance
/Zephyr-Core-3.7.0/drivers/usb/uhc/ |
D | uhc_virtual.c | 318 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()
|
D | uhc_max3421e.c | 666 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/ |
D | CMakeLists.txt | 22 # If thread local storage isn't used - we can safely schedule thread pointer register
|
/Zephyr-Core-3.7.0/kernel/ |
D | Kconfig.smp | 12 more than one CPU to schedule Zephyr tasks at a time. 82 to check if schedule IPI has called or not, for testing
|
D | work.c | 1004 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/ |
D | README.rst | 40 INFO: Running with entropic power schedule (0xFF, 100).
|
/Zephyr-Core-3.7.0/samples/subsys/zbus/work_queue/ |
D | README.rst | 9 …server can react "instantaneously" by using a listener callback. It can schedule a job, pushing th…
|
/Zephyr-Core-3.7.0/subsys/net/ip/ |
D | Kconfig.mgmt | 36 Submit work to the system work queue to schedule calling network
|
/Zephyr-Core-3.7.0/doc/services/pm/ |
D | device_runtime.rst | 109 :c:func:`pm_device_runtime_put_async` function. This function will schedule 226 /* "put" device (decreases usage count, schedule suspend if no more users) */
|
D | system.rst | 9 The kernel enters the idle state when it has nothing to schedule.
|
/Zephyr-Core-3.7.0/samples/drivers/counter/maxim_ds3231/ |
D | README.rst | 88 latency). The callback uses the counter alarm API to schedule a second
|
/Zephyr-Core-3.7.0/doc/kernel/services/threads/ |
D | workqueue.rst | 136 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
|
D | index.rst | 167 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/ |
D | access.rst | 155 schedule a work item with delay defined by the
|
/Zephyr-Core-3.7.0/doc/kernel/services/smp/ |
D | smp.rst | 347 to schedule, and follow through with their own :c:func:`arch_switch` or
|
/Zephyr-Core-3.7.0/doc/releases/ |
D | release-notes-2.1.rst | 716 * :github:`19437` - tests/kernel/sched/schedule\_api tests fail to build 826 * :github:`18282` - tests/kernel/sched/schedule\_api/ fails on LPC54114\_m4
|
D | release-notes-2.7.rst | 1881 * :github:`30245` - Bluetooth: controller: event scheduling pipeline preemption by short schedule
|
D | release-notes-3.1.rst | 308 schedule points, and not synchronously when the scheduler state
|
D | release-notes-2.6.rst | 1638 * :github:`33353` - work: k_work_schedule from running work item does not schedule
|
/Zephyr-Core-3.7.0/scripts/ |
D | spelling.txt | 1389 schdule||schedule
|