Home
last modified time | relevance | path

Searched refs:direct_complete (Results 1 – 4 of 4) sorted by relevance

/linux-4.1.27/drivers/base/power/
Dmain.c482 if (dev->power.syscore || dev->power.direct_complete) in device_resume_noirq()
611 if (dev->power.syscore || dev->power.direct_complete) in device_resume_early()
743 if (dev->power.direct_complete) { in device_resume()
1031 if (dev->power.syscore || dev->power.direct_complete) in __device_suspend_noirq()
1177 if (dev->power.syscore || dev->power.direct_complete) in __device_suspend_late()
1375 if (dev->power.direct_complete) { in __device_suspend()
1383 dev->power.direct_complete = false; in __device_suspend()
1442 dev->parent->power.direct_complete = false; in __device_suspend()
1610 dev->power.direct_complete = ret > 0 && state.event == PM_EVENT_SUSPEND; in device_prepare()
/linux-4.1.27/include/linux/
Dpm.h555 bool direct_complete:1; /* Owned by the PM core */ member
/linux-4.1.27/drivers/acpi/
Ddevice_pm.c962 if (dev->power.direct_complete) in acpi_subsys_complete()
/linux-4.1.27/Documentation/power/
Ddevices.txt427 can consult the device's power.direct_complete flag. Namely, if that