From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Aaron Lu <aaron.lu@intel.com>
Cc: Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org,
Aaron Lu <aaron.lwe@gmail.com>
Subject: Re: [PATCH] acpi: bus: handle power manageable but no _PSC/_PRx case
Date: Fri, 7 Sep 2012 20:32:55 +0200 [thread overview]
Message-ID: <201209072032.55469.rjw@sisk.pl> (raw)
In-Reply-To: <504A0579.3000109@intel.com>
On Friday, September 07, 2012, Aaron Lu wrote:
> On 09/07/2012 07:46 PM, Rafael J. Wysocki wrote:
> >> Yes, on a test system, when I try to put a device into D3 cold and ACPI
> >> will complain that I can't due to its parent is in a even lower power
> >> state UNKNOWN(255), this parent device is power manageable but has no
> >> _PSC and _PRx defined.
> >
> > Perhaps we can force _PS0 for such devices to start with, so that we know
> > for sure that the initial state is D0?
>
> Sounds good, I'll update the patch, thanks for the advice.
Actually, I suppose we can do something like the appended patch instead.
I wonder if it works around the particular problem you're seeing?
Rafael
---
drivers/acpi/bus.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
Index: linux/drivers/acpi/bus.c
===================================================================
--- linux.orig/drivers/acpi/bus.c
+++ linux/drivers/acpi/bus.c
@@ -229,7 +229,16 @@ static int __acpi_bus_get_power(struct a
result = psc;
}
/* The test below covers ACPI_STATE_UNKNOWN too. */
- if (result <= ACPI_STATE_D2) {
+ if (result == ACPI_STATE_D0) {
+ /*
+ * 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)
+ device->parent->power.state = ACPI_STATE_D0;
+ } else if (result <= ACPI_STATE_D2) {
; /* Do nothing. */
} else if (device->power.flags.power_resources) {
int error = acpi_power_get_inferred_state(device, &result);
next prev parent reply other threads:[~2012-09-07 18:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 7:38 [PATCH] acpi: bus: handle power manageable but no _PSC/_PRx case Aaron Lu
2012-09-06 21:45 ` Rafael J. Wysocki
2012-09-06 21:53 ` Rafael J. Wysocki
2012-09-07 0:35 ` Aaron Lu
2012-09-07 11:46 ` Rafael J. Wysocki
2012-09-07 14:32 ` Aaron Lu
2012-09-07 18:32 ` Rafael J. Wysocki [this message]
2012-09-10 0:38 ` Aaron Lu
2012-09-10 19:48 ` Rafael J. Wysocki
2012-09-10 19:50 ` [PATCH] ACPI / PM: Infer parent power state from child if unknown Rafael J. Wysocki
2012-09-11 5:33 ` Aaron Lu
2012-09-11 20:36 ` Rafael J. Wysocki
2012-09-11 20:38 ` [PATCH] ACPI / PM: Infer parent power state from child if unknown, v2 Rafael J. Wysocki
2012-09-12 6:59 ` Aaron Lu
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=201209072032.55469.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=aaron.lu@intel.com \
--cc=aaron.lwe@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).