Searched refs:pm_wq (Results 1 – 7 of 7) sorted by relevance
| /linux-4.1.27/kernel/power/ |
| D | main.c | 619 struct workqueue_struct *pm_wq; variable
620 EXPORT_SYMBOL_GPL(pm_wq);
624 pm_wq = alloc_workqueue("pm", WQ_FREEZABLE, 0); in pm_start_workqueue()
626 return pm_wq ? 0 : -ENOMEM; in pm_start_workqueue()
|
| /linux-4.1.27/include/linux/ |
| D | pm_runtime.h | 27 extern struct workqueue_struct *pm_wq;
31 return queue_work(pm_wq, work); in queue_pm_work()
|
| /linux-4.1.27/drivers/base/power/ |
| D | runtime.c | 337 queue_work(pm_wq, &dev->power.work); in rpm_idle()
508 queue_work(pm_wq, &dev->power.work); in rpm_suspend()
691 queue_work(pm_wq, &dev->power.work); in rpm_resume()
|
| D | domain.c | 501 queue_work(pm_wq, &genpd->power_off_work); in genpd_queue_power_off_work()
|
| /linux-4.1.27/Documentation/power/ |
| D | runtime_pm.txt | 12 * The power management workqueue pm_wq in which bus types and device drivers can
13 put their PM-related work items. It is strongly recommended that pm_wq be
16 hibernation and resume from system sleep states). pm_wq is declared in
213 - work structure used for queuing up requests (i.e. work items in pm_wq)
246 - if set, there's a pending request (i.e. a work item queued up into pm_wq)
339 device (the request is represented by a work item in pm_wq); returns 0 on
350 suspend work item in pm_wq, in milliseconds (if 'delay' is zero, the work
359 device (the request is represented by a work item in pm_wq); returns 0 on
|
| D | pci.txt | 1000 by work items put into the power management workqueue, pm_wq. Although there
1010 request into pm_wq. In the majority of cases this also is done by their
|
| /linux-4.1.27/drivers/usb/core/ |
| D | hcd.c | 2289 queue_work(pm_wq, &hcd->wakeup_work); in usb_hcd_resume_root_hub()
|