Lines Matching full:put
337 * have been put into D0 previously and that's why we in acpi_bus_init_power()
347 * it D0 in hope that this is what the BIOS put the device into. in acpi_bus_init_power()
362 * are assumed to be put into D0 by the BIOS. However, in some cases that may
946 * acpi_dev_pm_low_power - Put ACPI device into a low-power state.
947 * @dev: Device to put into a low-power state.
964 * acpi_dev_pm_full_power - Put ACPI device into the full-power state.
965 * @adev: ACPI device node to put into the full-power state.
974 * acpi_dev_suspend - Put device into a low-power state using ACPI.
975 * @dev: Device to put into a low-power state.
978 * Put the given device into a low-power state using the standard ACPI
979 * mechanism. Set up remote wakeup if desired, choose the state to put the
1009 * acpi_dev_resume - Put device into the full-power state using ACPI.
1010 * @dev: Device to put into the full-power state.
1012 * Put the given device into the full-power state using the standard ACPI
1033 * Carry out the generic runtime suspend procedure for @dev and use ACPI to put
1048 * Use ACPI to put the given device into the full-power state and carry out the
1144 * Carry out the generic late suspend procedure for @dev and use ACPI to put
1204 * Use ACPI to put the given device into the full-power state and carry out the
1231 * Use ACPI to put the given device into the full-power state if it has not been
1258 * put into the runtime-active metastate during system resume anyway, in acpi_subsys_freeze()
1303 * Carry out the generic late poweroff procedure for @dev and use ACPI to put
1379 * choice of the low-power state to put the device into. in acpi_dev_pm_detach()
1397 * be put into the ACPI D0 state before the function returns.