From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, 1248465@bugs.launchpad.net
Subject: Re: [PATCH] ALSA: hda - Make sure mute LEDs stay on during runtime suspend (Realtek)
Date: Wed, 06 Nov 2013 11:17:23 +0100 [thread overview]
Message-ID: <527A1733.2080907@canonical.com> (raw)
In-Reply-To: <s5hr4atet6f.wl%tiwai@suse.de>
On 11/06/2013 11:11 AM, Takashi Iwai wrote:
> At Wed, 6 Nov 2013 10:50:44 +0100,
> David Henningsson wrote:
>>
>> Some HP machines with Realtek codecs have mute LEDs connected to VREF pins.
>> However when these go into runtime suspend, the pin powers down and its
>> pin control is disabled, thus disabling the LED too.
>>
>> This patch fixes that issue by making sure that the pin stays in D0 with
>> correct pin control.
>>
>> Cc: stable@kernel.org
>> BugLink: https://bugs.launchpad.net/bugs/1248465
>> Tested-by: Franz Hsieh <franz.hsieh@canonical.com>
>> Signed-off-by: David Henningsson <david.henningsson@canonical.com>
>
> Thanks, applied.
>
> I do wonder, though, whether the LED survives even after turning AFG
> to D3. With IDT codecs, we had to keep AFG D0 just for keeping this
> VREF stuff. Maybe Realtek codecs behave differently.
Well, the patch was tested by Franz and found working, so it seems
indeed that AFG can be in D3 and the LED still works.
(Actually it could even be the other way around - maybe even the pin can
remain in D3 and still have vref output, as long as the pin ctl is set.
I never tested that explicitly.)
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
prev parent reply other threads:[~2013-11-06 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 9:50 [PATCH] ALSA: hda - Make sure mute LEDs stay on during runtime suspend (Realtek) David Henningsson
2013-11-06 10:11 ` Takashi Iwai
2013-11-06 10:17 ` David Henningsson [this message]
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=527A1733.2080907@canonical.com \
--to=david.henningsson@canonical.com \
--cc=1248465@bugs.launchpad.net \
--cc=alsa-devel@alsa-project.org \
--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.