All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Pospisek <tpo2@sourcepole.ch>
To: Takashi Iwai <tiwai@suse.de>
Cc: Alsa-devel@alsa-project.org,
	David Henningsson <david.henningsson@canonical.com>
Subject: Re: 100.0% power usage of Device Audio codec (HDA) on wake
Date: Wed, 21 Nov 2012 15:15:09 +0100	[thread overview]
Message-ID: <752ffd5c0c257045c7d8b23d95ea9ffa@sourcepole.ch> (raw)
In-Reply-To: <s5hk3tgps0x.wl%tiwai@suse.de>

On Tue, 20 Nov 2012 10:01:18 +0100, Takashi Iwai <tiwai@suse.de> wrote:
> At Tue, 20 Nov 2012 09:56:19 +0100,
> David Henningsson wrote:
>> 
>> On 11/20/2012 09:32 AM, Takashi Iwai wrote:
>> > At Tue, 20 Nov 2012 09:07:21 +0100,
>> > David Henningsson wrote:
>> >>
>> >> It does put another question - from where does powertop get its
>> >> values,
>> >> and do we have to do anything on our side to make sure / aid them
>> >> being
>> >> correct?
>> >
>> > powertop checks /sys/class/sound/hwC*D*/power_{off|on}_acct files.
>> > They contain the time (in ms) how long the codec is in the power-save
>> > mode.
>> 
>> Thanks. But I have also recently seen a computer where powertop showed
a 
>> Watt number, essentially saying that the codec consumed 1.4 Watts or so

>> (I don't remember the exact number). Have you seen that too?
> 
> When 1.4W is constantly consumed even without PCM, it's a bit too
> high.  But with PCM playback, about 1W usage can be measured normally,
> I guess.

man powertop says:

--calibrate   runs powertop in calibration mode. When running on battery,
              powertop can track power consumption as well as system
              activity. When there are enough measurements,  powertop
              can  start  to  report  power  estimates.  One can get more
              accurate estimates by using this option to enable a
              calibration cycle. This will cycle through various display
              levesl and USB device activities and workloads.

So that's what powertop does I think: it estimates.
*t

  reply	other threads:[~2012-11-21 14:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16 14:23 100.0% power usage of Device Audio codec (HDA) on wake Tomas Pospisek
2012-11-16 16:04 ` Takashi Iwai
2012-11-17  0:48   ` Tomas Pospisek
2012-11-17  1:17     ` Tomas Pospisek
2012-11-17 10:53     ` Takashi Iwai
2012-11-20  6:54       ` Tomas Pospisek
2012-11-20  7:16         ` Takashi Iwai
2012-11-21 15:12           ` Tomas Pospisek
2012-11-20  8:07         ` David Henningsson
2012-11-20  8:32           ` Takashi Iwai
2012-11-20  8:56             ` David Henningsson
2012-11-20  9:01               ` Takashi Iwai
2012-11-21 14:15                 ` Tomas Pospisek [this message]
2012-11-21 14:26                   ` Takashi Iwai
2012-11-21 14:44           ` Tomas Pospisek

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=752ffd5c0c257045c7d8b23d95ea9ffa@sourcepole.ch \
    --to=tpo2@sourcepole.ch \
    --cc=Alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.com \
    --cc=tiwai@suse.de \
    /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.