From: Aaron Lu <aaron.lu@intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org,
Aaron Lu <aaron.lwe@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI / PM: Infer parent power state from child if unknown, v2
Date: Wed, 12 Sep 2012 14:59:04 +0800 [thread overview]
Message-ID: <20120912065902.GA2229@mint-spring.sh.intel.com> (raw)
In-Reply-To: <201209112238.06658.rjw@sisk.pl>
On Tue, Sep 11, 2012 at 10:38:06PM +0200, Rafael J. Wysocki wrote:
> It turns out that there are ACPI BIOSes defining device objects with
> _PSx and without either _PSC or _PRx. For devices corresponding to
> those ACPI objetcs __acpi_bus_get_power() returns ACPI_STATE_UNKNOWN
> and their initial power states are regarded as unknown as a result.
> If such a device is a parent of another power-manageable device, the
> child cannot be put into a low-power state through ACPI, because
> __acpi_bus_set_power() refuses to change power states of devices
> whose parents' power states are unknown.
>
> To work around this problem, observe that the ACPI power state of
> a device cannot be higher-power (lower-number) than the power state
> of its parent. Thus, if the device's _PSC method or the
> configuration of its power resources indicates that the device is
> in D0, the device's parent has to be in D0 as well. Consequently,
> if the parent's power state is unknown when we've just learned that
> its child's power state is D0, we can safely set the parent's
> power.state field to ACPI_STATE_D0.
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Tested-by: Aaron Lu <aaron.lu@intel.com>
-Aaron
> ---
> drivers/acpi/bus.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> Index: linux/drivers/acpi/bus.c
> ===================================================================
> --- linux.orig/drivers/acpi/bus.c
> +++ linux/drivers/acpi/bus.c
> @@ -237,6 +237,16 @@ static int __acpi_bus_get_power(struct a
> } else if (result == ACPI_STATE_D3_HOT) {
> result = ACPI_STATE_D3;
> }
> +
> + /*
> + * 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:
prev parent reply other threads:[~2012-09-12 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1346053126-7646-1-git-send-email-aaron.lu@intel.com>
[not found] ` <201209072032.55469.rjw@sisk.pl>
[not found] ` <20120910003805.GA1590@mint-spring.sh.intel.com>
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 [this message]
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=20120912065902.GA2229@mint-spring.sh.intel.com \
--to=aaron.lu@intel.com \
--cc=aaron.lwe@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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