From: "Wang, Xingchao" <xingchao.wang@intel.com>
To: 'Takashi Iwai' <tiwai@suse.de>
Cc: "'alsa-devel@alsa-project.org'" <alsa-devel@alsa-project.org>,
"Girdwood, Liam R" <liam.r.girdwood@intel.com>,
"'daniel.vetter@ffwll.ch'" <daniel.vetter@ffwll.ch>,
"'intel-gfx@lists.freedesktop.org'"
<intel-gfx@lists.freedesktop.org>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
'David Henningsson' <david.henningsson@canonical.com>
Subject: Re: [alsa-devel] [PATCH 0/4 V7] Power-well API implementation for Haswell
Date: Thu, 25 Jul 2013 06:50:58 +0000 [thread overview]
Message-ID: <46B810F6945F7C4788E11DCE57EC489011851B50@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <46B810F6945F7C4788E11DCE57EC489011851470@SHSMSX104.ccr.corp.intel.com>
Hi Takashi,
In order to let audio power-save work even with charger connected, two parameters need be modified in userspace pm-utils scripts.
I tested the changes under Ubuntu 13.10 on Harris Beach, no matter charger connected or not, runtime power-saving works and power-well will
Be released as expected.
Here's my test under Ubuntu 13.04, the changes are:
1)
/usr/lib/pm-utils/power.d/intel-audio-powersave
case $1 in
true) audio_powersave 1 ;;
+ false) audio_powersave 10 ;;
- false) audio_powersave 0 ;;
help) help;;
*) exit $NA
esac
Audio will enter power-save mode after 10s inactive period.
2) /usr/lib/pm-utils/power.d/pci_devices
0x040300) # audio
echo "Setting Audio device $id to $1"
+ echo "auto" > $dev/power/control
- echo $1 > $dev/power/control
This keep audio subsystem always on.
This way the user may not let audio subsystem always active, may bring some delay from codec/controllers, or harm some chips.
Do you think we should add an exception for Haswell only or just make it as a common solution for audio subsystem?
Thanks
--xingchao
> -----Original Message-----
> From: Wang, Xingchao
> Sent: Wednesday, July 24, 2013 10:00 PM
> To: Takashi Iwai
> Cc: Wysocki, Rafael J; David Henningsson; Paulo Zanoni; Daniel Vetter;
> daniel.vetter@ffwll.ch; alsa-devel@alsa-project.org;
> intel-gfx@lists.freedesktop.org; Girdwood, Liam R; Jin, Gordon
> Subject: RE: [alsa-devel] [Intel-gfx] [PATCH 0/4 V7] Power-well API
> implementation for Haswell
>
>
>
> > -----Original Message-----
> > From: Takashi Iwai [mailto:tiwai@suse.de]
> > Sent: Wednesday, July 24, 2013 9:43 PM
> > To: Wang, Xingchao
> > Cc: Wysocki, Rafael J; David Henningsson; Paulo Zanoni; Daniel Vetter;
> > daniel.vetter@ffwll.ch; alsa-devel@alsa-project.org;
> > intel-gfx@lists.freedesktop.org; Girdwood, Liam R; Jin, Gordon
> > Subject: Re: [alsa-devel] [Intel-gfx] [PATCH 0/4 V7] Power-well API
> > implementation for Haswell
> >
> > At Wed, 24 Jul 2013 13:30:16 +0000,
> > Wang, Xingchao wrote:
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Wysocki, Rafael J
> > > > Sent: Wednesday, July 24, 2013 9:15 PM
> > > > To: David Henningsson
> > > > Cc: Wang, Xingchao; Takashi Iwai; Paulo Zanoni; Daniel Vetter;
> > > > daniel.vetter@ffwll.ch; alsa-devel@alsa-project.org;
> > > > intel-gfx@lists.freedesktop.org; Girdwood, Liam R; Jin, Gordon
> > > > Subject: Re: [alsa-devel] [Intel-gfx] [PATCH 0/4 V7] Power-well
> > > > API implementation for Haswell
> > > >
> > > > On 7/24/2013 1:57 PM, David Henningsson wrote:
> > > > > On 07/24/2013 01:33 PM, Wang, Xingchao wrote:
> > > > >> Yes, I agree. I'm debugging this issue on Ubuntu, not sure it
> > > > >> happens on other distribution too.
> > > > >> If it's related to Ubuntu, maybe need check Ubuntu power policy.
> > > > >> Does anyone know the Ubuntu power-policy on laptop?
> > > > >> i.e. when charger connected, will Ubuntu make decision to
> > > > >> disable power-save feature for audio subsystem?
> > > > >
> > > > > I'm not a power management expert, but I got a pointer from my
> > > > > team mate to pm-utils:
> > > > >
> > > > > http://cgit.freedesktop.org/pm-utils/tree/pm/power.d/intel-audio
> > > > > -p
> > > > > ower
> > > > > save
> > > > >
> > > > >
> > > > > If I understand correctly, The scripts in power.d are executed
> > > > > when battery / AC-power is changed.
> > > > >
> > > >
> > > > To me, this sounds like a user space issue. It requested power on
> > > > and the kernel delivered.
> > >
> > > Do you know which user-space application will touch below two flags?
> > > - /sys/devices/pci0000\:00/0000\:00\:03.0/power/control
> > > - /sys/module/snd_hda_intel/parameters/power_save
> >
> > The latter is touched most likely by pm-utils, one of the hooks, as David
> pointed.
>
> Oh yes I found the hook:
> ./pm/power.d/intel-audio-powersave
>
> --xingchao
> > The former is unknown, but better to check pm-utils hooks and udev rules.
> >
> >
> > Takashi
next prev parent reply other threads:[~2013-07-25 6:50 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 14:07 [PATCH 0/4 V7] Power-well API implementation for Haswell Wang Xingchao
2013-05-30 14:07 ` [PATCH 1/4 V7] ALSA: hda - Fix runtime PM check Wang Xingchao
2013-05-30 14:07 ` [PATCH 2/4] ALSA: hda - Move azx_first_init() into azx_probe_continue() Wang Xingchao
2013-05-30 14:07 ` [PATCH 3/4 V7] ALSA: hda - Add power-welll support for haswell HDA Wang Xingchao
2013-05-30 14:07 ` [PATCH 4/4 V7] i915/drm: Add private api for power well usage Wang Xingchao
2013-06-06 15:34 ` [PATCH 0/4 V7] Power-well API implementation for Haswell Daniel Vetter
2013-07-03 20:00 ` Paulo Zanoni
2013-07-04 8:23 ` Wang xingchao
2013-07-04 13:24 ` Paulo Zanoni
2013-07-04 13:13 ` [Intel-gfx] " Wang xingchao
2013-07-05 21:19 ` Paulo Zanoni
2013-07-06 6:20 ` [Intel-gfx] " Takashi Iwai
2013-07-07 23:59 ` Wang xingchao
2013-07-08 8:07 ` Takashi Iwai
2013-07-17 2:52 ` [Intel-gfx] " Wang, Xingchao
2013-07-17 7:34 ` [alsa-devel] " Takashi Iwai
2013-07-17 8:03 ` [Intel-gfx] " Wang, Xingchao
2013-07-17 8:18 ` Takashi Iwai
2013-07-17 8:25 ` Wang, Xingchao
2013-07-17 13:31 ` [alsa-devel] " Paulo Zanoni
2013-07-17 14:00 ` [Intel-gfx] " Takashi Iwai
2013-07-17 14:05 ` David Henningsson
2013-07-17 14:21 ` [alsa-devel] " Takashi Iwai
2013-07-17 23:17 ` [Intel-gfx] " Wang, Xingchao
2013-07-18 1:00 ` Wang, Xingchao
2013-07-18 6:44 ` Daniel Vetter
2013-07-18 9:23 ` [alsa-devel] " Wang, Xingchao
2013-07-18 9:34 ` Takashi Iwai
2013-07-24 10:31 ` [Intel-gfx] " Wang, Xingchao
2013-07-24 11:02 ` [alsa-devel] " Takashi Iwai
2013-07-24 11:33 ` [Intel-gfx] " Wang, Xingchao
2013-07-24 11:57 ` [alsa-devel] " David Henningsson
2013-07-24 12:13 ` [Intel-gfx] " Takashi Iwai
2013-07-24 13:14 ` Rafael J. Wysocki
2013-07-24 13:30 ` Wang, Xingchao
2013-07-24 13:42 ` Takashi Iwai
2013-07-24 13:46 ` Wang, Xingchao
2013-07-24 14:00 ` Wang, Xingchao
2013-07-25 6:50 ` Wang, Xingchao [this message]
2013-07-24 14:36 ` Wang, Xingchao
2013-07-18 6:54 ` [alsa-devel] " Takashi Iwai
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=46B810F6945F7C4788E11DCE57EC489011851B50@SHSMSX104.ccr.corp.intel.com \
--to=xingchao.wang@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=daniel.vetter@ffwll.ch \
--cc=david.henningsson@canonical.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=liam.r.girdwood@intel.com \
--cc=rafael.j.wysocki@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 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.