From: David Henningsson <david.henningsson@canonical.com>
To: mengdong.lin@intel.com
Cc: tiwai@suse.de, alsa-devel@alsa-project.org
Subject: Re: [RFC PATCH 1/1] ALSA: hda - add a timer to find and suspend idle codecs
Date: Tue, 14 Aug 2012 12:05:15 +0200 [thread overview]
Message-ID: <502A22DB.5010503@canonical.com> (raw)
In-Reply-To: <1344967003-5470-1-git-send-email-mengdong.lin@intel.com>
On 08/14/2012 07:56 PM, mengdong.lin@intel.com wrote:
> From: Mengdong Lin <mengdong.lin@intel.com>
>
> This patch sets up a timer to monitor changes of the parameter 'power_save'
> and suspend any idle codecs if power save is re-enabled by the user.
Adding timers means are you adding wakeups to the CPU. That seems
counterproductive if you're trying to save power...?
Is there no way to listen to a change event of some sort instead?
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next prev parent reply other threads:[~2012-08-14 9:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 17:56 [RFC PATCH 1/1] ALSA: hda - add a timer to find and suspend idle codecs mengdong.lin
2012-08-14 10:05 ` David Henningsson [this message]
2012-08-14 13:42 ` Lin, Mengdong
2012-08-14 10:08 ` Jaroslav Kysela
2012-08-14 13:55 ` Lin, Mengdong
2012-08-14 10:26 ` Takashi Iwai
2012-08-14 14:35 ` Lin, Mengdong
2012-08-14 14:42 ` Takashi Iwai
2012-08-14 15:19 ` Takashi Iwai
2012-08-14 15:20 ` [PATCH 1/2] ALSA: hda - Implement snd_hda_power_sync() helper function Takashi Iwai
2012-08-14 15:21 ` [PATCH 2/2] ALSA: hda - Check the power state when power_save option is changed Takashi Iwai
2012-08-15 4:19 ` Lin, Mengdong
2012-08-15 6:58 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2012-08-14 17:44 [RFC PATCH 1/1] ALSA: hda - add a timer to find and suspend idle codecs mengdong.lin
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=502A22DB.5010503@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=mengdong.lin@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).