From: Peter Wu <lekensteyn@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Len Brown <lenb@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [Resend][PATCH] ACPI / PM: Do not power manage devices in unknown initial states
Date: Fri, 01 Feb 2013 19:23:52 +0100 [thread overview]
Message-ID: <2135454.ENo8eA9AXp@al> (raw)
In-Reply-To: <3676077.i6vcpp7Nrn@vostro.rjw.lan>
On Thursday 31 January 2013 23:32:40 Rafael J. Wysocki wrote:
> In general, for ACPI device power management to work, the initial
> power states of devices must be known (otherwise, we wouldn't be able
> to keep track of power resources, for example). Hence, if it is
> impossible to determine the initial ACPI power states of some
> devices, they can't be regarded as power-manageable using ACPI.
>
> For this reason, modify acpi_bus_get_power_flags() to clear the
> power_manageable flag if acpi_bus_init_power() fails and add some
> extra fallback code to acpi_bus_init_power() to cover broken
> BIOSes that provide _PS0/_PS3 without _PSC for some devices.
>
> Verified to work on my HP nx6325 that has this problem.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Peter Wu <lekensteyn@gmail.com>
I applied it on top of branch linux-next of repo linux-pm.
Fixes the issue I had with bbswitch in Linux 3.8. Can a backport patch be made
available for 3.8?
Regards,
Peter
next prev parent reply other threads:[~2013-02-01 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 22:32 [Resend][PATCH] ACPI / PM: Do not power manage devices in unknown initial states Rafael J. Wysocki
2013-02-01 18:23 ` Peter Wu [this message]
2013-02-01 21:44 ` Rafael J. Wysocki
2013-03-04 14:37 ` Peter Wu
2013-03-09 12:09 ` Peter Wu
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=2135454.ENo8eA9AXp@al \
--to=lekensteyn@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--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