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>
Subject: Re: [PATCH] acpi: bus: handle power manageable but no _PSC/_PRx case
Date: Fri, 7 Sep 2012 08:35:14 +0800 [thread overview]
Message-ID: <20120907003513.GA1419@mint-spring.sh.intel.com> (raw)
In-Reply-To: <201209062353.34517.rjw@sisk.pl>
On Thu, Sep 06, 2012 at 11:53:34PM +0200, Rafael J. Wysocki wrote:
> On Thursday, September 06, 2012, Rafael J. Wysocki wrote:
> > On Monday, August 27, 2012, Aaron Lu wrote:
> > > Currently, when we are trying to get the power state of an acpi device,
> > > we will do the following:
> > > If device is not power manageable, init its power state as its parent or
> > > if it does not have a parent, init as D0;
> > > If device is power manageable, evaluate _PSC and then refine with
> > > acpi_power_get_inferred_state.
> > >
> > > But there exist some devices with _PSx defined, but no _PSC or _PRx.
> > > It is power manageable, but the above method to get power state does
> > > not cover this case and its power state will be UNKNOWN(255).
> > >
> > > So change the check of power manageable to whether _PSC and _PRx
> > > defined.
> > >
> > > Signed-off-by: Aaron Lu <aaron.lu@intel.com>
> >
> > Applied to the linux-next branch of the linux-pm.git tree.
> >
> > I think it should go to -stable too and therefore it would be good to have
> > it in v3.6, so I'd like to push it to Linus for -rc5, if Len has no objections.
>
> On a second thought, perhaps the initial power state of those devices
> _should_ be "unknown", hmm?
>
> After all, we don't know what power state the device is in.
Agree here but I think this is a safe assumption that on initial system
boot, all devices should be at D0. We have already assumed this fact if
the device is not power manageable and has no parent.
And this patch just changed the condition to not judging if power
manageable but if it has _PSC or _PRx, since we will use that to know
the device's power state, so I think using _PSC or _PRx as the
condition check is more precise.
>
> Is there any practical user-visible problem this causes to happen?
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.
Thanks,
Aaron
next prev parent reply other threads:[~2012-09-07 0:35 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 [this message]
2012-09-07 11:46 ` Rafael J. Wysocki
2012-09-07 14:32 ` Aaron Lu
2012-09-07 18:32 ` Rafael J. Wysocki
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=20120907003513.GA1419@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-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 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.