| /linux/Documentation/translations/zh_CN/core-api/ |
| H A D | workqueue.rst | 236 15 w0 wakes up and burns CPU
240 35 w1 wakes up and finishes
243 50 w2 wakes up and finishes
254 15 w0 wakes up and burns CPU
256 20 w1 wakes up and finishes
257 25 w2 wakes up and finishes
266 15 w0 wakes up and burns CPU
268 20 w1 wakes up and finishes
271 35 w2 wakes up and finishes
282 15 w0 wakes up and burns CPU
[all …]
|
| /linux/drivers/platform/goldfish/ |
| H A D | goldfish_pipe.c | 550 struct goldfish_pipe_dev *dev, int *wakes) in signalled_pipes_pop_front() argument
559 *wakes = pipe->signalled_flags; in signalled_pipes_pop_front()
582 int wakes; in goldfish_interrupt_task() local
584 while ((pipe = signalled_pipes_pop_front(dev, &wakes)) != NULL) { in goldfish_interrupt_task()
585 if (wakes & PIPE_WAKE_CLOSED) { in goldfish_interrupt_task()
588 if (wakes & PIPE_WAKE_READ) in goldfish_interrupt_task()
590 if (wakes & PIPE_WAKE_WRITE) in goldfish_interrupt_task()
|
| /linux/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
|
| /linux/Documentation/core-api/ |
| H A D | workqueue.rst | 125 whenever an active worker wakes up or sleeps and keeps track of the
284 15 w0 wakes up and burns CPU
288 35 w1 wakes up and finishes
291 50 w2 wakes up and finishes
302 15 w0 wakes up and burns CPU
304 20 w1 wakes up and finishes
305 25 w2 wakes up and finishes
314 15 w0 wakes up and burns CPU
316 20 w1 wakes up and finishes
319 35 w2 wakes up and finishes
[all …]
|
| H A D | this_cpu_ops.rst | 335 that most likely will access it. If the processor wakes up and finds a
|
| /linux/Documentation/scheduler/ |
| H A D | sched-util-clamp.rst | 110 when an RT task wakes up. This cost is unchanged by using uclamp. Uclamp only
127 they are intact. Clamping happens only when needed, e.g: when a task wakes up
136 When a task wakes up on an rq, the utilization signal of the rq will be
167 When a task wakes up, the scheduler will look at the current effective uclamp
547 wakes up. However, it requires to finish its work within a specific time window
648 wakes up on an idle CPU, then it will run at min frequency (Fmin) this
685 If task p1 wakes up on this CPU, which have:
728 performance point when it wakes up and starts running, then all these
|
| H A D | sched-capacity.rst | 377 sleeps, if at all - it thus rarely wakes up, if at all. Consider::
|
| /linux/Documentation/ABI/obsolete/ |
| H A D | sysfs-class-typec | 45 entered/exited so poll(2) on the attribute wakes up.
|
| /linux/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.
|
| /linux/Documentation/trace/ |
| H A D | timerlat-tracer.rst | 7 the tracer sets a periodic timer that wakes up a thread. The thread then
101 stacktrace section). Then the timer interrupt that wakes up the timerlat
|
| /linux/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
|
| /linux/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
|
| /linux/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.
|
| /linux/Documentation/PCI/ |
| H A D | boot-interrupts.rst | 65 handler wakes. These "one shot" conditions mean that the threaded interrupt
|
| /linux/Documentation/power/ |
| H A D | userland-swsusp.rst | 111 to use the SNAPSHOT_UNFREEZE call after the system wakes up. This call
|
| H A D | charger-manager.rst | 35 periodically. However, such a method wakes up devices unnecessarily for
|
| H A D | freezing-of-tasks.rst | 31 wakes up all the kernel threads. All freezable tasks must react to that by
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | userfaultfd.rst | 189 those IOCTLs wakes up the faulting thread.
212 set. This wakes up the thread which will continue to run with writes. This
|
| /linux/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
|
| /linux/Documentation/networking/device_drivers/ethernet/toshiba/ |
| H A D | spider_net.rst | 198 interrupt wakes up the netdev, which can then refill the queue.
|
| /linux/Documentation/userspace-api/ |
| H A D | perf_ring_buffer.rst | 402 kernel wakes up the perf process to read samples from the ring buffer.
426 wakes up tasks waiting on the event. This is fulfilled by the kernel
|