From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: broken bm_sts on 82801CA?
Date: Fri, 10 Oct 2003 12:35:01 -0700 (PDT) [thread overview]
Message-ID: <20031010123339.D17381@root.org> (raw)
In-Reply-To: <20031010105834.GM11391-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
On Fri, 10 Oct 2003, Ducrot Bruno wrote:
> On Wed, Oct 08, 2003 at 10:40:21AM -0700, Nate Lawson wrote:
> > However, since this code is run every time acpi_processor_idle() is
> > called, it will never enter even C2 if you have a bm_sts bit that is
> > always 1.
>
> I checked a little bit more, but I think you are wrong because
> acpi_processor_power_activate(pr, next_state), with next_state == ACPI_STATE_C2,
> will be called after the end label,
> and since pr->power.states[ACPI_STATE_C2].demotion.threshold.bm
> is always 0 we do not go to the 'then' statement at the next run if we
> were at C3 state.
Yes, I was incorrect. It should always go to C2.
-Nate
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
prev parent reply other threads:[~2003-10-10 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 6:38 broken bm_sts on 82801CA? Nate Lawson
[not found] ` <20031006233406.N4792-Y6VGUYTwhu0@public.gmane.org>
2003-10-07 8:55 ` Ducrot Bruno
[not found] ` <20031007085536.GB11391-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-10-07 18:10 ` Nate Lawson
[not found] ` <20031008123103.GG11391@poupinou.org>
[not found] ` <20031008123103.GG11391-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-10-08 16:55 ` Nate Lawson
[not found] ` <20031008095321.B10515-Y6VGUYTwhu0@public.gmane.org>
2003-10-08 17:28 ` Ducrot Bruno
[not found] ` <20031008172800.GI11391-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-10-08 17:40 ` Nate Lawson
[not found] ` <20031008103531.B10689-Y6VGUYTwhu0@public.gmane.org>
2003-10-10 10:58 ` Ducrot Bruno
[not found] ` <20031010105834.GM11391-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-10-10 19:35 ` Nate Lawson [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=20031010123339.D17381@root.org \
--to=nate-y6vguytwhu0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.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