public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Robert Moore
	<robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Subject: Re: Re: [PATCHES] add _CST support
Date: Thu, 23 Dec 2004 01:10:24 +0100	[thread overview]
Message-ID: <20041223001024.GB8289@dominikbrodowski.de> (raw)
In-Reply-To: <1103698332.17318.170.camel@d845pe>

> I found I had to disable the bm_check to get out of C1
> on my D600.  This doesn't sound right, as bm_check
> should only have an effect on entering C3.

Huh, yes, this sounds like a bug. Can't reproduce it here, though :-(

>  cat /proc/acpi/processor/CPU0/power
> active state:            3
> max_cstate:              C42
> bus master activity:     00000000
> states:
>     1:                  type[C1] promotion[2] demotion[-] latency[001]
> usage[00000010]
>     2:                  type[C2] promotion[3] demotion[1] latency[001]
> usage[00003280]
>    *3:                  type[C3] promotion[4] demotion[2] latency[085]
> usage[00000819]
>     4:                  type[C3] promotion[-] demotion[2] latency[185]
> usage[00000000]
> 
> It appears the demotion from C4 is to C2, when one would expect C3.

Actually, this was on purpose: I think we want to leave C3-type sleep
quickly to advance bus master activity...

	Dominik


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  parent reply	other threads:[~2004-12-23  0:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-27 21:51 [PATCHES] add _CST support Dominik Brodowski
     [not found] ` <20041127215118.GA30309-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-11-27 21:56   ` Dominik Brodowski
2004-12-22  5:44   ` Len Brown
2004-12-23  0:08     ` Dominik Brodowski
     [not found]       ` <20041223000842.GA8289-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-12-23  5:02         ` Len Brown
2004-12-23 13:07           ` Pavel Machek
     [not found]             ` <20041223130723.GE731-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org>
2004-12-28  3:27               ` Len Brown
2004-12-28 17:50                 ` Dominik Brodowski
2004-12-28 21:28                 ` Pavel Machek
2004-12-22  6:52   ` Len Brown
2004-12-22 20:37     ` Len Brown
2004-12-23  0:18       ` Dominik Brodowski
     [not found]         ` <20041223001830.GC8289-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-12-23  5:30           ` Len Brown
2004-12-23  0:10     ` Dominik Brodowski [this message]
     [not found]       ` <20041223001024.GB8289-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-12-23  5:07         ` Len Brown
2004-12-22  7:22   ` Len Brown
2004-12-22 20:13     ` Len Brown

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=20041223001024.GB8289@dominikbrodowski.de \
    --to=linux-x3ehhduj6siigcdfoqap7bvvk+yq3zxh@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@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