2012-11-02 00:40:09 +00:00
|
|
|
/*
|
|
|
|
* drivers/acpi/device_pm.c - ACPI device power management routines.
|
|
|
|
*
|
|
|
|
* Copyright (C) 2012, Intel Corp.
|
|
|
|
* Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
|
|
|
|
*
|
|
|
|
* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License version 2 as published
|
|
|
|
* by the Free Software Foundation.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful, but
|
|
|
|
* WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
* General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License along
|
|
|
|
* with this program; if not, write to the Free Software Foundation, Inc.,
|
|
|
|
* 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
|
|
|
|
*
|
|
|
|
* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/device.h>
|
2012-11-02 00:40:18 +00:00
|
|
|
#include <linux/export.h>
|
2012-11-02 00:40:09 +00:00
|
|
|
#include <linux/mutex.h>
|
2012-11-02 00:40:18 +00:00
|
|
|
#include <linux/pm_qos.h>
|
2012-11-02 00:40:28 +00:00
|
|
|
#include <linux/pm_runtime.h>
|
2012-11-02 00:40:09 +00:00
|
|
|
|
|
|
|
#include <acpi/acpi.h>
|
|
|
|
#include <acpi/acpi_bus.h>
|
2013-01-17 13:11:08 +00:00
|
|
|
#include <acpi/acpi_drivers.h>
|
|
|
|
|
|
|
|
#include "internal.h"
|
|
|
|
|
|
|
|
#define _COMPONENT ACPI_POWER_COMPONENT
|
|
|
|
ACPI_MODULE_NAME("device_pm");
|
2012-11-02 00:40:09 +00:00
|
|
|
|
2013-01-17 13:11:08 +00:00
|
|
|
/**
|
|
|
|
* acpi_power_state_string - String representation of ACPI device power state.
|
|
|
|
* @state: ACPI device power state to return the string representation of.
|
|
|
|
*/
|
|
|
|
const char *acpi_power_state_string(int state)
|
|
|
|
{
|
|
|
|
switch (state) {
|
|
|
|
case ACPI_STATE_D0:
|
|
|
|
return "D0";
|
|
|
|
case ACPI_STATE_D1:
|
|
|
|
return "D1";
|
|
|
|
case ACPI_STATE_D2:
|
|
|
|
return "D2";
|
|
|
|
case ACPI_STATE_D3_HOT:
|
|
|
|
return "D3hot";
|
|
|
|
case ACPI_STATE_D3_COLD:
|
2013-01-22 11:56:26 +00:00
|
|
|
return "D3cold";
|
2013-01-17 13:11:08 +00:00
|
|
|
default:
|
|
|
|
return "(unknown)";
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_device_get_power - Get power state of an ACPI device.
|
|
|
|
* @device: Device to get the power state of.
|
|
|
|
* @state: Place to store the power state of the device.
|
|
|
|
*
|
|
|
|
* This function does not update the device's power.state field, but it may
|
|
|
|
* update its parent's power.state field (when the parent's power state is
|
|
|
|
* unknown and the device's power state turns out to be D0).
|
|
|
|
*/
|
|
|
|
int acpi_device_get_power(struct acpi_device *device, int *state)
|
|
|
|
{
|
|
|
|
int result = ACPI_STATE_UNKNOWN;
|
|
|
|
|
|
|
|
if (!device || !state)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
if (!device->flags.power_manageable) {
|
|
|
|
/* TBD: Non-recursive algorithm for walking up hierarchy. */
|
|
|
|
*state = device->parent ?
|
|
|
|
device->parent->power.state : ACPI_STATE_D0;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
ACPI / PM: Fix potential problem in acpi_device_get_power()
Theoretically, in some situations acpi_device_get_power() may return
an incorrect result, because the settings of the power resources
depended on by the device may indicate a power state shallower than
the actual power state of the device.
Say that two devices, A and B, depend on two power resources, X and
Y, in such a way that _PR0 for both A and B list both X and Y and
_PR3 for both A and B list power resource Y alone. Also suppose
that _PS0 and _PS3 are present for both A and B. Then, if devices
A and B are initially in D0, power resources X and Y are initially
"on" and their reference counters are equal to 2. To put device A
into power state D3hot the kernel will decrement the reference
counter of power resource X, but that power resource won't be turned
off, because it is still in use by device B (its reference counter is
equal to 1). Next, _PS3 will be executed for device A. Afterward
the configuration of the power resources will indicate that device
A is in power state D0 (both X and Y are "on"), but in fact it is
in D3hot (because _PS3 has been executed for it).
In that situation, if acpi_device_get_power() is called to get the
power state of device A, it will first execute _PSC for it which
should return 3. That will cause acpi_device_get_power() to run
acpi_power_get_inferred_state() for device A and the resultant power
state will be D0, which is incorrect.
To fix that change acpi_device_get_power() to first execute
acpi_power_get_inferred_state() for the given device (if it
depends on power resources) and to evaluate _PSC for it subsequently,
so that the result inferred from the power resources configuration
can be amended by the _PSC return value.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Aaron Lu <aaron.lu@intel.com>
2013-03-24 21:54:40 +00:00
|
|
|
* Get the device's power state from power resources settings and _PSC,
|
|
|
|
* if available.
|
2013-01-17 13:11:08 +00:00
|
|
|
*/
|
ACPI / PM: Fix potential problem in acpi_device_get_power()
Theoretically, in some situations acpi_device_get_power() may return
an incorrect result, because the settings of the power resources
depended on by the device may indicate a power state shallower than
the actual power state of the device.
Say that two devices, A and B, depend on two power resources, X and
Y, in such a way that _PR0 for both A and B list both X and Y and
_PR3 for both A and B list power resource Y alone. Also suppose
that _PS0 and _PS3 are present for both A and B. Then, if devices
A and B are initially in D0, power resources X and Y are initially
"on" and their reference counters are equal to 2. To put device A
into power state D3hot the kernel will decrement the reference
counter of power resource X, but that power resource won't be turned
off, because it is still in use by device B (its reference counter is
equal to 1). Next, _PS3 will be executed for device A. Afterward
the configuration of the power resources will indicate that device
A is in power state D0 (both X and Y are "on"), but in fact it is
in D3hot (because _PS3 has been executed for it).
In that situation, if acpi_device_get_power() is called to get the
power state of device A, it will first execute _PSC for it which
should return 3. That will cause acpi_device_get_power() to run
acpi_power_get_inferred_state() for device A and the resultant power
state will be D0, which is incorrect.
To fix that change acpi_device_get_power() to first execute
acpi_power_get_inferred_state() for the given device (if it
depends on power resources) and to evaluate _PSC for it subsequently,
so that the result inferred from the power resources configuration
can be amended by the _PSC return value.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Aaron Lu <aaron.lu@intel.com>
2013-03-24 21:54:40 +00:00
|
|
|
if (device->power.flags.power_resources) {
|
|
|
|
int error = acpi_power_get_inferred_state(device, &result);
|
|
|
|
if (error)
|
|
|
|
return error;
|
|
|
|
}
|
2013-01-17 13:11:08 +00:00
|
|
|
if (device->power.flags.explicit_get) {
|
ACPI / PM: Fix potential problem in acpi_device_get_power()
Theoretically, in some situations acpi_device_get_power() may return
an incorrect result, because the settings of the power resources
depended on by the device may indicate a power state shallower than
the actual power state of the device.
Say that two devices, A and B, depend on two power resources, X and
Y, in such a way that _PR0 for both A and B list both X and Y and
_PR3 for both A and B list power resource Y alone. Also suppose
that _PS0 and _PS3 are present for both A and B. Then, if devices
A and B are initially in D0, power resources X and Y are initially
"on" and their reference counters are equal to 2. To put device A
into power state D3hot the kernel will decrement the reference
counter of power resource X, but that power resource won't be turned
off, because it is still in use by device B (its reference counter is
equal to 1). Next, _PS3 will be executed for device A. Afterward
the configuration of the power resources will indicate that device
A is in power state D0 (both X and Y are "on"), but in fact it is
in D3hot (because _PS3 has been executed for it).
In that situation, if acpi_device_get_power() is called to get the
power state of device A, it will first execute _PSC for it which
should return 3. That will cause acpi_device_get_power() to run
acpi_power_get_inferred_state() for device A and the resultant power
state will be D0, which is incorrect.
To fix that change acpi_device_get_power() to first execute
acpi_power_get_inferred_state() for the given device (if it
depends on power resources) and to evaluate _PSC for it subsequently,
so that the result inferred from the power resources configuration
can be amended by the _PSC return value.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Aaron Lu <aaron.lu@intel.com>
2013-03-24 21:54:40 +00:00
|
|
|
acpi_handle handle = device->handle;
|
2013-01-17 13:11:08 +00:00
|
|
|
unsigned long long psc;
|
ACPI / PM: Fix potential problem in acpi_device_get_power()
Theoretically, in some situations acpi_device_get_power() may return
an incorrect result, because the settings of the power resources
depended on by the device may indicate a power state shallower than
the actual power state of the device.
Say that two devices, A and B, depend on two power resources, X and
Y, in such a way that _PR0 for both A and B list both X and Y and
_PR3 for both A and B list power resource Y alone. Also suppose
that _PS0 and _PS3 are present for both A and B. Then, if devices
A and B are initially in D0, power resources X and Y are initially
"on" and their reference counters are equal to 2. To put device A
into power state D3hot the kernel will decrement the reference
counter of power resource X, but that power resource won't be turned
off, because it is still in use by device B (its reference counter is
equal to 1). Next, _PS3 will be executed for device A. Afterward
the configuration of the power resources will indicate that device
A is in power state D0 (both X and Y are "on"), but in fact it is
in D3hot (because _PS3 has been executed for it).
In that situation, if acpi_device_get_power() is called to get the
power state of device A, it will first execute _PSC for it which
should return 3. That will cause acpi_device_get_power() to run
acpi_power_get_inferred_state() for device A and the resultant power
state will be D0, which is incorrect.
To fix that change acpi_device_get_power() to first execute
acpi_power_get_inferred_state() for the given device (if it
depends on power resources) and to evaluate _PSC for it subsequently,
so that the result inferred from the power resources configuration
can be amended by the _PSC return value.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Aaron Lu <aaron.lu@intel.com>
2013-03-24 21:54:40 +00:00
|
|
|
acpi_status status;
|
|
|
|
|
|
|
|
status = acpi_evaluate_integer(handle, "_PSC", NULL, &psc);
|
2013-01-17 13:11:08 +00:00
|
|
|
if (ACPI_FAILURE(status))
|
|
|
|
return -ENODEV;
|
|
|
|
|
ACPI / PM: Fix potential problem in acpi_device_get_power()
Theoretically, in some situations acpi_device_get_power() may return
an incorrect result, because the settings of the power resources
depended on by the device may indicate a power state shallower than
the actual power state of the device.
Say that two devices, A and B, depend on two power resources, X and
Y, in such a way that _PR0 for both A and B list both X and Y and
_PR3 for both A and B list power resource Y alone. Also suppose
that _PS0 and _PS3 are present for both A and B. Then, if devices
A and B are initially in D0, power resources X and Y are initially
"on" and their reference counters are equal to 2. To put device A
into power state D3hot the kernel will decrement the reference
counter of power resource X, but that power resource won't be turned
off, because it is still in use by device B (its reference counter is
equal to 1). Next, _PS3 will be executed for device A. Afterward
the configuration of the power resources will indicate that device
A is in power state D0 (both X and Y are "on"), but in fact it is
in D3hot (because _PS3 has been executed for it).
In that situation, if acpi_device_get_power() is called to get the
power state of device A, it will first execute _PSC for it which
should return 3. That will cause acpi_device_get_power() to run
acpi_power_get_inferred_state() for device A and the resultant power
state will be D0, which is incorrect.
To fix that change acpi_device_get_power() to first execute
acpi_power_get_inferred_state() for the given device (if it
depends on power resources) and to evaluate _PSC for it subsequently,
so that the result inferred from the power resources configuration
can be amended by the _PSC return value.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Aaron Lu <aaron.lu@intel.com>
2013-03-24 21:54:40 +00:00
|
|
|
/*
|
|
|
|
* The power resources settings may indicate a power state
|
|
|
|
* shallower than the actual power state of the device.
|
|
|
|
*
|
|
|
|
* Moreover, on systems predating ACPI 4.0, if the device
|
|
|
|
* doesn't depend on any power resources and _PSC returns 3,
|
|
|
|
* that means "power off". We need to maintain compatibility
|
|
|
|
* with those systems.
|
|
|
|
*/
|
|
|
|
if (psc > result && psc < ACPI_STATE_D3_COLD)
|
|
|
|
result = psc;
|
|
|
|
else if (result == ACPI_STATE_UNKNOWN)
|
|
|
|
result = psc > ACPI_STATE_D2 ? ACPI_STATE_D3_COLD : psc;
|
2013-01-17 13:11:08 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If we were unsure about the device parent's power state up to this
|
|
|
|
* point, the fact that the device is in D0 implies that the parent has
|
|
|
|
* to be in D0 too.
|
|
|
|
*/
|
|
|
|
if (device->parent && device->parent->power.state == ACPI_STATE_UNKNOWN
|
|
|
|
&& result == ACPI_STATE_D0)
|
|
|
|
device->parent->power.state = ACPI_STATE_D0;
|
|
|
|
|
|
|
|
*state = result;
|
|
|
|
|
|
|
|
out:
|
|
|
|
ACPI_DEBUG_PRINT((ACPI_DB_INFO, "Device [%s] power state is %s\n",
|
|
|
|
device->pnp.bus_id, acpi_power_state_string(*state)));
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2013-01-22 11:55:52 +00:00
|
|
|
static int acpi_dev_pm_explicit_set(struct acpi_device *adev, int state)
|
|
|
|
{
|
|
|
|
if (adev->power.states[state].flags.explicit_set) {
|
|
|
|
char method[5] = { '_', 'P', 'S', '0' + state, '\0' };
|
|
|
|
acpi_status status;
|
|
|
|
|
|
|
|
status = acpi_evaluate_object(adev->handle, method, NULL, NULL);
|
|
|
|
if (ACPI_FAILURE(status))
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2013-01-17 13:11:08 +00:00
|
|
|
/**
|
|
|
|
* acpi_device_set_power - Set power state of an ACPI device.
|
|
|
|
* @device: Device to set the power state of.
|
|
|
|
* @state: New power state to set.
|
|
|
|
*
|
|
|
|
* Callers must ensure that the device is power manageable before using this
|
|
|
|
* function.
|
|
|
|
*/
|
|
|
|
int acpi_device_set_power(struct acpi_device *device, int state)
|
|
|
|
{
|
|
|
|
int result = 0;
|
|
|
|
bool cut_power = false;
|
|
|
|
|
|
|
|
if (!device || (state < ACPI_STATE_D0) || (state > ACPI_STATE_D3_COLD))
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
/* Make sure this is a valid target state */
|
|
|
|
|
|
|
|
if (state == device->power.state) {
|
|
|
|
ACPI_DEBUG_PRINT((ACPI_DB_INFO, "Device is already at %s\n",
|
|
|
|
acpi_power_state_string(state)));
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!device->power.states[state].flags.valid) {
|
|
|
|
printk(KERN_WARNING PREFIX "Device does not support %s\n",
|
|
|
|
acpi_power_state_string(state));
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
if (device->parent && (state < device->parent->power.state)) {
|
|
|
|
printk(KERN_WARNING PREFIX
|
|
|
|
"Cannot set device to a higher-powered"
|
|
|
|
" state than parent\n");
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* For D3cold we should first transition into D3hot. */
|
|
|
|
if (state == ACPI_STATE_D3_COLD
|
|
|
|
&& device->power.states[ACPI_STATE_D3_COLD].flags.os_accessible) {
|
|
|
|
state = ACPI_STATE_D3_HOT;
|
|
|
|
cut_power = true;
|
|
|
|
}
|
|
|
|
|
2013-01-22 11:56:04 +00:00
|
|
|
if (state < device->power.state && state != ACPI_STATE_D0
|
|
|
|
&& device->power.state >= ACPI_STATE_D3_HOT) {
|
|
|
|
printk(KERN_WARNING PREFIX
|
|
|
|
"Cannot transition to non-D0 state from D3\n");
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
|
2013-01-17 13:11:08 +00:00
|
|
|
/*
|
|
|
|
* Transition Power
|
|
|
|
* ----------------
|
2013-01-22 11:56:04 +00:00
|
|
|
* In accordance with the ACPI specification first apply power (via
|
|
|
|
* power resources) and then evalute _PSx.
|
2013-01-17 13:11:08 +00:00
|
|
|
*/
|
2013-01-22 11:56:04 +00:00
|
|
|
if (device->power.flags.power_resources) {
|
|
|
|
result = acpi_power_transition(device, state);
|
2013-01-22 11:55:52 +00:00
|
|
|
if (result)
|
|
|
|
goto end;
|
2013-01-17 13:11:08 +00:00
|
|
|
}
|
2013-01-22 11:56:04 +00:00
|
|
|
result = acpi_dev_pm_explicit_set(device, state);
|
|
|
|
if (result)
|
|
|
|
goto end;
|
2013-01-17 13:11:08 +00:00
|
|
|
|
2013-01-22 11:56:35 +00:00
|
|
|
if (cut_power) {
|
|
|
|
device->power.state = state;
|
|
|
|
state = ACPI_STATE_D3_COLD;
|
|
|
|
result = acpi_power_transition(device, state);
|
|
|
|
}
|
2013-01-17 13:11:08 +00:00
|
|
|
|
2013-01-22 11:56:04 +00:00
|
|
|
end:
|
|
|
|
if (result) {
|
2013-01-17 13:11:08 +00:00
|
|
|
printk(KERN_WARNING PREFIX
|
|
|
|
"Device [%s] failed to transition to %s\n",
|
|
|
|
device->pnp.bus_id,
|
|
|
|
acpi_power_state_string(state));
|
2013-01-22 11:56:04 +00:00
|
|
|
} else {
|
2013-01-17 13:11:08 +00:00
|
|
|
device->power.state = state;
|
|
|
|
ACPI_DEBUG_PRINT((ACPI_DB_INFO,
|
|
|
|
"Device [%s] transitioned to %s\n",
|
|
|
|
device->pnp.bus_id,
|
|
|
|
acpi_power_state_string(state)));
|
|
|
|
}
|
|
|
|
|
|
|
|
return result;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(acpi_device_set_power);
|
|
|
|
|
|
|
|
int acpi_bus_set_power(acpi_handle handle, int state)
|
|
|
|
{
|
|
|
|
struct acpi_device *device;
|
|
|
|
int result;
|
|
|
|
|
|
|
|
result = acpi_bus_get_device(handle, &device);
|
|
|
|
if (result)
|
|
|
|
return result;
|
|
|
|
|
|
|
|
if (!device->flags.power_manageable) {
|
|
|
|
ACPI_DEBUG_PRINT((ACPI_DB_INFO,
|
|
|
|
"Device [%s] is not power manageable\n",
|
|
|
|
dev_name(&device->dev)));
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
|
|
|
|
return acpi_device_set_power(device, state);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(acpi_bus_set_power);
|
|
|
|
|
|
|
|
int acpi_bus_init_power(struct acpi_device *device)
|
|
|
|
{
|
|
|
|
int state;
|
|
|
|
int result;
|
|
|
|
|
|
|
|
if (!device)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
device->power.state = ACPI_STATE_UNKNOWN;
|
|
|
|
|
|
|
|
result = acpi_device_get_power(device, &state);
|
|
|
|
if (result)
|
|
|
|
return result;
|
|
|
|
|
2013-01-22 11:54:38 +00:00
|
|
|
if (state < ACPI_STATE_D3_COLD && device->power.flags.power_resources) {
|
2013-01-17 13:11:08 +00:00
|
|
|
result = acpi_power_on_resources(device, state);
|
2013-01-22 11:54:38 +00:00
|
|
|
if (result)
|
|
|
|
return result;
|
2013-01-17 13:11:08 +00:00
|
|
|
|
2013-01-22 11:55:52 +00:00
|
|
|
result = acpi_dev_pm_explicit_set(device, state);
|
|
|
|
if (result)
|
|
|
|
return result;
|
2013-02-01 22:43:02 +00:00
|
|
|
} else if (state == ACPI_STATE_UNKNOWN) {
|
2013-06-05 12:01:19 +00:00
|
|
|
/*
|
|
|
|
* No power resources and missing _PSC? Cross fingers and make
|
|
|
|
* it D0 in hope that this is what the BIOS put the device into.
|
|
|
|
* [We tried to force D0 here by executing _PS0, but that broke
|
|
|
|
* Toshiba P870-303 in a nasty way.]
|
|
|
|
*/
|
2013-02-01 22:43:02 +00:00
|
|
|
state = ACPI_STATE_D0;
|
2013-01-22 11:54:38 +00:00
|
|
|
}
|
|
|
|
device->power.state = state;
|
|
|
|
return 0;
|
2013-01-17 13:11:08 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
int acpi_bus_update_power(acpi_handle handle, int *state_p)
|
|
|
|
{
|
|
|
|
struct acpi_device *device;
|
|
|
|
int state;
|
|
|
|
int result;
|
|
|
|
|
|
|
|
result = acpi_bus_get_device(handle, &device);
|
|
|
|
if (result)
|
|
|
|
return result;
|
|
|
|
|
|
|
|
result = acpi_device_get_power(device, &state);
|
|
|
|
if (result)
|
|
|
|
return result;
|
|
|
|
|
2013-02-03 13:57:32 +00:00
|
|
|
if (state == ACPI_STATE_UNKNOWN)
|
|
|
|
state = ACPI_STATE_D0;
|
|
|
|
|
2013-01-17 13:11:08 +00:00
|
|
|
result = acpi_device_set_power(device, state);
|
|
|
|
if (!result && state_p)
|
|
|
|
*state_p = state;
|
|
|
|
|
|
|
|
return result;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(acpi_bus_update_power);
|
|
|
|
|
|
|
|
bool acpi_bus_power_manageable(acpi_handle handle)
|
|
|
|
{
|
|
|
|
struct acpi_device *device;
|
|
|
|
int result;
|
|
|
|
|
|
|
|
result = acpi_bus_get_device(handle, &device);
|
|
|
|
return result ? false : device->flags.power_manageable;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(acpi_bus_power_manageable);
|
|
|
|
|
2013-05-16 20:29:28 +00:00
|
|
|
#ifdef CONFIG_PM
|
|
|
|
static DEFINE_MUTEX(acpi_pm_notifier_lock);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_add_pm_notifier - Register PM notifier for given ACPI device.
|
|
|
|
* @adev: ACPI device to add the notifier for.
|
|
|
|
* @context: Context information to pass to the notifier routine.
|
|
|
|
*
|
|
|
|
* NOTE: @adev need not be a run-wake or wakeup device to be a valid source of
|
|
|
|
* PM wakeup events. For example, wakeup events may be generated for bridges
|
|
|
|
* if one of the devices below the bridge is signaling wakeup, even if the
|
|
|
|
* bridge itself doesn't have a wakeup GPE associated with it.
|
|
|
|
*/
|
|
|
|
acpi_status acpi_add_pm_notifier(struct acpi_device *adev,
|
|
|
|
acpi_notify_handler handler, void *context)
|
|
|
|
{
|
|
|
|
acpi_status status = AE_ALREADY_EXISTS;
|
|
|
|
|
|
|
|
mutex_lock(&acpi_pm_notifier_lock);
|
|
|
|
|
|
|
|
if (adev->wakeup.flags.notifier_present)
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
status = acpi_install_notify_handler(adev->handle,
|
|
|
|
ACPI_SYSTEM_NOTIFY,
|
|
|
|
handler, context);
|
|
|
|
if (ACPI_FAILURE(status))
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
adev->wakeup.flags.notifier_present = true;
|
|
|
|
|
|
|
|
out:
|
|
|
|
mutex_unlock(&acpi_pm_notifier_lock);
|
|
|
|
return status;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_remove_pm_notifier - Unregister PM notifier from given ACPI device.
|
|
|
|
* @adev: ACPI device to remove the notifier from.
|
|
|
|
*/
|
|
|
|
acpi_status acpi_remove_pm_notifier(struct acpi_device *adev,
|
|
|
|
acpi_notify_handler handler)
|
|
|
|
{
|
|
|
|
acpi_status status = AE_BAD_PARAMETER;
|
|
|
|
|
|
|
|
mutex_lock(&acpi_pm_notifier_lock);
|
|
|
|
|
|
|
|
if (!adev->wakeup.flags.notifier_present)
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
status = acpi_remove_notify_handler(adev->handle,
|
|
|
|
ACPI_SYSTEM_NOTIFY,
|
|
|
|
handler);
|
|
|
|
if (ACPI_FAILURE(status))
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
adev->wakeup.flags.notifier_present = false;
|
|
|
|
|
|
|
|
out:
|
|
|
|
mutex_unlock(&acpi_pm_notifier_lock);
|
|
|
|
return status;
|
|
|
|
}
|
|
|
|
|
2013-01-17 13:11:08 +00:00
|
|
|
bool acpi_bus_can_wakeup(acpi_handle handle)
|
|
|
|
{
|
|
|
|
struct acpi_device *device;
|
|
|
|
int result;
|
|
|
|
|
|
|
|
result = acpi_bus_get_device(handle, &device);
|
|
|
|
return result ? false : device->wakeup.flags.valid;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(acpi_bus_can_wakeup);
|
|
|
|
|
2012-11-02 00:40:18 +00:00
|
|
|
/**
|
2013-06-15 22:37:42 +00:00
|
|
|
* acpi_dev_pm_get_state - Get preferred power state of ACPI device.
|
2012-11-02 00:40:18 +00:00
|
|
|
* @dev: Device whose preferred target power state to return.
|
|
|
|
* @adev: ACPI device node corresponding to @dev.
|
|
|
|
* @target_state: System state to match the resultant device state.
|
|
|
|
* @d_max_in: Deepest low-power state to take into consideration.
|
|
|
|
* @d_min_p: Location to store the upper limit of the allowed states range.
|
|
|
|
* Return value: Preferred power state of the device on success, -ENODEV
|
|
|
|
* (if there's no 'struct acpi_device' for @dev) or -EINVAL on failure
|
|
|
|
*
|
|
|
|
* Find the lowest power (highest number) ACPI device power state that the
|
|
|
|
* device can be in while the system is in the state represented by
|
|
|
|
* @target_state. If @d_min_p is set, the highest power (lowest number) device
|
|
|
|
* power state that @dev can be in for the given system sleep state is stored
|
|
|
|
* at the location pointed to by it.
|
|
|
|
*
|
|
|
|
* Callers must ensure that @dev and @adev are valid pointers and that @adev
|
|
|
|
* actually corresponds to @dev before using this function.
|
|
|
|
*/
|
2013-06-15 22:37:42 +00:00
|
|
|
static int acpi_dev_pm_get_state(struct device *dev, struct acpi_device *adev,
|
|
|
|
u32 target_state, int d_max_in, int *d_min_p)
|
2012-11-02 00:40:18 +00:00
|
|
|
{
|
|
|
|
char acpi_method[] = "_SxD";
|
|
|
|
unsigned long long d_min, d_max;
|
|
|
|
bool wakeup = false;
|
|
|
|
|
|
|
|
if (d_max_in < ACPI_STATE_D0 || d_max_in > ACPI_STATE_D3)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
if (d_max_in > ACPI_STATE_D3_HOT) {
|
|
|
|
enum pm_qos_flags_status stat;
|
|
|
|
|
|
|
|
stat = dev_pm_qos_flags(dev, PM_QOS_FLAG_NO_POWER_OFF);
|
|
|
|
if (stat == PM_QOS_FLAGS_ALL)
|
|
|
|
d_max_in = ACPI_STATE_D3_HOT;
|
|
|
|
}
|
|
|
|
|
|
|
|
acpi_method[2] = '0' + target_state;
|
|
|
|
/*
|
|
|
|
* If the sleep state is S0, the lowest limit from ACPI is D3,
|
|
|
|
* but if the device has _S0W, we will use the value from _S0W
|
|
|
|
* as the lowest limit from ACPI. Finally, we will constrain
|
|
|
|
* the lowest limit with the specified one.
|
|
|
|
*/
|
|
|
|
d_min = ACPI_STATE_D0;
|
|
|
|
d_max = ACPI_STATE_D3;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If present, _SxD methods return the minimum D-state (highest power
|
|
|
|
* state) we can use for the corresponding S-states. Otherwise, the
|
|
|
|
* minimum D-state is D0 (ACPI 3.x).
|
|
|
|
*
|
|
|
|
* NOTE: We rely on acpi_evaluate_integer() not clobbering the integer
|
|
|
|
* provided -- that's our fault recovery, we ignore retval.
|
|
|
|
*/
|
|
|
|
if (target_state > ACPI_STATE_S0) {
|
|
|
|
acpi_evaluate_integer(adev->handle, acpi_method, NULL, &d_min);
|
|
|
|
wakeup = device_may_wakeup(dev) && adev->wakeup.flags.valid
|
|
|
|
&& adev->wakeup.sleep_state >= target_state;
|
|
|
|
} else if (dev_pm_qos_flags(dev, PM_QOS_FLAG_REMOTE_WAKEUP) !=
|
|
|
|
PM_QOS_FLAGS_NONE) {
|
|
|
|
wakeup = adev->wakeup.flags.valid;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If _PRW says we can wake up the system from the target sleep state,
|
|
|
|
* the D-state returned by _SxD is sufficient for that (we assume a
|
|
|
|
* wakeup-aware driver if wake is set). Still, if _SxW exists
|
|
|
|
* (ACPI 3.x), it should return the maximum (lowest power) D-state that
|
|
|
|
* can wake the system. _S0W may be valid, too.
|
|
|
|
*/
|
|
|
|
if (wakeup) {
|
|
|
|
acpi_status status;
|
|
|
|
|
|
|
|
acpi_method[3] = 'W';
|
|
|
|
status = acpi_evaluate_integer(adev->handle, acpi_method, NULL,
|
|
|
|
&d_max);
|
|
|
|
if (ACPI_FAILURE(status)) {
|
|
|
|
if (target_state != ACPI_STATE_S0 ||
|
|
|
|
status != AE_NOT_FOUND)
|
|
|
|
d_max = d_min;
|
|
|
|
} else if (d_max < d_min) {
|
|
|
|
/* Warn the user of the broken DSDT */
|
|
|
|
printk(KERN_WARNING "ACPI: Wrong value from %s\n",
|
|
|
|
acpi_method);
|
|
|
|
/* Sanitize it */
|
|
|
|
d_min = d_max;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (d_max_in < d_min)
|
|
|
|
return -EINVAL;
|
|
|
|
if (d_min_p)
|
|
|
|
*d_min_p = d_min;
|
|
|
|
/* constrain d_max with specified lowest limit (max number) */
|
|
|
|
if (d_max > d_max_in) {
|
|
|
|
for (d_max = d_max_in; d_max > d_min; d_max--) {
|
|
|
|
if (adev->power.states[d_max].flags.valid)
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return d_max;
|
|
|
|
}
|
2012-11-02 00:40:28 +00:00
|
|
|
|
2012-11-02 00:40:53 +00:00
|
|
|
/**
|
|
|
|
* acpi_pm_device_sleep_state - Get preferred power state of ACPI device.
|
|
|
|
* @dev: Device whose preferred target power state to return.
|
|
|
|
* @d_min_p: Location to store the upper limit of the allowed states range.
|
|
|
|
* @d_max_in: Deepest low-power state to take into consideration.
|
|
|
|
* Return value: Preferred power state of the device on success, -ENODEV
|
|
|
|
* (if there's no 'struct acpi_device' for @dev) or -EINVAL on failure
|
|
|
|
*
|
|
|
|
* The caller must ensure that @dev is valid before using this function.
|
|
|
|
*/
|
|
|
|
int acpi_pm_device_sleep_state(struct device *dev, int *d_min_p, int d_max_in)
|
|
|
|
{
|
|
|
|
acpi_handle handle = DEVICE_ACPI_HANDLE(dev);
|
|
|
|
struct acpi_device *adev;
|
|
|
|
|
2013-01-31 03:22:14 +00:00
|
|
|
if (!handle || acpi_bus_get_device(handle, &adev)) {
|
2012-11-02 00:40:53 +00:00
|
|
|
dev_dbg(dev, "ACPI handle without context in %s!\n", __func__);
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
|
2013-06-15 22:37:42 +00:00
|
|
|
return acpi_dev_pm_get_state(dev, adev, acpi_target_system_state(),
|
|
|
|
d_max_in, d_min_p);
|
2012-11-02 00:40:53 +00:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(acpi_pm_device_sleep_state);
|
|
|
|
|
2012-11-02 00:40:28 +00:00
|
|
|
#ifdef CONFIG_PM_RUNTIME
|
ACPI / PM: Provide ACPI PM callback routines for subsystems
Some bus types don't support power management natively, but generally
there may be device nodes in ACPI tables corresponding to the devices
whose bus types they are (under ACPI 5 those bus types may be SPI,
I2C and platform). If that is the case, standard ACPI power
management may be applied to those devices, although currently the
kernel has no means for that.
For this reason, provide a set of routines that may be used as power
management callbacks for such devices. This may be done in three
different ways.
(1) Device drivers handling the devices in question may run
acpi_dev_pm_attach() in their .probe() routines, which (on
success) will cause the devices to be added to the general ACPI
PM domain and ACPI power management will be used for them going
forward. Then, acpi_dev_pm_detach() may be used to remove the
devices from the general ACPI PM domain if ACPI power management
is not necessary for them any more.
(2) The devices' subsystems may use acpi_subsys_runtime_suspend(),
acpi_subsys_runtime_resume(), acpi_subsys_prepare(),
acpi_subsys_suspend_late(), acpi_subsys_resume_early() as their
power management callbacks in the same way as the general ACPI
PM domain does that.
(3) The devices' drivers may execute acpi_dev_suspend_late(),
acpi_dev_resume_early(), acpi_dev_runtime_suspend(),
acpi_dev_runtime_resume() from their power management callbacks
as appropriate, if that's absolutely necessary, but it is not
recommended to do that, because such drivers may not work
without ACPI support as a result.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:41:01 +00:00
|
|
|
/**
|
|
|
|
* acpi_wakeup_device - Wakeup notification handler for ACPI devices.
|
|
|
|
* @handle: ACPI handle of the device the notification is for.
|
|
|
|
* @event: Type of the signaled event.
|
|
|
|
* @context: Device corresponding to @handle.
|
|
|
|
*/
|
|
|
|
static void acpi_wakeup_device(acpi_handle handle, u32 event, void *context)
|
|
|
|
{
|
|
|
|
struct device *dev = context;
|
|
|
|
|
|
|
|
if (event == ACPI_NOTIFY_DEVICE_WAKE && dev) {
|
|
|
|
pm_wakeup_event(dev, 0);
|
|
|
|
pm_runtime_resume(dev);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2012-11-02 00:40:28 +00:00
|
|
|
/**
|
ACPI / PM: Split device wakeup management routines
Two device wakeup management routines in device_pm.c and sleep.c,
acpi_pm_device_run_wake() and acpi_pm_device_sleep_wake(), take a
device pointer argument and use it to obtain the ACPI handle of the
corresponding ACPI namespace node. That handle is then used to get
the address of the struct acpi_device object corresponding to the
struct device passed as the argument.
Unfortunately, that last operation may be costly, because it involves
taking the global ACPI namespace mutex, so it shouldn't be carried
out too often. However, the callers of those routines usually call
them in a row with acpi_pm_device_sleep_state() which also takes that
mutex for the same reason, so it would be more efficient if they ran
acpi_bus_get_device() themselves to obtain a pointer to the struct
acpi_device object in question and then passed that pointer to the
appropriate PM routines.
To make that possible, split each of the PM routines mentioned above
in two parts, one taking a struct acpi_device pointer argument and
the other implementing the current interface for compatibility.
Additionally, change acpi_pm_device_run_wake() to actually return
an error code if there is an error while setting up runtime remote
wakeup for the device.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:40:36 +00:00
|
|
|
* __acpi_device_run_wake - Enable/disable runtime remote wakeup for device.
|
|
|
|
* @adev: ACPI device to enable/disable the remote wakeup for.
|
2012-11-02 00:40:28 +00:00
|
|
|
* @enable: Whether to enable or disable the wakeup functionality.
|
|
|
|
*
|
ACPI / PM: Split device wakeup management routines
Two device wakeup management routines in device_pm.c and sleep.c,
acpi_pm_device_run_wake() and acpi_pm_device_sleep_wake(), take a
device pointer argument and use it to obtain the ACPI handle of the
corresponding ACPI namespace node. That handle is then used to get
the address of the struct acpi_device object corresponding to the
struct device passed as the argument.
Unfortunately, that last operation may be costly, because it involves
taking the global ACPI namespace mutex, so it shouldn't be carried
out too often. However, the callers of those routines usually call
them in a row with acpi_pm_device_sleep_state() which also takes that
mutex for the same reason, so it would be more efficient if they ran
acpi_bus_get_device() themselves to obtain a pointer to the struct
acpi_device object in question and then passed that pointer to the
appropriate PM routines.
To make that possible, split each of the PM routines mentioned above
in two parts, one taking a struct acpi_device pointer argument and
the other implementing the current interface for compatibility.
Additionally, change acpi_pm_device_run_wake() to actually return
an error code if there is an error while setting up runtime remote
wakeup for the device.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:40:36 +00:00
|
|
|
* Enable/disable the GPE associated with @adev so that it can generate
|
|
|
|
* wakeup signals for the device in response to external (remote) events and
|
|
|
|
* enable/disable device wakeup power.
|
|
|
|
*
|
|
|
|
* Callers must ensure that @adev is a valid ACPI device node before executing
|
|
|
|
* this function.
|
|
|
|
*/
|
|
|
|
int __acpi_device_run_wake(struct acpi_device *adev, bool enable)
|
|
|
|
{
|
|
|
|
struct acpi_device_wakeup *wakeup = &adev->wakeup;
|
|
|
|
|
|
|
|
if (enable) {
|
|
|
|
acpi_status res;
|
|
|
|
int error;
|
|
|
|
|
|
|
|
error = acpi_enable_wakeup_device_power(adev, ACPI_STATE_S0);
|
|
|
|
if (error)
|
|
|
|
return error;
|
|
|
|
|
|
|
|
res = acpi_enable_gpe(wakeup->gpe_device, wakeup->gpe_number);
|
|
|
|
if (ACPI_FAILURE(res)) {
|
|
|
|
acpi_disable_wakeup_device_power(adev);
|
|
|
|
return -EIO;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
acpi_disable_gpe(wakeup->gpe_device, wakeup->gpe_number);
|
|
|
|
acpi_disable_wakeup_device_power(adev);
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_pm_device_run_wake - Enable/disable remote wakeup for given device.
|
|
|
|
* @dev: Device to enable/disable the platform to wake up.
|
|
|
|
* @enable: Whether to enable or disable the wakeup functionality.
|
2012-11-02 00:40:28 +00:00
|
|
|
*/
|
|
|
|
int acpi_pm_device_run_wake(struct device *phys_dev, bool enable)
|
|
|
|
{
|
ACPI / PM: Split device wakeup management routines
Two device wakeup management routines in device_pm.c and sleep.c,
acpi_pm_device_run_wake() and acpi_pm_device_sleep_wake(), take a
device pointer argument and use it to obtain the ACPI handle of the
corresponding ACPI namespace node. That handle is then used to get
the address of the struct acpi_device object corresponding to the
struct device passed as the argument.
Unfortunately, that last operation may be costly, because it involves
taking the global ACPI namespace mutex, so it shouldn't be carried
out too often. However, the callers of those routines usually call
them in a row with acpi_pm_device_sleep_state() which also takes that
mutex for the same reason, so it would be more efficient if they ran
acpi_bus_get_device() themselves to obtain a pointer to the struct
acpi_device object in question and then passed that pointer to the
appropriate PM routines.
To make that possible, split each of the PM routines mentioned above
in two parts, one taking a struct acpi_device pointer argument and
the other implementing the current interface for compatibility.
Additionally, change acpi_pm_device_run_wake() to actually return
an error code if there is an error while setting up runtime remote
wakeup for the device.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:40:36 +00:00
|
|
|
struct acpi_device *adev;
|
2012-11-02 00:40:28 +00:00
|
|
|
acpi_handle handle;
|
|
|
|
|
|
|
|
if (!device_run_wake(phys_dev))
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
handle = DEVICE_ACPI_HANDLE(phys_dev);
|
2013-01-31 03:22:14 +00:00
|
|
|
if (!handle || acpi_bus_get_device(handle, &adev)) {
|
ACPI / PM: Split device wakeup management routines
Two device wakeup management routines in device_pm.c and sleep.c,
acpi_pm_device_run_wake() and acpi_pm_device_sleep_wake(), take a
device pointer argument and use it to obtain the ACPI handle of the
corresponding ACPI namespace node. That handle is then used to get
the address of the struct acpi_device object corresponding to the
struct device passed as the argument.
Unfortunately, that last operation may be costly, because it involves
taking the global ACPI namespace mutex, so it shouldn't be carried
out too often. However, the callers of those routines usually call
them in a row with acpi_pm_device_sleep_state() which also takes that
mutex for the same reason, so it would be more efficient if they ran
acpi_bus_get_device() themselves to obtain a pointer to the struct
acpi_device object in question and then passed that pointer to the
appropriate PM routines.
To make that possible, split each of the PM routines mentioned above
in two parts, one taking a struct acpi_device pointer argument and
the other implementing the current interface for compatibility.
Additionally, change acpi_pm_device_run_wake() to actually return
an error code if there is an error while setting up runtime remote
wakeup for the device.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:40:36 +00:00
|
|
|
dev_dbg(phys_dev, "ACPI handle without context in %s!\n",
|
2012-11-02 00:40:28 +00:00
|
|
|
__func__);
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
|
ACPI / PM: Split device wakeup management routines
Two device wakeup management routines in device_pm.c and sleep.c,
acpi_pm_device_run_wake() and acpi_pm_device_sleep_wake(), take a
device pointer argument and use it to obtain the ACPI handle of the
corresponding ACPI namespace node. That handle is then used to get
the address of the struct acpi_device object corresponding to the
struct device passed as the argument.
Unfortunately, that last operation may be costly, because it involves
taking the global ACPI namespace mutex, so it shouldn't be carried
out too often. However, the callers of those routines usually call
them in a row with acpi_pm_device_sleep_state() which also takes that
mutex for the same reason, so it would be more efficient if they ran
acpi_bus_get_device() themselves to obtain a pointer to the struct
acpi_device object in question and then passed that pointer to the
appropriate PM routines.
To make that possible, split each of the PM routines mentioned above
in two parts, one taking a struct acpi_device pointer argument and
the other implementing the current interface for compatibility.
Additionally, change acpi_pm_device_run_wake() to actually return
an error code if there is an error while setting up runtime remote
wakeup for the device.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:40:36 +00:00
|
|
|
return __acpi_device_run_wake(adev, enable);
|
2012-11-02 00:40:28 +00:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(acpi_pm_device_run_wake);
|
ACPI / PM: Provide ACPI PM callback routines for subsystems
Some bus types don't support power management natively, but generally
there may be device nodes in ACPI tables corresponding to the devices
whose bus types they are (under ACPI 5 those bus types may be SPI,
I2C and platform). If that is the case, standard ACPI power
management may be applied to those devices, although currently the
kernel has no means for that.
For this reason, provide a set of routines that may be used as power
management callbacks for such devices. This may be done in three
different ways.
(1) Device drivers handling the devices in question may run
acpi_dev_pm_attach() in their .probe() routines, which (on
success) will cause the devices to be added to the general ACPI
PM domain and ACPI power management will be used for them going
forward. Then, acpi_dev_pm_detach() may be used to remove the
devices from the general ACPI PM domain if ACPI power management
is not necessary for them any more.
(2) The devices' subsystems may use acpi_subsys_runtime_suspend(),
acpi_subsys_runtime_resume(), acpi_subsys_prepare(),
acpi_subsys_suspend_late(), acpi_subsys_resume_early() as their
power management callbacks in the same way as the general ACPI
PM domain does that.
(3) The devices' drivers may execute acpi_dev_suspend_late(),
acpi_dev_resume_early(), acpi_dev_runtime_suspend(),
acpi_dev_runtime_resume() from their power management callbacks
as appropriate, if that's absolutely necessary, but it is not
recommended to do that, because such drivers may not work
without ACPI support as a result.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:41:01 +00:00
|
|
|
#else
|
|
|
|
static inline void acpi_wakeup_device(acpi_handle handle, u32 event,
|
|
|
|
void *context) {}
|
2012-11-02 00:40:28 +00:00
|
|
|
#endif /* CONFIG_PM_RUNTIME */
|
ACPI / PM: Split device wakeup management routines
Two device wakeup management routines in device_pm.c and sleep.c,
acpi_pm_device_run_wake() and acpi_pm_device_sleep_wake(), take a
device pointer argument and use it to obtain the ACPI handle of the
corresponding ACPI namespace node. That handle is then used to get
the address of the struct acpi_device object corresponding to the
struct device passed as the argument.
Unfortunately, that last operation may be costly, because it involves
taking the global ACPI namespace mutex, so it shouldn't be carried
out too often. However, the callers of those routines usually call
them in a row with acpi_pm_device_sleep_state() which also takes that
mutex for the same reason, so it would be more efficient if they ran
acpi_bus_get_device() themselves to obtain a pointer to the struct
acpi_device object in question and then passed that pointer to the
appropriate PM routines.
To make that possible, split each of the PM routines mentioned above
in two parts, one taking a struct acpi_device pointer argument and
the other implementing the current interface for compatibility.
Additionally, change acpi_pm_device_run_wake() to actually return
an error code if there is an error while setting up runtime remote
wakeup for the device.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:40:36 +00:00
|
|
|
|
2013-01-14 20:13:37 +00:00
|
|
|
#ifdef CONFIG_PM_SLEEP
|
ACPI / PM: Split device wakeup management routines
Two device wakeup management routines in device_pm.c and sleep.c,
acpi_pm_device_run_wake() and acpi_pm_device_sleep_wake(), take a
device pointer argument and use it to obtain the ACPI handle of the
corresponding ACPI namespace node. That handle is then used to get
the address of the struct acpi_device object corresponding to the
struct device passed as the argument.
Unfortunately, that last operation may be costly, because it involves
taking the global ACPI namespace mutex, so it shouldn't be carried
out too often. However, the callers of those routines usually call
them in a row with acpi_pm_device_sleep_state() which also takes that
mutex for the same reason, so it would be more efficient if they ran
acpi_bus_get_device() themselves to obtain a pointer to the struct
acpi_device object in question and then passed that pointer to the
appropriate PM routines.
To make that possible, split each of the PM routines mentioned above
in two parts, one taking a struct acpi_device pointer argument and
the other implementing the current interface for compatibility.
Additionally, change acpi_pm_device_run_wake() to actually return
an error code if there is an error while setting up runtime remote
wakeup for the device.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:40:36 +00:00
|
|
|
/**
|
|
|
|
* __acpi_device_sleep_wake - Enable or disable device to wake up the system.
|
|
|
|
* @dev: Device to enable/desible to wake up the system.
|
|
|
|
* @target_state: System state the device is supposed to wake up from.
|
|
|
|
* @enable: Whether to enable or disable @dev to wake up the system.
|
|
|
|
*/
|
|
|
|
int __acpi_device_sleep_wake(struct acpi_device *adev, u32 target_state,
|
|
|
|
bool enable)
|
|
|
|
{
|
|
|
|
return enable ?
|
|
|
|
acpi_enable_wakeup_device_power(adev, target_state) :
|
|
|
|
acpi_disable_wakeup_device_power(adev);
|
|
|
|
}
|
2012-11-02 00:40:53 +00:00
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_pm_device_sleep_wake - Enable or disable device to wake up the system.
|
|
|
|
* @dev: Device to enable/desible to wake up the system from sleep states.
|
|
|
|
* @enable: Whether to enable or disable @dev to wake up the system.
|
|
|
|
*/
|
|
|
|
int acpi_pm_device_sleep_wake(struct device *dev, bool enable)
|
|
|
|
{
|
|
|
|
acpi_handle handle;
|
|
|
|
struct acpi_device *adev;
|
|
|
|
int error;
|
|
|
|
|
|
|
|
if (!device_can_wakeup(dev))
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
handle = DEVICE_ACPI_HANDLE(dev);
|
2013-01-31 03:22:14 +00:00
|
|
|
if (!handle || acpi_bus_get_device(handle, &adev)) {
|
2012-11-02 00:40:53 +00:00
|
|
|
dev_dbg(dev, "ACPI handle without context in %s!\n", __func__);
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
|
|
|
|
error = __acpi_device_sleep_wake(adev, acpi_target_system_state(),
|
|
|
|
enable);
|
|
|
|
if (!error)
|
|
|
|
dev_info(dev, "System wakeup %s by ACPI\n",
|
|
|
|
enable ? "enabled" : "disabled");
|
|
|
|
|
|
|
|
return error;
|
|
|
|
}
|
ACPI / PM: Split device wakeup management routines
Two device wakeup management routines in device_pm.c and sleep.c,
acpi_pm_device_run_wake() and acpi_pm_device_sleep_wake(), take a
device pointer argument and use it to obtain the ACPI handle of the
corresponding ACPI namespace node. That handle is then used to get
the address of the struct acpi_device object corresponding to the
struct device passed as the argument.
Unfortunately, that last operation may be costly, because it involves
taking the global ACPI namespace mutex, so it shouldn't be carried
out too often. However, the callers of those routines usually call
them in a row with acpi_pm_device_sleep_state() which also takes that
mutex for the same reason, so it would be more efficient if they ran
acpi_bus_get_device() themselves to obtain a pointer to the struct
acpi_device object in question and then passed that pointer to the
appropriate PM routines.
To make that possible, split each of the PM routines mentioned above
in two parts, one taking a struct acpi_device pointer argument and
the other implementing the current interface for compatibility.
Additionally, change acpi_pm_device_run_wake() to actually return
an error code if there is an error while setting up runtime remote
wakeup for the device.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:40:36 +00:00
|
|
|
#endif /* CONFIG_PM_SLEEP */
|
ACPI / PM: Provide ACPI PM callback routines for subsystems
Some bus types don't support power management natively, but generally
there may be device nodes in ACPI tables corresponding to the devices
whose bus types they are (under ACPI 5 those bus types may be SPI,
I2C and platform). If that is the case, standard ACPI power
management may be applied to those devices, although currently the
kernel has no means for that.
For this reason, provide a set of routines that may be used as power
management callbacks for such devices. This may be done in three
different ways.
(1) Device drivers handling the devices in question may run
acpi_dev_pm_attach() in their .probe() routines, which (on
success) will cause the devices to be added to the general ACPI
PM domain and ACPI power management will be used for them going
forward. Then, acpi_dev_pm_detach() may be used to remove the
devices from the general ACPI PM domain if ACPI power management
is not necessary for them any more.
(2) The devices' subsystems may use acpi_subsys_runtime_suspend(),
acpi_subsys_runtime_resume(), acpi_subsys_prepare(),
acpi_subsys_suspend_late(), acpi_subsys_resume_early() as their
power management callbacks in the same way as the general ACPI
PM domain does that.
(3) The devices' drivers may execute acpi_dev_suspend_late(),
acpi_dev_resume_early(), acpi_dev_runtime_suspend(),
acpi_dev_runtime_resume() from their power management callbacks
as appropriate, if that's absolutely necessary, but it is not
recommended to do that, because such drivers may not work
without ACPI support as a result.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:41:01 +00:00
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_dev_pm_get_node - Get ACPI device node for the given physical device.
|
|
|
|
* @dev: Device to get the ACPI node for.
|
|
|
|
*/
|
2012-12-22 23:02:44 +00:00
|
|
|
struct acpi_device *acpi_dev_pm_get_node(struct device *dev)
|
ACPI / PM: Provide ACPI PM callback routines for subsystems
Some bus types don't support power management natively, but generally
there may be device nodes in ACPI tables corresponding to the devices
whose bus types they are (under ACPI 5 those bus types may be SPI,
I2C and platform). If that is the case, standard ACPI power
management may be applied to those devices, although currently the
kernel has no means for that.
For this reason, provide a set of routines that may be used as power
management callbacks for such devices. This may be done in three
different ways.
(1) Device drivers handling the devices in question may run
acpi_dev_pm_attach() in their .probe() routines, which (on
success) will cause the devices to be added to the general ACPI
PM domain and ACPI power management will be used for them going
forward. Then, acpi_dev_pm_detach() may be used to remove the
devices from the general ACPI PM domain if ACPI power management
is not necessary for them any more.
(2) The devices' subsystems may use acpi_subsys_runtime_suspend(),
acpi_subsys_runtime_resume(), acpi_subsys_prepare(),
acpi_subsys_suspend_late(), acpi_subsys_resume_early() as their
power management callbacks in the same way as the general ACPI
PM domain does that.
(3) The devices' drivers may execute acpi_dev_suspend_late(),
acpi_dev_resume_early(), acpi_dev_runtime_suspend(),
acpi_dev_runtime_resume() from their power management callbacks
as appropriate, if that's absolutely necessary, but it is not
recommended to do that, because such drivers may not work
without ACPI support as a result.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:41:01 +00:00
|
|
|
{
|
|
|
|
acpi_handle handle = DEVICE_ACPI_HANDLE(dev);
|
|
|
|
struct acpi_device *adev;
|
|
|
|
|
2012-12-16 22:28:53 +00:00
|
|
|
return handle && !acpi_bus_get_device(handle, &adev) ? adev : NULL;
|
ACPI / PM: Provide ACPI PM callback routines for subsystems
Some bus types don't support power management natively, but generally
there may be device nodes in ACPI tables corresponding to the devices
whose bus types they are (under ACPI 5 those bus types may be SPI,
I2C and platform). If that is the case, standard ACPI power
management may be applied to those devices, although currently the
kernel has no means for that.
For this reason, provide a set of routines that may be used as power
management callbacks for such devices. This may be done in three
different ways.
(1) Device drivers handling the devices in question may run
acpi_dev_pm_attach() in their .probe() routines, which (on
success) will cause the devices to be added to the general ACPI
PM domain and ACPI power management will be used for them going
forward. Then, acpi_dev_pm_detach() may be used to remove the
devices from the general ACPI PM domain if ACPI power management
is not necessary for them any more.
(2) The devices' subsystems may use acpi_subsys_runtime_suspend(),
acpi_subsys_runtime_resume(), acpi_subsys_prepare(),
acpi_subsys_suspend_late(), acpi_subsys_resume_early() as their
power management callbacks in the same way as the general ACPI
PM domain does that.
(3) The devices' drivers may execute acpi_dev_suspend_late(),
acpi_dev_resume_early(), acpi_dev_runtime_suspend(),
acpi_dev_runtime_resume() from their power management callbacks
as appropriate, if that's absolutely necessary, but it is not
recommended to do that, because such drivers may not work
without ACPI support as a result.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:41:01 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_dev_pm_low_power - Put ACPI device into a low-power state.
|
|
|
|
* @dev: Device to put into a low-power state.
|
|
|
|
* @adev: ACPI device node corresponding to @dev.
|
|
|
|
* @system_state: System state to choose the device state for.
|
|
|
|
*/
|
|
|
|
static int acpi_dev_pm_low_power(struct device *dev, struct acpi_device *adev,
|
|
|
|
u32 system_state)
|
|
|
|
{
|
|
|
|
int power_state;
|
|
|
|
|
|
|
|
if (!acpi_device_power_manageable(adev))
|
|
|
|
return 0;
|
|
|
|
|
2013-06-15 22:37:42 +00:00
|
|
|
power_state = acpi_dev_pm_get_state(dev, adev, system_state,
|
|
|
|
ACPI_STATE_D3, NULL);
|
ACPI / PM: Provide ACPI PM callback routines for subsystems
Some bus types don't support power management natively, but generally
there may be device nodes in ACPI tables corresponding to the devices
whose bus types they are (under ACPI 5 those bus types may be SPI,
I2C and platform). If that is the case, standard ACPI power
management may be applied to those devices, although currently the
kernel has no means for that.
For this reason, provide a set of routines that may be used as power
management callbacks for such devices. This may be done in three
different ways.
(1) Device drivers handling the devices in question may run
acpi_dev_pm_attach() in their .probe() routines, which (on
success) will cause the devices to be added to the general ACPI
PM domain and ACPI power management will be used for them going
forward. Then, acpi_dev_pm_detach() may be used to remove the
devices from the general ACPI PM domain if ACPI power management
is not necessary for them any more.
(2) The devices' subsystems may use acpi_subsys_runtime_suspend(),
acpi_subsys_runtime_resume(), acpi_subsys_prepare(),
acpi_subsys_suspend_late(), acpi_subsys_resume_early() as their
power management callbacks in the same way as the general ACPI
PM domain does that.
(3) The devices' drivers may execute acpi_dev_suspend_late(),
acpi_dev_resume_early(), acpi_dev_runtime_suspend(),
acpi_dev_runtime_resume() from their power management callbacks
as appropriate, if that's absolutely necessary, but it is not
recommended to do that, because such drivers may not work
without ACPI support as a result.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:41:01 +00:00
|
|
|
if (power_state < ACPI_STATE_D0 || power_state > ACPI_STATE_D3)
|
|
|
|
return -EIO;
|
|
|
|
|
|
|
|
return acpi_device_set_power(adev, power_state);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_dev_pm_full_power - Put ACPI device into the full-power state.
|
|
|
|
* @adev: ACPI device node to put into the full-power state.
|
|
|
|
*/
|
|
|
|
static int acpi_dev_pm_full_power(struct acpi_device *adev)
|
|
|
|
{
|
|
|
|
return acpi_device_power_manageable(adev) ?
|
|
|
|
acpi_device_set_power(adev, ACPI_STATE_D0) : 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
#ifdef CONFIG_PM_RUNTIME
|
|
|
|
/**
|
|
|
|
* acpi_dev_runtime_suspend - Put device into a low-power state using ACPI.
|
|
|
|
* @dev: Device to put into a low-power state.
|
|
|
|
*
|
|
|
|
* Put the given device into a runtime low-power state using the standard ACPI
|
|
|
|
* mechanism. Set up remote wakeup if desired, choose the state to put the
|
|
|
|
* device into (this checks if remote wakeup is expected to work too), and set
|
|
|
|
* the power state of the device.
|
|
|
|
*/
|
|
|
|
int acpi_dev_runtime_suspend(struct device *dev)
|
|
|
|
{
|
|
|
|
struct acpi_device *adev = acpi_dev_pm_get_node(dev);
|
|
|
|
bool remote_wakeup;
|
|
|
|
int error;
|
|
|
|
|
|
|
|
if (!adev)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
remote_wakeup = dev_pm_qos_flags(dev, PM_QOS_FLAG_REMOTE_WAKEUP) >
|
|
|
|
PM_QOS_FLAGS_NONE;
|
|
|
|
error = __acpi_device_run_wake(adev, remote_wakeup);
|
|
|
|
if (remote_wakeup && error)
|
|
|
|
return -EAGAIN;
|
|
|
|
|
|
|
|
error = acpi_dev_pm_low_power(dev, adev, ACPI_STATE_S0);
|
|
|
|
if (error)
|
|
|
|
__acpi_device_run_wake(adev, false);
|
|
|
|
|
|
|
|
return error;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(acpi_dev_runtime_suspend);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_dev_runtime_resume - Put device into the full-power state using ACPI.
|
|
|
|
* @dev: Device to put into the full-power state.
|
|
|
|
*
|
|
|
|
* Put the given device into the full-power state using the standard ACPI
|
|
|
|
* mechanism at run time. Set the power state of the device to ACPI D0 and
|
|
|
|
* disable remote wakeup.
|
|
|
|
*/
|
|
|
|
int acpi_dev_runtime_resume(struct device *dev)
|
|
|
|
{
|
|
|
|
struct acpi_device *adev = acpi_dev_pm_get_node(dev);
|
|
|
|
int error;
|
|
|
|
|
|
|
|
if (!adev)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
error = acpi_dev_pm_full_power(adev);
|
|
|
|
__acpi_device_run_wake(adev, false);
|
|
|
|
return error;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(acpi_dev_runtime_resume);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_subsys_runtime_suspend - Suspend device using ACPI.
|
|
|
|
* @dev: Device to suspend.
|
|
|
|
*
|
|
|
|
* Carry out the generic runtime suspend procedure for @dev and use ACPI to put
|
|
|
|
* it into a runtime low-power state.
|
|
|
|
*/
|
|
|
|
int acpi_subsys_runtime_suspend(struct device *dev)
|
|
|
|
{
|
|
|
|
int ret = pm_generic_runtime_suspend(dev);
|
|
|
|
return ret ? ret : acpi_dev_runtime_suspend(dev);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(acpi_subsys_runtime_suspend);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_subsys_runtime_resume - Resume device using ACPI.
|
|
|
|
* @dev: Device to Resume.
|
|
|
|
*
|
|
|
|
* Use ACPI to put the given device into the full-power state and carry out the
|
|
|
|
* generic runtime resume procedure for it.
|
|
|
|
*/
|
|
|
|
int acpi_subsys_runtime_resume(struct device *dev)
|
|
|
|
{
|
|
|
|
int ret = acpi_dev_runtime_resume(dev);
|
|
|
|
return ret ? ret : pm_generic_runtime_resume(dev);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(acpi_subsys_runtime_resume);
|
|
|
|
#endif /* CONFIG_PM_RUNTIME */
|
|
|
|
|
|
|
|
#ifdef CONFIG_PM_SLEEP
|
|
|
|
/**
|
|
|
|
* acpi_dev_suspend_late - Put device into a low-power state using ACPI.
|
|
|
|
* @dev: Device to put into a low-power state.
|
|
|
|
*
|
|
|
|
* Put the given device into a low-power state during system transition to a
|
|
|
|
* sleep state using the standard ACPI mechanism. Set up system wakeup if
|
|
|
|
* desired, choose the state to put the device into (this checks if system
|
|
|
|
* wakeup is expected to work too), and set the power state of the device.
|
|
|
|
*/
|
|
|
|
int acpi_dev_suspend_late(struct device *dev)
|
|
|
|
{
|
|
|
|
struct acpi_device *adev = acpi_dev_pm_get_node(dev);
|
|
|
|
u32 target_state;
|
|
|
|
bool wakeup;
|
|
|
|
int error;
|
|
|
|
|
|
|
|
if (!adev)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
target_state = acpi_target_system_state();
|
|
|
|
wakeup = device_may_wakeup(dev);
|
|
|
|
error = __acpi_device_sleep_wake(adev, target_state, wakeup);
|
|
|
|
if (wakeup && error)
|
|
|
|
return error;
|
|
|
|
|
|
|
|
error = acpi_dev_pm_low_power(dev, adev, target_state);
|
|
|
|
if (error)
|
|
|
|
__acpi_device_sleep_wake(adev, ACPI_STATE_UNKNOWN, false);
|
|
|
|
|
|
|
|
return error;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(acpi_dev_suspend_late);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_dev_resume_early - Put device into the full-power state using ACPI.
|
|
|
|
* @dev: Device to put into the full-power state.
|
|
|
|
*
|
|
|
|
* Put the given device into the full-power state using the standard ACPI
|
|
|
|
* mechanism during system transition to the working state. Set the power
|
|
|
|
* state of the device to ACPI D0 and disable remote wakeup.
|
|
|
|
*/
|
|
|
|
int acpi_dev_resume_early(struct device *dev)
|
|
|
|
{
|
|
|
|
struct acpi_device *adev = acpi_dev_pm_get_node(dev);
|
|
|
|
int error;
|
|
|
|
|
|
|
|
if (!adev)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
error = acpi_dev_pm_full_power(adev);
|
|
|
|
__acpi_device_sleep_wake(adev, ACPI_STATE_UNKNOWN, false);
|
|
|
|
return error;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(acpi_dev_resume_early);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_subsys_prepare - Prepare device for system transition to a sleep state.
|
|
|
|
* @dev: Device to prepare.
|
|
|
|
*/
|
|
|
|
int acpi_subsys_prepare(struct device *dev)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* Follow PCI and resume devices suspended at run time before running
|
|
|
|
* their system suspend callbacks.
|
|
|
|
*/
|
|
|
|
pm_runtime_resume(dev);
|
|
|
|
return pm_generic_prepare(dev);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(acpi_subsys_prepare);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_subsys_suspend_late - Suspend device using ACPI.
|
|
|
|
* @dev: Device to suspend.
|
|
|
|
*
|
|
|
|
* Carry out the generic late suspend procedure for @dev and use ACPI to put
|
|
|
|
* it into a low-power state during system transition into a sleep state.
|
|
|
|
*/
|
|
|
|
int acpi_subsys_suspend_late(struct device *dev)
|
|
|
|
{
|
|
|
|
int ret = pm_generic_suspend_late(dev);
|
|
|
|
return ret ? ret : acpi_dev_suspend_late(dev);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(acpi_subsys_suspend_late);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_subsys_resume_early - Resume device using ACPI.
|
|
|
|
* @dev: Device to Resume.
|
|
|
|
*
|
|
|
|
* Use ACPI to put the given device into the full-power state and carry out the
|
|
|
|
* generic early resume procedure for it during system transition into the
|
|
|
|
* working state.
|
|
|
|
*/
|
|
|
|
int acpi_subsys_resume_early(struct device *dev)
|
|
|
|
{
|
|
|
|
int ret = acpi_dev_resume_early(dev);
|
|
|
|
return ret ? ret : pm_generic_resume_early(dev);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(acpi_subsys_resume_early);
|
|
|
|
#endif /* CONFIG_PM_SLEEP */
|
|
|
|
|
|
|
|
static struct dev_pm_domain acpi_general_pm_domain = {
|
|
|
|
.ops = {
|
|
|
|
#ifdef CONFIG_PM_RUNTIME
|
|
|
|
.runtime_suspend = acpi_subsys_runtime_suspend,
|
|
|
|
.runtime_resume = acpi_subsys_runtime_resume,
|
|
|
|
.runtime_idle = pm_generic_runtime_idle,
|
|
|
|
#endif
|
|
|
|
#ifdef CONFIG_PM_SLEEP
|
|
|
|
.prepare = acpi_subsys_prepare,
|
|
|
|
.suspend_late = acpi_subsys_suspend_late,
|
|
|
|
.resume_early = acpi_subsys_resume_early,
|
|
|
|
.poweroff_late = acpi_subsys_suspend_late,
|
|
|
|
.restore_early = acpi_subsys_resume_early,
|
|
|
|
#endif
|
|
|
|
},
|
|
|
|
};
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_dev_pm_attach - Prepare device for ACPI power management.
|
|
|
|
* @dev: Device to prepare.
|
2012-11-26 09:03:06 +00:00
|
|
|
* @power_on: Whether or not to power on the device.
|
ACPI / PM: Provide ACPI PM callback routines for subsystems
Some bus types don't support power management natively, but generally
there may be device nodes in ACPI tables corresponding to the devices
whose bus types they are (under ACPI 5 those bus types may be SPI,
I2C and platform). If that is the case, standard ACPI power
management may be applied to those devices, although currently the
kernel has no means for that.
For this reason, provide a set of routines that may be used as power
management callbacks for such devices. This may be done in three
different ways.
(1) Device drivers handling the devices in question may run
acpi_dev_pm_attach() in their .probe() routines, which (on
success) will cause the devices to be added to the general ACPI
PM domain and ACPI power management will be used for them going
forward. Then, acpi_dev_pm_detach() may be used to remove the
devices from the general ACPI PM domain if ACPI power management
is not necessary for them any more.
(2) The devices' subsystems may use acpi_subsys_runtime_suspend(),
acpi_subsys_runtime_resume(), acpi_subsys_prepare(),
acpi_subsys_suspend_late(), acpi_subsys_resume_early() as their
power management callbacks in the same way as the general ACPI
PM domain does that.
(3) The devices' drivers may execute acpi_dev_suspend_late(),
acpi_dev_resume_early(), acpi_dev_runtime_suspend(),
acpi_dev_runtime_resume() from their power management callbacks
as appropriate, if that's absolutely necessary, but it is not
recommended to do that, because such drivers may not work
without ACPI support as a result.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:41:01 +00:00
|
|
|
*
|
|
|
|
* If @dev has a valid ACPI handle that has a valid struct acpi_device object
|
|
|
|
* attached to it, install a wakeup notification handler for the device and
|
2012-11-26 09:03:06 +00:00
|
|
|
* add it to the general ACPI PM domain. If @power_on is set, the device will
|
|
|
|
* be put into the ACPI D0 state before the function returns.
|
ACPI / PM: Provide ACPI PM callback routines for subsystems
Some bus types don't support power management natively, but generally
there may be device nodes in ACPI tables corresponding to the devices
whose bus types they are (under ACPI 5 those bus types may be SPI,
I2C and platform). If that is the case, standard ACPI power
management may be applied to those devices, although currently the
kernel has no means for that.
For this reason, provide a set of routines that may be used as power
management callbacks for such devices. This may be done in three
different ways.
(1) Device drivers handling the devices in question may run
acpi_dev_pm_attach() in their .probe() routines, which (on
success) will cause the devices to be added to the general ACPI
PM domain and ACPI power management will be used for them going
forward. Then, acpi_dev_pm_detach() may be used to remove the
devices from the general ACPI PM domain if ACPI power management
is not necessary for them any more.
(2) The devices' subsystems may use acpi_subsys_runtime_suspend(),
acpi_subsys_runtime_resume(), acpi_subsys_prepare(),
acpi_subsys_suspend_late(), acpi_subsys_resume_early() as their
power management callbacks in the same way as the general ACPI
PM domain does that.
(3) The devices' drivers may execute acpi_dev_suspend_late(),
acpi_dev_resume_early(), acpi_dev_runtime_suspend(),
acpi_dev_runtime_resume() from their power management callbacks
as appropriate, if that's absolutely necessary, but it is not
recommended to do that, because such drivers may not work
without ACPI support as a result.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:41:01 +00:00
|
|
|
*
|
|
|
|
* This assumes that the @dev's bus type uses generic power management callbacks
|
|
|
|
* (or doesn't use any power management callbacks at all).
|
|
|
|
*
|
|
|
|
* Callers must ensure proper synchronization of this function with power
|
|
|
|
* management callbacks.
|
|
|
|
*/
|
2012-11-26 09:03:06 +00:00
|
|
|
int acpi_dev_pm_attach(struct device *dev, bool power_on)
|
ACPI / PM: Provide ACPI PM callback routines for subsystems
Some bus types don't support power management natively, but generally
there may be device nodes in ACPI tables corresponding to the devices
whose bus types they are (under ACPI 5 those bus types may be SPI,
I2C and platform). If that is the case, standard ACPI power
management may be applied to those devices, although currently the
kernel has no means for that.
For this reason, provide a set of routines that may be used as power
management callbacks for such devices. This may be done in three
different ways.
(1) Device drivers handling the devices in question may run
acpi_dev_pm_attach() in their .probe() routines, which (on
success) will cause the devices to be added to the general ACPI
PM domain and ACPI power management will be used for them going
forward. Then, acpi_dev_pm_detach() may be used to remove the
devices from the general ACPI PM domain if ACPI power management
is not necessary for them any more.
(2) The devices' subsystems may use acpi_subsys_runtime_suspend(),
acpi_subsys_runtime_resume(), acpi_subsys_prepare(),
acpi_subsys_suspend_late(), acpi_subsys_resume_early() as their
power management callbacks in the same way as the general ACPI
PM domain does that.
(3) The devices' drivers may execute acpi_dev_suspend_late(),
acpi_dev_resume_early(), acpi_dev_runtime_suspend(),
acpi_dev_runtime_resume() from their power management callbacks
as appropriate, if that's absolutely necessary, but it is not
recommended to do that, because such drivers may not work
without ACPI support as a result.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:41:01 +00:00
|
|
|
{
|
|
|
|
struct acpi_device *adev = acpi_dev_pm_get_node(dev);
|
|
|
|
|
|
|
|
if (!adev)
|
|
|
|
return -ENODEV;
|
|
|
|
|
|
|
|
if (dev->pm_domain)
|
|
|
|
return -EEXIST;
|
|
|
|
|
|
|
|
acpi_add_pm_notifier(adev, acpi_wakeup_device, dev);
|
|
|
|
dev->pm_domain = &acpi_general_pm_domain;
|
2012-11-26 09:03:06 +00:00
|
|
|
if (power_on) {
|
|
|
|
acpi_dev_pm_full_power(adev);
|
|
|
|
__acpi_device_run_wake(adev, false);
|
|
|
|
}
|
ACPI / PM: Provide ACPI PM callback routines for subsystems
Some bus types don't support power management natively, but generally
there may be device nodes in ACPI tables corresponding to the devices
whose bus types they are (under ACPI 5 those bus types may be SPI,
I2C and platform). If that is the case, standard ACPI power
management may be applied to those devices, although currently the
kernel has no means for that.
For this reason, provide a set of routines that may be used as power
management callbacks for such devices. This may be done in three
different ways.
(1) Device drivers handling the devices in question may run
acpi_dev_pm_attach() in their .probe() routines, which (on
success) will cause the devices to be added to the general ACPI
PM domain and ACPI power management will be used for them going
forward. Then, acpi_dev_pm_detach() may be used to remove the
devices from the general ACPI PM domain if ACPI power management
is not necessary for them any more.
(2) The devices' subsystems may use acpi_subsys_runtime_suspend(),
acpi_subsys_runtime_resume(), acpi_subsys_prepare(),
acpi_subsys_suspend_late(), acpi_subsys_resume_early() as their
power management callbacks in the same way as the general ACPI
PM domain does that.
(3) The devices' drivers may execute acpi_dev_suspend_late(),
acpi_dev_resume_early(), acpi_dev_runtime_suspend(),
acpi_dev_runtime_resume() from their power management callbacks
as appropriate, if that's absolutely necessary, but it is not
recommended to do that, because such drivers may not work
without ACPI support as a result.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:41:01 +00:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(acpi_dev_pm_attach);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_dev_pm_detach - Remove ACPI power management from the device.
|
|
|
|
* @dev: Device to take care of.
|
2012-11-26 09:03:06 +00:00
|
|
|
* @power_off: Whether or not to try to remove power from the device.
|
ACPI / PM: Provide ACPI PM callback routines for subsystems
Some bus types don't support power management natively, but generally
there may be device nodes in ACPI tables corresponding to the devices
whose bus types they are (under ACPI 5 those bus types may be SPI,
I2C and platform). If that is the case, standard ACPI power
management may be applied to those devices, although currently the
kernel has no means for that.
For this reason, provide a set of routines that may be used as power
management callbacks for such devices. This may be done in three
different ways.
(1) Device drivers handling the devices in question may run
acpi_dev_pm_attach() in their .probe() routines, which (on
success) will cause the devices to be added to the general ACPI
PM domain and ACPI power management will be used for them going
forward. Then, acpi_dev_pm_detach() may be used to remove the
devices from the general ACPI PM domain if ACPI power management
is not necessary for them any more.
(2) The devices' subsystems may use acpi_subsys_runtime_suspend(),
acpi_subsys_runtime_resume(), acpi_subsys_prepare(),
acpi_subsys_suspend_late(), acpi_subsys_resume_early() as their
power management callbacks in the same way as the general ACPI
PM domain does that.
(3) The devices' drivers may execute acpi_dev_suspend_late(),
acpi_dev_resume_early(), acpi_dev_runtime_suspend(),
acpi_dev_runtime_resume() from their power management callbacks
as appropriate, if that's absolutely necessary, but it is not
recommended to do that, because such drivers may not work
without ACPI support as a result.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:41:01 +00:00
|
|
|
*
|
|
|
|
* Remove the device from the general ACPI PM domain and remove its wakeup
|
2012-11-26 09:03:06 +00:00
|
|
|
* notifier. If @power_off is set, additionally remove power from the device if
|
|
|
|
* possible.
|
ACPI / PM: Provide ACPI PM callback routines for subsystems
Some bus types don't support power management natively, but generally
there may be device nodes in ACPI tables corresponding to the devices
whose bus types they are (under ACPI 5 those bus types may be SPI,
I2C and platform). If that is the case, standard ACPI power
management may be applied to those devices, although currently the
kernel has no means for that.
For this reason, provide a set of routines that may be used as power
management callbacks for such devices. This may be done in three
different ways.
(1) Device drivers handling the devices in question may run
acpi_dev_pm_attach() in their .probe() routines, which (on
success) will cause the devices to be added to the general ACPI
PM domain and ACPI power management will be used for them going
forward. Then, acpi_dev_pm_detach() may be used to remove the
devices from the general ACPI PM domain if ACPI power management
is not necessary for them any more.
(2) The devices' subsystems may use acpi_subsys_runtime_suspend(),
acpi_subsys_runtime_resume(), acpi_subsys_prepare(),
acpi_subsys_suspend_late(), acpi_subsys_resume_early() as their
power management callbacks in the same way as the general ACPI
PM domain does that.
(3) The devices' drivers may execute acpi_dev_suspend_late(),
acpi_dev_resume_early(), acpi_dev_runtime_suspend(),
acpi_dev_runtime_resume() from their power management callbacks
as appropriate, if that's absolutely necessary, but it is not
recommended to do that, because such drivers may not work
without ACPI support as a result.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:41:01 +00:00
|
|
|
*
|
|
|
|
* Callers must ensure proper synchronization of this function with power
|
|
|
|
* management callbacks.
|
|
|
|
*/
|
2012-11-26 09:03:06 +00:00
|
|
|
void acpi_dev_pm_detach(struct device *dev, bool power_off)
|
ACPI / PM: Provide ACPI PM callback routines for subsystems
Some bus types don't support power management natively, but generally
there may be device nodes in ACPI tables corresponding to the devices
whose bus types they are (under ACPI 5 those bus types may be SPI,
I2C and platform). If that is the case, standard ACPI power
management may be applied to those devices, although currently the
kernel has no means for that.
For this reason, provide a set of routines that may be used as power
management callbacks for such devices. This may be done in three
different ways.
(1) Device drivers handling the devices in question may run
acpi_dev_pm_attach() in their .probe() routines, which (on
success) will cause the devices to be added to the general ACPI
PM domain and ACPI power management will be used for them going
forward. Then, acpi_dev_pm_detach() may be used to remove the
devices from the general ACPI PM domain if ACPI power management
is not necessary for them any more.
(2) The devices' subsystems may use acpi_subsys_runtime_suspend(),
acpi_subsys_runtime_resume(), acpi_subsys_prepare(),
acpi_subsys_suspend_late(), acpi_subsys_resume_early() as their
power management callbacks in the same way as the general ACPI
PM domain does that.
(3) The devices' drivers may execute acpi_dev_suspend_late(),
acpi_dev_resume_early(), acpi_dev_runtime_suspend(),
acpi_dev_runtime_resume() from their power management callbacks
as appropriate, if that's absolutely necessary, but it is not
recommended to do that, because such drivers may not work
without ACPI support as a result.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:41:01 +00:00
|
|
|
{
|
|
|
|
struct acpi_device *adev = acpi_dev_pm_get_node(dev);
|
|
|
|
|
|
|
|
if (adev && dev->pm_domain == &acpi_general_pm_domain) {
|
|
|
|
dev->pm_domain = NULL;
|
|
|
|
acpi_remove_pm_notifier(adev, acpi_wakeup_device);
|
2012-11-26 09:03:06 +00:00
|
|
|
if (power_off) {
|
|
|
|
/*
|
|
|
|
* If the device's PM QoS resume latency limit or flags
|
|
|
|
* have been exposed to user space, they have to be
|
|
|
|
* hidden at this point, so that they don't affect the
|
|
|
|
* choice of the low-power state to put the device into.
|
|
|
|
*/
|
|
|
|
dev_pm_qos_hide_latency_limit(dev);
|
|
|
|
dev_pm_qos_hide_flags(dev);
|
|
|
|
__acpi_device_run_wake(adev, false);
|
|
|
|
acpi_dev_pm_low_power(dev, adev, ACPI_STATE_S0);
|
|
|
|
}
|
ACPI / PM: Provide ACPI PM callback routines for subsystems
Some bus types don't support power management natively, but generally
there may be device nodes in ACPI tables corresponding to the devices
whose bus types they are (under ACPI 5 those bus types may be SPI,
I2C and platform). If that is the case, standard ACPI power
management may be applied to those devices, although currently the
kernel has no means for that.
For this reason, provide a set of routines that may be used as power
management callbacks for such devices. This may be done in three
different ways.
(1) Device drivers handling the devices in question may run
acpi_dev_pm_attach() in their .probe() routines, which (on
success) will cause the devices to be added to the general ACPI
PM domain and ACPI power management will be used for them going
forward. Then, acpi_dev_pm_detach() may be used to remove the
devices from the general ACPI PM domain if ACPI power management
is not necessary for them any more.
(2) The devices' subsystems may use acpi_subsys_runtime_suspend(),
acpi_subsys_runtime_resume(), acpi_subsys_prepare(),
acpi_subsys_suspend_late(), acpi_subsys_resume_early() as their
power management callbacks in the same way as the general ACPI
PM domain does that.
(3) The devices' drivers may execute acpi_dev_suspend_late(),
acpi_dev_resume_early(), acpi_dev_runtime_suspend(),
acpi_dev_runtime_resume() from their power management callbacks
as appropriate, if that's absolutely necessary, but it is not
recommended to do that, because such drivers may not work
without ACPI support as a result.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2012-11-02 00:41:01 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(acpi_dev_pm_detach);
|
ACPI / PM: Rework the handling of devices depending on power resources
Commit 0090def6 (ACPI: Add interface to register/unregister device
to/from power resources) made it possible to indicate to the ACPI
core that if the given device depends on any power resources, then
it should be resumed as soon as all of the power resources required
by it to transition to the D0 power state have been turned on.
Unfortunately, however, this was a mistake, because all devices
depending on power resources should be treated this way (i.e. they
should be resumed when all power resources required by their D0
state have been turned on) and for the majority of those devices
the ACPI core can figure out by itself which (physical) devices
depend on what power resources.
For this reason, replace the code added by commit 0090def6 with a
new, much more straightforward, mechanism that will be used
internally by the ACPI core and remove all references to that code
from kernel subsystems using ACPI.
For the cases when there are (physical) devices that should be
resumed whenever a not directly related ACPI device node goes into
D0 as a result of power resources configuration changes, like in
the SATA case, add two new routines, acpi_dev_pm_add_dependent()
and acpi_dev_pm_remove_dependent(), allowing subsystems to manage
such dependencies. Convert the SATA subsystem to use the new
functions accordingly.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2013-01-17 13:11:05 +00:00
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_dev_pm_add_dependent - Add physical device depending for PM.
|
|
|
|
* @handle: Handle of ACPI device node.
|
|
|
|
* @depdev: Device depending on that node for PM.
|
|
|
|
*/
|
|
|
|
void acpi_dev_pm_add_dependent(acpi_handle handle, struct device *depdev)
|
|
|
|
{
|
|
|
|
struct acpi_device_physical_node *dep;
|
|
|
|
struct acpi_device *adev;
|
|
|
|
|
|
|
|
if (!depdev || acpi_bus_get_device(handle, &adev))
|
|
|
|
return;
|
|
|
|
|
|
|
|
mutex_lock(&adev->physical_node_lock);
|
|
|
|
|
|
|
|
list_for_each_entry(dep, &adev->power_dependent, node)
|
|
|
|
if (dep->dev == depdev)
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
dep = kzalloc(sizeof(*dep), GFP_KERNEL);
|
|
|
|
if (dep) {
|
|
|
|
dep->dev = depdev;
|
|
|
|
list_add_tail(&dep->node, &adev->power_dependent);
|
|
|
|
}
|
|
|
|
|
|
|
|
out:
|
|
|
|
mutex_unlock(&adev->physical_node_lock);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(acpi_dev_pm_add_dependent);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* acpi_dev_pm_remove_dependent - Remove physical device depending for PM.
|
|
|
|
* @handle: Handle of ACPI device node.
|
|
|
|
* @depdev: Device depending on that node for PM.
|
|
|
|
*/
|
|
|
|
void acpi_dev_pm_remove_dependent(acpi_handle handle, struct device *depdev)
|
|
|
|
{
|
|
|
|
struct acpi_device_physical_node *dep;
|
|
|
|
struct acpi_device *adev;
|
|
|
|
|
|
|
|
if (!depdev || acpi_bus_get_device(handle, &adev))
|
|
|
|
return;
|
|
|
|
|
|
|
|
mutex_lock(&adev->physical_node_lock);
|
|
|
|
|
|
|
|
list_for_each_entry(dep, &adev->power_dependent, node)
|
|
|
|
if (dep->dev == depdev) {
|
|
|
|
list_del(&dep->node);
|
|
|
|
kfree(dep);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
mutex_unlock(&adev->physical_node_lock);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(acpi_dev_pm_remove_dependent);
|
2013-05-16 20:29:28 +00:00
|
|
|
#endif /* CONFIG_PM */
|