On Friday, October 11, 2013 04:16:25 PM tianyu....@intel.com wrote:
> From: Lan Tianyu <tianyu....@intel.com>
>
> Currently, when one power resource is turned on, devices owning it
> will be requested to resume regardless of their runtime pm status.
> ACPI power resource maybe turn on in some devices' runtime pm
> resume callback(E.G, usb port) while turning on the power resource
> will trigger one new resume request of the device. It causes
> infinite loop between resume and suspend. This has happened on
> clearing usb port's PM Qos NO_POWER_OFF flag twice. This patch is
> to add check of physical device's runtime pm status and request resume
> if the device is suspended.
>
> Signed-off-by: Lan Tianyu <tianyu....@intel.com>
> ---
> drivers/acpi/power.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/acpi/power.c b/drivers/acpi/power.c
> index 0dbe5cd..228c138 100644
> --- a/drivers/acpi/power.c
> +++ b/drivers/acpi/power.c
> @@ -250,8 +250,10 @@ static void acpi_power_resume_dependent(struct
> work_struct *work)
>
> mutex_lock(&adev->physical_node_lock);
>
> - list_for_each_entry(pn, &adev->physical_node_list, node)
> - pm_request_resume(pn->dev);
> + list_for_each_entry(pn, &adev->physical_node_list, node) {
> + if (pm_runtime_suspended(pn->dev))
> + pm_request_resume(pn->dev);
> + }
This is racy, because the status may change right after you check it and before
you call pm_request_resume().
Besides, pm_request_resume() checks the status of the device and won't
try to resume it if it is not suspended.
>
> list_for_each_entry(pn, &adev->power_dependent, node)
> pm_request_resume(pn->dev);
Thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
