All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
To: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Cc: Janosch Machowinski <scotch-cGBD8117FJM@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: _CST implementation
Date: Mon, 18 Apr 2005 19:25:54 +0200	[thread overview]
Message-ID: <4263EDA2.4030106@suse.de> (raw)
In-Reply-To: <20050418120744.GG2298-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>

Bruno Ducrot wrote:
> On Fri, Apr 15, 2005 at 10:50:44PM +0200, Janosch Machowinski wrote:
...
> 
>>Oh I almost forgot another question : 
>>About the validation of the C states. At the moment it is tested if the
>>latency of C2 if under 100 and if C3 latency is under 1000 but the
>>ACPI-Spec says that "There is no latency restrictions" so why do you do
>>this ? (My notebook hat a C3 latency of 1001)
> 
> Normally you are right, but unfortunately there are still some strange
> misread of the specification by bios writters in that regard.  Therefore
> if for C3 the latency is 1001 even if given by _CST, we should disable
> it.
> 

My spec says (Revision 3.0, September 2, 2004):
The worst-case hardware latency for this state is declared in the FADT
(p. 257).

And there they say (p. 98):
The worst-case hardware latency, in microseconds, to enter and
exit a C2 state. A value > 100 indicates the system does not
support a C2 state.
The worst-case hardware latency, in microseconds, to enter and
exit a C3 state. A value > 1000 indicates the system does not
support a C3 state.

     Thomas


-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  parent reply	other threads:[~2005-04-18 17:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-15 20:50 _CST implementation Janosch Machowinski
2005-04-18 12:07 ` Bruno Ducrot
     [not found]   ` <20050418120744.GG2298-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-04-18 12:23     ` Janosch Machowinski
2005-04-18 14:21       ` Bruno Ducrot
2005-04-18 17:25     ` Thomas Renninger [this message]
     [not found]       ` <4263EDA2.4030106-l3A5Bk7waGM@public.gmane.org>
2005-04-18 17:52         ` Janosch Machowinski
2005-04-19  9:22         ` Bruno Ducrot
     [not found]           ` <20050419092251.GK2298-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-04-19 11:58             ` Thomas Renninger
     [not found]               ` <4264F251.5030705-l3A5Bk7waGM@public.gmane.org>
2005-04-19 13:45                 ` Bruno Ducrot
     [not found]                   ` <20050419134518.GL2298-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-04-19 20:05                     ` Stefan Seyfried
     [not found]                       ` <20050419200505.GE19499-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2005-04-19 20:11                         ` Rich Townsend
     [not found]                           ` <42656601.3060304-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
2005-04-20  9:45                             ` Bruno Ducrot
     [not found]                               ` <20050420094556.GN2298-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-04-22 13:00                                 ` Thomas Renninger
     [not found]                                   ` <4268F572.4090707-l3A5Bk7waGM@public.gmane.org>
2005-04-22 17:13                                     ` Janosch Machowinski

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=4263EDA2.4030106@suse.de \
    --to=trenn-l3a5bk7wagm@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org \
    --cc=scotch-cGBD8117FJM@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 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.