From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Lv Zheng <lv.zheng@intel.com>
Cc: Len Brown <len.brown@intel.com>,
Rafael J Wysocki <rafael.j.wysocki@intel.com>,
linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>
Subject: Re: [PATCH] ACPI / PM: Add check preventing transitioning to non-D0 state from D3.
Date: Fri, 16 Nov 2012 02:49:54 +0100 [thread overview]
Message-ID: <2072306.j28QTtV7ui@vostro.rjw.lan> (raw)
In-Reply-To: <e4ec829902580af84cddbba6e98ef54b33052b85.1352953283.git.lv.zheng@intel.com>
On Thursday, November 15, 2012 12:25:01 PM Lv Zheng wrote:
> No power transitioning from D3 state to a non-D0 state is allowed.
> This patch also cleans up device power updating code in the
> acpi_device_set_power() as it should already been updated in the
> acpi_power_transition().
>
> Signed-off-by: Lv Zheng <lv.zheng@intel.com>
> ---
> drivers/acpi/bus.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
> index 07a20ee..12c1b51 100644
> --- a/drivers/acpi/bus.c
> +++ b/drivers/acpi/bus.c
> @@ -293,6 +293,12 @@ int acpi_device_set_power(struct acpi_device *device, int state)
> " state than parent\n");
> return -ENODEV;
> }
> + if (device->parent->power.state >= ACPI_STATE_D3_HOT &&
Why parent? The device's own power state shouldn't be D3, right?
> + state != ACPI_STATE_D0) {
> + printk(KERN_WARNING PREFIX
> + "Cannot transition to non-D0 state from D3\n");
> + return -ENODEV;
> + }
I fixed up the check and moved it into the (state < device->power.state)
block, because otherwise it would prevent transitions from D3_HOT to
D3_COLD from being carried out, but they are allowed.
> /* For D3cold we should execute _PS3, not _PS4. */
> if (state == ACPI_STATE_D3_COLD)
> @@ -341,7 +347,6 @@ int acpi_device_set_power(struct acpi_device *device, int state)
> "Device [%s] failed to transition to %s\n",
> device->pnp.bus_id, state_string(state));
> else {
> - device->power.state = state;
> ACPI_DEBUG_PRINT((ACPI_DB_INFO,
> "Device [%s] transitioned to %s\n",
> device->pnp.bus_id, state_string(state)));
>
Please check the linux-next branch of linux-pm.git and see if that's what you
wanted. :-)
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2012-11-16 1:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 4:25 [PATCH] ACPI / PM: Add check preventing transitioning to non-D0 state from D3 Lv Zheng
2012-11-16 1:49 ` Rafael J. Wysocki [this message]
2012-11-19 2:31 ` Zheng, Lv
2013-01-30 17:53 ` Peter Wu
2013-01-30 21:55 ` Rafael J. Wysocki
2013-01-30 23:27 ` Rafael J. Wysocki
2013-01-31 0:58 ` 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=2072306.j28QTtV7ui@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rafael.j.wysocki@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox