From: Takashi Iwai <tiwai@suse.de>
To: woodrow.shen@canonical.com
Cc: alsa-devel@alsa-project.org, stable@vger.kernel.org
Subject: Re: [alsa-devel][PATCH] ALSA: hda - Fix the headset mic jack detection on Dell machine
Date: Fri, 24 Jun 2016 10:31:05 +0200 [thread overview]
Message-ID: <s5hmvmbt2d2.wl-tiwai@suse.de> (raw)
In-Reply-To: <1466755114-18477-1-git-send-email-woodrow.shen@canonical.com>
On Fri, 24 Jun 2016 09:58:34 +0200,
woodrow.shen@canonical.com wrote:
>
> From: Woodrow Shen <woodrow.shen@gmail.com>
>
> The new Dell laptop with codec 3246 can't detect headset mic when
> headset was inserted on the machine. So adding pin configurations
> into quirk table makes headset mic work correctly.
>
> Codec: Realtek ALC3246
> Vendor Id: 0x10ec0256
> Subsystem Id: 0x10280781
>
> Signed-off-by: Woodrow Shen <woodrow.shen@canonical.com>
Applied, thanks.
Takashi
next prev parent reply other threads:[~2016-06-24 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 7:58 [alsa-devel][PATCH] ALSA: hda - Fix the headset mic jack detection on Dell machine woodrow.shen
2016-06-24 8:31 ` Takashi Iwai [this message]
2016-06-24 15:35 ` Greg KH
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=s5hmvmbt2d2.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=stable@vger.kernel.org \
--cc=woodrow.shen@canonical.com \
/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