From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] ALSA: HDA: Refactor Realtek's automute
Date: Tue, 20 Sep 2011 17:29:22 +0200 [thread overview]
Message-ID: <4E78B152.8070903@canonical.com> (raw)
In-Reply-To: <s5hwrd3z29b.wl%tiwai@suse.de>
On 09/20/2011 05:01 PM, Takashi Iwai wrote:
> At Tue, 20 Sep 2011 12:26:30 +0200,
> David Henningsson wrote:
>>
>> Ok, my automute refactoring has been rebased to your latest tree. I've
>> tested it on my own machine, but I don't know if wider testing is needed
>> to ensure there are no regressions.
>
> Thanks.
>
> alc_simple_setup_automute() calls can be more simplified.
> The function can check spec->autocfg.line_out_pins[0], hp_pins[0] and
> speaker_pins[0] to identify detect_hp& co flags. Otherwise, the
> arguments "1, 0, 0, 1" are hard to understand.
>
> Other than that, the patch looks good to me.
That means a functional change in one place (alc882_quirks.c), where
there are line_out_pins but automute for line out is not set:
@@ -2568,8 +2554,7 @@ static void alc888_lenovo_ms7195_setup(struct
hda_codec *codec)
spec->autocfg.hp_pins[0] = 0x1b;
spec->autocfg.line_out_pins[0] = 0x14;
spec->autocfg.speaker_pins[0] = 0x15;
- spec->automute = 1;
- spec->automute_mode = ALC_AUTOMUTE_AMP;
+ alc_simple_setup_automute(spec, ALC_AUTOMUTE_AMP, 1, 0, 0, 1);
}
If you don't mind that change I can do what you suggest.
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next prev parent reply other threads:[~2011-09-20 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 10:26 [PATCH] ALSA: HDA: Refactor Realtek's automute David Henningsson
2011-09-20 15:01 ` Takashi Iwai
2011-09-20 15:29 ` David Henningsson [this message]
2011-09-20 15:36 ` Takashi Iwai
2011-09-20 16:04 ` David Henningsson
2011-09-20 16:23 ` 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=4E78B152.8070903@canonical.com \
--to=david.henningsson@canonical.com \
--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.