Searched refs:waking (Results 1 – 25 of 41) sorted by relevance
12
7 - wakeup-gpios: the gpio pin to be used for waking up the controller
37 waking the task up. BOOM, the wakeup will happen while the task is
20 remain asleep before waking up to enter hibernation.
42 handoff to the OS waking vector. In nanoseconds.
63 waking up via magic packet.65 waking up by Filer General Purpose Interrupt (FGPI) asserted on the
17 pthread_cond_broadcast() must resort to waking all the tasks waiting94 requeue call returning to user space and the waiter waking and
26 waiting on a particular futex, and waking up the next waiter on a
22 - num-perips: Number of waking peripherals.
104 :doc: Lockless queue stopping / waking helpers.
276 on the socket thus waking up the application thread. When the application
115 unsigned long waking; member1661 thread->waking++; in record__thread()2309 thread_data[t].samples, thread_data[t].waking); in record__stop_threads()2323 unsigned long waking = 0; in record__waking() local2327 waking += thread_data[t].waking; in record__waking()2329 return waking; in record__waking()2660 thread->waking = 0; in __cmd_record()2684 thread->waking++; in __cmd_record()
142 energy consumed by the system if the waking task was migrated. compute_energy()254 a specific point in time, a small task waking up at that moment could be better262 increase the cost of the tasks already running there. If the waking task is
149 waking cpu because it was cache-cold on its own cpu anyway
109 Clock-pause is exited by waking up framer device (if controller driver initiates
350 Set to 1 if the system is waking up because the user352 waking up because the user requested the system to538 0x2304 System is waking up from suspend to undock539 0x2305 System is waking up from suspend to eject bay540 0x2404 System is waking up from hibernation to undock541 0x2405 System is waking up from hibernation to eject bay556 0x2313 ALARM: System is waking up from suspend because558 0x2413 ALARM: System is waking up from hibernation because
119 be logged, some of it can be lost due to the processor not waking up
15 the caller may also wish to avoid waking kswapd.
172 * waking anyone up */
34 battery temperature. We can accomplish this by waking up the system
196 That usually prevents in-band hardware interrupts from waking up the system,
127 // sleep forver, waking only for interrupts.
158 // sleep forever, waking for interrupts
314 based on the ARM architected timer. It is used for waking up CPUs
64 impact the performances by waking up userspace every time there is an
206 user tasks and waking kthreads to patch them. But it could still be
