From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Hui Wang <hui.wang@canonical.com>
Subject: Re: [PATCH 0/4] More aggressive PM for HD-audio
Date: Fri, 20 Mar 2015 17:20:59 +0100 [thread overview]
Message-ID: <550C48EB.1050200@canonical.com> (raw)
In-Reply-To: <1426668658-15911-1-git-send-email-tiwai@suse.de>
On 2015-03-18 09:50, Takashi Iwai wrote:
> Hi,
>
> here is a patchset for supporting more aggressive PM for HD-audio.
> This allows to change the power state of each widget more dynamically
> with jack and stream states. It's activated only when the codec
> driver (or via sysfs or f/w patch) sets codec->power_mgmt flag.
>
> In theory, this should work for the recent Realtek codecs, but
> currently I have no machine for test.
>
> David, could you or your team check whether this works for ALC282 or
> such? Just add like:
>
> --- a/sound/pci/hda/patch_realtek.c
> +++ b/sound/pci/hda/patch_realtek.c
> @@ -5415,6 +5415,7 @@ static int patch_alc269(struct hda_codec *codec)
>
> spec = codec->spec;
> spec->gen.shared_mic_vref_pin = 0x18;
> + codec->power_mgmt = 1;
>
> snd_hda_pick_fixup(codec, alc269_fixup_models,
> alc269_fixup_tbl, alc269_fixups);
>
>
> The patchset is for for-next branch of sound git tree, but they might
> be applicable to 4.0-rc (or even older), too. The current patches are
> found in topic/hda-power branch.
So I hoped to be able to look at this today, but it turns out the
machine I was thinking of using for testing has an ALC262 codec, which
hardly counts as "new".
Hui, is this something you feel like taking on? Otherwise I'll try to
talk to someone in Taipei.
Anyhow, after reading through the code, I have a question about LEDs. It
could be that if vref is used for controlling a LED, maybe that pin
needs to stay in D0 for the LED to stay lit. Is this correctly handled?
I couldn't find any code specific to that issue, but maybe I just missed it.
Also, I find the power_mgmt name easy to confuse with the existing
power_save parameter, perhaps power_save_pin, power_save_node or
power_save_widget is better?
>
>
> thanks,
>
> Takashi
>
> ===
>
> Takashi Iwai (4):
> ALSA: hda - Simplify PCM setup overrides
> ALSA: hda - Support advanced power state controls
> ALSA: hda - Use the new power control for VIA codecs
> ALSA: hda - Adjust power of beep widget and outputs
>
> sound/pci/hda/hda_beep.c | 29 +-
> sound/pci/hda/hda_beep.h | 1 +
> sound/pci/hda/hda_codec.c | 4 +
> sound/pci/hda/hda_codec.h | 2 +
> sound/pci/hda/hda_generic.c | 480 ++++++++++++++++++++++++------
> sound/pci/hda/hda_generic.h | 5 +-
> sound/pci/hda/patch_realtek.c | 41 ---
> sound/pci/hda/patch_sigmatel.c | 5 +
> sound/pci/hda/patch_via.c | 662 +----------------------------------------
> 9 files changed, 427 insertions(+), 802 deletions(-)
>
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next prev parent reply other threads:[~2015-03-20 16:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 8:50 [PATCH 0/4] More aggressive PM for HD-audio Takashi Iwai
2015-03-18 8:50 ` [PATCH 1/4] ALSA: hda - Simplify PCM setup overrides Takashi Iwai
2015-03-18 8:50 ` [PATCH 2/4] ALSA: hda - Support advanced power state controls Takashi Iwai
2015-03-18 8:50 ` [PATCH 3/4] ALSA: hda - Use the new power control for VIA codecs Takashi Iwai
2015-03-18 8:50 ` [PATCH 4/4] ALSA: hda - Adjust power of beep widget and outputs Takashi Iwai
2015-03-18 19:34 ` [PATCH 0/4] More aggressive PM for HD-audio David Henningsson
2015-03-18 20:02 ` Takashi Iwai
2015-03-20 16:20 ` David Henningsson [this message]
2015-03-20 16:28 ` Takashi Iwai
2015-03-20 17:18 ` Takashi Iwai
2015-03-20 17:33 ` Takashi Iwai
2015-03-21 6:38 ` Hui Wang
[not found] ` <5513FA8B.402@canonical.com>
2015-03-26 13:10 ` Takashi Iwai
2015-03-26 13:52 ` Takashi Iwai
2015-03-27 0:11 ` Hui Wang
2015-03-30 6:53 ` hwang4
2015-04-04 10:31 ` Takashi Iwai
2015-04-09 6:54 ` hwang4
2015-04-09 6:56 ` Takashi Iwai
2015-04-09 6:59 ` David Henningsson
2015-04-09 8:35 ` 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=550C48EB.1050200@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=hui.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox