| /OK3568_Linux_fs/kernel/Documentation/core-api/ |
| H A D | workqueue.rst | 117 whenever an active worker wakes up or sleeps and keeps track of the
274 15 w0 wakes up and burns CPU
278 35 w1 wakes up and finishes
281 50 w2 wakes up and finishes
292 15 w0 wakes up and burns CPU
294 20 w1 wakes up and finishes
295 25 w2 wakes up and finishes
304 15 w0 wakes up and burns CPU
306 20 w1 wakes up and finishes
309 35 w2 wakes up and finishes
[all …]
|
| H A D | this_cpu_ops.rst | 337 that most likely will access it. If the processor wakes up and finds a
|
| /OK3568_Linux_fs/kernel/drivers/platform/goldfish/ |
| H A D | goldfish_pipe.c | 553 struct goldfish_pipe_dev *dev, int *wakes) in signalled_pipes_pop_front() argument
562 *wakes = pipe->signalled_flags; in signalled_pipes_pop_front()
585 int wakes; in goldfish_interrupt_task() local
587 while ((pipe = signalled_pipes_pop_front(dev, &wakes)) != NULL) { in goldfish_interrupt_task()
588 if (wakes & PIPE_WAKE_CLOSED) { in goldfish_interrupt_task()
591 if (wakes & PIPE_WAKE_READ) in goldfish_interrupt_task()
593 if (wakes & PIPE_WAKE_WRITE) in goldfish_interrupt_task()
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | sysfs-devices-platform-ACPI-TAD | 16 BIT(5): The AC timer wakes up from S4 if set
17 BIT(6): The AC timer wakes up from S5 if set
18 BIT(7): The DC timer wakes up from S4 if set
19 BIT(8): The DC timer wakes up from S5 if set
|
| H A D | sysfs-bus-i2c-devices-hm6352 | 13 sleep mode, 1 wakes it up.
|
| H A D | sysfs-bus-typec | 10 entered/exited so poll(2) on the attribute wakes up.
|
| H A D | sysfs-class-typec | 12 wakes up. Change on the role will also generate uevent
27 wakes up. Change on the role will also generate uevent
61 poll(2) on the attribute wakes up. Change on VCONN source also
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/obsolete/ |
| H A D | sysfs-class-typec | 45 entered/exited so poll(2) on the attribute wakes up.
|
| /OK3568_Linux_fs/kernel/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3368-808-evb.dts | 174 * the system sleeps and wakes up, 4g module can not disconnect the network,
|
| /OK3568_Linux_fs/kernel/Documentation/hwmon/ |
| H A D | amd_energy.rst | 84 running during probe, wakes up every 100secs and stops running
|
| /OK3568_Linux_fs/kernel/Documentation/mhi/ |
| H A D | mhi.rst | 211 * Device wakes up to process the TD.
215 * Host wakes up and checks the event ring for completion event.
|
| /OK3568_Linux_fs/kernel/Documentation/scheduler/ |
| H A D | sched-deadline.rst | 57 every time the task wakes up, the scheduler computes a "scheduling deadline"
82 - When a SCHED_DEADLINE task wakes up (becomes ready for execution),
180 (b) If the task wakes up before the inactive timer fires, the task re-enters
182 In addition, if the task wakes up on a different runqueue, then
189 "inactive timer" fires or when the task wakes up).
194 (d) When an inactive task wakes up, it enters the ActiveContending state and
282 Task T1 wakes up. It enters the ActiveContending state again, and the
|
| H A D | sched-capacity.rst | 374 sleeps, if at all - it thus rarely wakes up, if at all. Consider::
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/usb/ |
| H A D | persist.rst | 28 wakes up all the devices attached to that controller are treated as
65 suspended -- but it will crash as soon as it wakes up, which isn't
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/mmc/ |
| H A D | ti-omap-hsmmc.txt | 101 event normally. Since am33xx doesn't have this line it never wakes from
|
| /OK3568_Linux_fs/kernel/Documentation/locking/ |
| H A D | robust-futexes.rst | 102 this thread with the FUTEX_OWNER_DIED bit, and wakes up one waiter (if
196 and wakes up the next futex waiter (if any). User-space does the rest of
|
| H A D | pi-futex.rst | 111 pi_state->rt_mutex and thus wakes up any potential waiters.
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/mm/ |
| H A D | userfaultfd.rst | 153 those IOCTLs wakes up the faulting thread.
176 set. This wakes up the thread which will continue to run with writes. This
|
| /OK3568_Linux_fs/kernel/Documentation/PCI/ |
| H A D | boot-interrupts.rst | 65 handler wakes. These "one shot" conditions mean that the threaded interrupt
|
| /OK3568_Linux_fs/external/xserver/doc/ |
| H A D | smartsched | 70 WaitForSomething wakes up from select and returns that client
|
| /OK3568_Linux_fs/kernel/Documentation/power/ |
| H A D | charger-manager.rst | 35 periodically. However, such a method wakes up devices unnecessarily for
|
| H A D | userland-swsusp.rst | 111 to use the SNAPSHOT_UNFREEZE call after the system wakes up. This call
|
| /OK3568_Linux_fs/kernel/Documentation/networking/device_drivers/wifi/intel/ |
| H A D | ipw2100.rst | 244 must buffer packets at the AP until the station wakes up and requests
|
| /OK3568_Linux_fs/kernel/Documentation/filesystems/caching/ |
| H A D | object.rst | 102 wakes up in that state. There are four logical sets of states:
|
| /OK3568_Linux_fs/kernel/Documentation/networking/device_drivers/ethernet/toshiba/ |
| H A D | spider_net.rst | 198 interrupt wakes up the netdev, which can then refill the queue.
|