Searched refs:wakes (Results 1 – 25 of 25) sorted by relevance
| /linux-4.4.14/drivers/platform/goldfish/ |
| D | goldfish_pipe.c | 457 unsigned long wakes; in goldfish_pipe_interrupt() local
472 wakes = readl(dev->base + PIPE_REG_WAKES); in goldfish_pipe_interrupt()
476 if (wakes & PIPE_WAKE_CLOSED) { in goldfish_pipe_interrupt()
478 wakes |= PIPE_WAKE_READ | PIPE_WAKE_WRITE; in goldfish_pipe_interrupt()
480 if (wakes & PIPE_WAKE_READ) in goldfish_pipe_interrupt()
482 if (wakes & PIPE_WAKE_WRITE) in goldfish_pipe_interrupt()
|
| /linux-4.4.14/Documentation/ |
| D | workqueue.txt | 122 whenever an active worker wakes up or sleeps and keeps track of the
273 15 w0 wakes up and burns CPU
277 35 w1 wakes up and finishes
280 50 w2 wakes up and finishes
291 15 w0 wakes up and burns CPU
293 20 w1 wakes up and finishes
294 25 w2 wakes up and finishes
303 15 w0 wakes up and burns CPU
305 20 w1 wakes up and finishes
308 35 w2 wakes up and finishes
[all …]
|
| D | robust-futexes.txt | 98 this thread with the FUTEX_OWNER_DIED bit, and wakes up one waiter (if
192 and wakes up the next futex waiter (if any). User-space does the rest of
|
| D | pi-futex.txt | 110 pi_state->rt_mutex and thus wakes up any potential waiters.
|
| D | this_cpu_ops.txt | 327 that most likely will access it. If the processor wakes up and finds a
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-bus-i2c-devices-hm6352 | 13 sleep mode, 1 wakes it up.
|
| /linux-4.4.14/Documentation/devicetree/bindings/mmc/ |
| D | ti-omap-hsmmc.txt | 79 event normally. Since am33xx doesn't have this line it never wakes from
|
| /linux-4.4.14/Documentation/usb/ |
| D | persist.txt | 25 wakes up all the devices attached to that controller are treated as
62 suspended -- but it will crash as soon as it wakes up, which isn't
|
| D | WUSB-Design-overview.txt | 229 UWBD wakes up and scans the event list; finds a beacon and adds it to
|
| /linux-4.4.14/Documentation/vm/ |
| D | userfaultfd.txt | 77 atomically copies a page into the userfault registered range and wakes
|
| /linux-4.4.14/Documentation/power/ |
| D | userland-swsusp.txt | 92 to use the SNAPSHOT_UNFREEZE call after the system wakes up. This call
|
| D | charger-manager.txt | 32 periodically. However, such a method wakes up devices unnecessarily for
|
| D | freezing-of-tasks.txt | 24 fake signal to all user space processes, and wakes up all the kernel threads.
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | governors.txt | 266 (for example, when there's a "daemonized" function that wakes up
|
| /linux-4.4.14/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-4.4.14/Documentation/filesystems/caching/ |
| D | object.txt | 102 wakes up in that state. There are four logical sets of states:
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-deadline.txt | 51 every time the task wakes up, the scheduler computes a "scheduling deadline"
76 - When a SCHED_DEADLINE task wakes up (becomes ready for execution),
|
| /linux-4.4.14/Documentation/scsi/ |
| D | scsi_eh.txt | 146 shost->host_failed. This wakes up SCSI EH thread. So, once woken up,
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | vm.txt | 163 interval will be written out next time a flusher thread wakes up.
|
| /linux-4.4.14/arch/blackfin/ |
| D | Kconfig | 1268 such as GPIO interrupt or RTC activity wakes up the processor.
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | HD-Audio.txt | 73 the wake-up timing. It wakes up a few samples before actually
|
| /linux-4.4.14/Documentation/locking/ |
| D | rt-mutex-design.txt | 605 owner to grab the mutex. When a pending owner wakes up, it checks to see
|
| /linux-4.4.14/Documentation/security/ |
| D | keys.txt | 814 This function marks a key as being invalidated and then wakes up the
|