| /Linux-v4.19/Documentation/core-api/ |
| 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 …]
|
| /Linux-v4.19/drivers/platform/goldfish/ |
| D | goldfish_pipe.c | 599 struct goldfish_pipe_dev *dev, int *wakes) in signalled_pipes_pop_front() argument
608 *wakes = pipe->signalled_flags; in signalled_pipes_pop_front()
631 int wakes; in goldfish_interrupt_task() local
633 while ((pipe = signalled_pipes_pop_front(dev, &wakes)) != NULL) { in goldfish_interrupt_task()
634 if (wakes & PIPE_WAKE_CLOSED) { in goldfish_interrupt_task()
637 if (wakes & PIPE_WAKE_READ) in goldfish_interrupt_task()
639 if (wakes & PIPE_WAKE_WRITE) in goldfish_interrupt_task()
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-devices-platform-ACPI-TAD | 15 BIT(5): The AC timer wakes up from S4 if set
16 BIT(6): The AC timer wakes up from S5 if set
17 BIT(7): The DC timer wakes up from S4 if set
18 BIT(8): The DC timer wakes up from S5 if set
|
| D | sysfs-bus-i2c-devices-hm6352 | 13 sleep mode, 1 wakes it up.
|
| D | sysfs-bus-typec | 10 entered/exited so poll(2) on the attribute wakes up.
|
| D | sysfs-class-typec | 12 wakes up. Change on the role will also generate uevent
27 that poll(2) on the attribute wakes up. Change on the role will
58 poll(2) on the attribute wakes up. Change on VCONN source also
|
| /Linux-v4.19/drivers/staging/android/uapi/ |
| D | vsoc_shm.h | 283 __u32 wakes; member
|
| /Linux-v4.19/Documentation/ABI/obsolete/ |
| D | sysfs-class-typec | 45 entered/exited so poll(2) on the attribute wakes up.
|
| /Linux-v4.19/Documentation/driver-api/usb/ |
| 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
|
| /Linux-v4.19/Documentation/scheduler/ |
| D | sched-deadline.txt | 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
|
| /Linux-v4.19/Documentation/devicetree/bindings/mmc/ |
| D | ti-omap-hsmmc.txt | 101 event normally. Since am33xx doesn't have this line it never wakes from
|
| /Linux-v4.19/Documentation/ |
| D | robust-futexes.txt | 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
|
| D | pi-futex.txt | 111 pi_state->rt_mutex and thus wakes up any potential waiters.
|
| D | this_cpu_ops.txt | 337 that most likely will access it. If the processor wakes up and finds a
|
| /Linux-v4.19/drivers/staging/android/ |
| D | vsoc.c | 477 ++arg->wakes; in handle_vsoc_cond_wait()
502 arg.wakes = 0; in do_vsoc_cond_wait()
|
| /Linux-v4.19/Documentation/power/ |
| D | charger-manager.txt | 32 periodically. However, such a method wakes up devices unnecessarily for
|
| D | userland-swsusp.txt | 92 to use the SNAPSHOT_UNFREEZE call after the system wakes up. This call
|
| D | freezing-of-tasks.txt | 24 fake signal to all user space processes, and wakes up all the kernel threads.
|
| /Linux-v4.19/Documentation/networking/ |
| D | README.ipw2100 | 218 must buffer packets at the AP until the station wakes up and requests
|
| D | spider_net.txt | 196 interrupt wakes up the netdev, which can then refill the queue.
|
| D | scaling.txt | 134 packets have been queued to their backlog queue. The IPI wakes backlog
|
| /Linux-v4.19/Documentation/filesystems/caching/ |
| D | object.txt | 102 wakes up in that state. There are four logical sets of states:
|
| /Linux-v4.19/Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 104 atomically copies a page into the userfault registered range and wakes
|
| /Linux-v4.19/Documentation/scsi/ |
| D | scsi_eh.txt | 133 shost->host_failed. This wakes up SCSI EH thread. So, once woken up,
|
| /Linux-v4.19/Documentation/usb/ |
| D | WUSB-Design-overview.txt | 229 UWBD wakes up and scans the event list; finds a beacon and adds it to
|
