From: Lan Tianyu <tianyu.lan@intel.com>
To: lenb@kernel.org, rjw@rjwysocki.net
Cc: Lan Tianyu <tianyu.lan@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 3/3] ACPI/POWER: Call acpi_power_resume_dependent() directly in the acpi_power_on_unlocked()
Date: Tue, 15 Oct 2013 23:12:36 +0800 [thread overview]
Message-ID: <525D5B64.3090206@intel.com> (raw)
In-Reply-To: <1381849493-7977-4-git-send-email-tianyu.lan@intel.com>
On 10/15/2013 11:04 PM, Lan Tianyu wrote:
> acpi_power_resume_dependent() purposes to resume power resource's dependent
> physical devices after turning on the related power resource. But current
> it runs in the workqueue, pm_request_resume() can't check the right
> runtime pm state just after turning on power resource. This will cause
> infinite loop between resume and suspend in some cases that turn on power
> resource in the pm runtime resume callback(e,g usb port). This patch is to
> fix the issue via calling acpi_power_resume_dependent() directly instead
> of running it in a workqueue.
>
> Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
> ---
> drivers/acpi/power.c | 15 ++-------------
> 1 file changed, 2 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/acpi/power.c b/drivers/acpi/power.c
> index 3fc2873..5e4991b 100644
> --- a/drivers/acpi/power.c
> +++ b/drivers/acpi/power.c
> @@ -62,7 +62,6 @@ ACPI_MODULE_NAME("power");
> struct acpi_power_dependent_device {
> struct list_head node;
> struct acpi_device *adev;
> - struct work_struct work;
> };
>
> struct acpi_power_resource {
> @@ -235,14 +234,12 @@ static int acpi_power_get_list_state(struct list_head *list, int *state)
> return 0;
> }
>
> -static void acpi_power_resume_dependent(struct work_struct *work)
> +static void acpi_power_resume_dependent(struct acpi_power_dependent_device *dep)
> {
> - struct acpi_power_dependent_device *dep;
> struct acpi_device_physical_node *pn;
> struct acpi_device *adev;
> int state;
>
> - dep = container_of(work, struct acpi_power_dependent_device, work);
> adev = dep->adev;
> if (acpi_power_get_inferred_state(adev, &state))
> return;
> @@ -294,7 +291,7 @@ static int acpi_power_on_unlocked(struct acpi_power_resource *resource)
> struct acpi_power_dependent_device *dep;
>
> list_for_each_entry(dep, &resource->dependent, node)
> - schedule_work(&dep->work);
> + acpi_power_resume_dependent(dep);
> }
> }
> return result;
> @@ -414,7 +411,6 @@ static void acpi_power_add_dependent(struct acpi_power_resource *resource,
> goto out;
>
> dep->adev = adev;
> - INIT_WORK(&dep->work, acpi_power_resume_dependent);
> list_add_tail(&dep->node, &resource->dependent);
>
> out:
> @@ -425,23 +421,16 @@ static void acpi_power_remove_dependent(struct acpi_power_resource *resource,
> struct acpi_device *adev)
> {
> struct acpi_power_dependent_device *dep;
> - struct work_struct *work = NULL;
>
> mutex_lock(&resource->resource_lock);
>
> list_for_each_entry(dep, &resource->dependent, node)
> if (dep->adev == adev) {
> list_del(&dep->node);
> - work = &dep->work;
Sorry, Just find forget to free dep Here. Will update if this patchset
is acceptable.
> break;
> }
>
> mutex_unlock(&resource->resource_lock);
> -
> - if (work) {
> - cancel_work_sync(work);
> - kfree(dep);
> - }
> }
>
> static struct attribute *attrs[] = {
>
next prev parent reply other threads:[~2013-10-15 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 15:04 [RFC PATCH 0/3] ACPI/Power: Fix infinite loop of runtime resume and suspend caused by turning on power resource Lan Tianyu
2013-10-15 15:04 ` [RFC PATCH 1/3] ACPI/Power: Add state_lock to mutex power resource's _ON, _OFF and _STA Lan Tianyu
2013-10-15 15:04 ` [RFC PATCH 2/3] ACPI/POWER: Rework acpi_power_get_state() Lan Tianyu
2013-10-15 15:04 ` [RFC PATCH 3/3] ACPI/POWER: Call acpi_power_resume_dependent() directly in the acpi_power_on_unlocked() Lan Tianyu
2013-10-15 15:12 ` Lan Tianyu [this message]
2013-10-15 21:05 ` [RFC PATCH 0/3] ACPI/Power: Fix infinite loop of runtime resume and suspend caused by turning on power resource Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=525D5B64.3090206@intel.com \
--to=tianyu.lan@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.