public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Janosch Machowinski <scotch-cGBD8117FJM@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: _CST implementation
Date: Mon, 18 Apr 2005 16:21:53 +0200	[thread overview]
Message-ID: <20050418142153.GI2298@poupinou.org> (raw)
In-Reply-To: <1113827030.8500.17.camel@scotchmobil>

On Mon, Apr 18, 2005 at 02:23:50PM +0200, Janosch Machowinski wrote:
> On Mon, 2005-04-18 at 14:07 +0200, Bruno Ducrot wrote:
> > On Fri, Apr 15, 2005 at 10:50:44PM +0200, Janosch Machowinski wrote:
> > > Hey, 
> > > im new to ACPI, so please be patient with my stupid questions ;-)
> > > I spend a little time in debugging my kernel ACPI and reading the 3.0
> > > specs... Now I am wondering about some pieces of the implementation. 
> > > First of all in processor_idle.c in the funktion
> > > acpi_processor_get_power_info_cst there is a test if the power.count is
> > > less than 2. Why do you test on 2 and not on 1 ? As far 
> > > as I can see 1 would be an valid value. 
> > 
> > No.  It cant be a valid value.  Consider this case:
> > 
> > Name (_CST, Package{} {
> > 		1,
> > 		Package{} {ResourceTemplate{} {Register(SystemIO, 8, 0, 0xXXXX), 2, 40, 750}
> > })
> > 
> > 
> > There are *2* elements in the package, an integer (whose value is 1) and
> > a package defining a C2 state.
> 
> I must disagree, power.count is not a variable to test, how many
> elements are in the _CST object (that would be count), pr->power.count
> is a counter for the number ob C-States that were extracted from the
> _CST Object, therefor one C-State is a C-State and should be valid. 
>   Janosch

I think I misread what you wrote.  I was thinking you were refering to
cst->package.count

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
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

  reply	other threads:[~2005-04-18 14:21 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 [this message]
2005-04-18 17:25     ` Thomas Renninger
     [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=20050418142153.GI2298@poupinou.org \
    --to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox