All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot@poupinou.org>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
	linux-acpilinux-acpi@intel.com, cpufreq@www.linux.org.uk
Subject: Re: [PATCHSET] 0/3 Dynamic cpufreq governor and updates to ACPI P-state driver
Date: Thu, 23 Oct 2003 20:03:00 +0200	[thread overview]
Message-ID: <20031023180300.GT13989@poupinou.org> (raw)
In-Reply-To: <20031023102937.B18225@devserv.devel.redhat.com>

On Thu, Oct 23, 2003 at 10:29:37AM +0200, Arjan van de Ven wrote:
> On Thu, Oct 23, 2003 at 11:24:01AM +0300, Alexander Bokovoy wrote:
> > On Thu, Oct 23, 2003 at 10:19:44AM +0200, Arjan van de Ven wrote:
> > > On Wed, 2003-10-22 at 20:21, Pallipadi, Venkatesh wrote:
> > > 
> > > > And with the kind of power savings that comes with these frequency
> > > > changes, this behaviour 
> > > > results in  longer battery life. However, as yet I do not have any
> > > > numbers to quantify this gain, 
> > > > mainly because I do not have any setup where I can measure actual power.
> > > >  
> > > 
> > > some time ago I did this by using the ACPI method of asking the battery
> > > what the current use is at this point in time; it's of course not as
> > > exact as a full measurement setup but it's a nice poor mans power watch
> > > too ....
> > Unfortunately, there is a number of ACPI-enabled BIOSes which report wrong
> > battery rate when EST is in action -- they still continue to report a rate
> > which corresponds to highest CPU frequency despite the fact that actual
> > frequency might be the lowest one.
> 
> ok I admit to cheating and not actually using ACPI but talking
> to the battery directly based on reverse engineered info (partially based
> on the AML, mostly on "if I do this what value changes" ;)

Most modern embedded chips 'cache' results.  Better to go directly
to the smbus for those one, and talk to the smart battery slave.

-- 
Ducrot Bruno

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

  reply	other threads:[~2003-10-23 18:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-22 18:21 [PATCHSET] 0/3 Dynamic cpufreq governor and updates to ACPI P-state driver Pallipadi, Venkatesh
2003-10-23  8:19 ` Arjan van de Ven
2003-10-23  8:24   ` Alexander Bokovoy
2003-10-23  8:29     ` Arjan van de Ven
2003-10-23 18:03       ` Ducrot Bruno [this message]
2003-10-23 18:16   ` Todd Poynor
2003-10-23 18:26     ` Todd Poynor
2003-11-02 20:28 ` Jan Rychter
  -- strict thread matches above, loose matches on Subject: below --
2003-11-05 21:12 Mukesh Rajan
2003-11-04  3:14 Brown, Len
2003-11-04  3:21 ` Jan Rychter
2003-11-04  7:16   ` Dominik Brodowski
2003-10-22  1:48 Pallipadi, Venkatesh
2003-10-22  1:48 ` Pallipadi, Venkatesh
2003-10-22  1:42 Pallipadi, Venkatesh
2003-10-22  1:42 ` Pallipadi, Venkatesh
2003-10-21  2:56 Pallipadi, Venkatesh
2003-10-21  2:56 ` Pallipadi, Venkatesh
2003-10-21  8:25 ` Måns Rullgård
2003-10-21  8:25   ` Måns Rullgård
2003-10-21 20:47   ` Dominik Brodowski
2003-10-21 10:57 ` Måns Rullgård
2003-10-21 11:09   ` Måns Rullgård
2003-10-21 20:30   ` Alexander Bokovoy
2003-10-21 20:39     ` Måns Rullgård
2003-10-21 21:11       ` Alexander Bokovoy
2003-10-21 21:37         ` Måns Rullgård
2003-10-21 21:53           ` Alexander Bokovoy
2003-10-21 22:27             ` Måns Rullgård

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=20031023180300.GT13989@poupinou.org \
    --to=ducrot@poupinou.org \
    --cc=arjanv@redhat.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux-acpilinux-acpi@intel.com \
    --cc=venkatesh.pallipadi@intel.com \
    /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.