From: Takashi Iwai <tiwai@suse.de>
To: Werner Sembach <wse@tuxedocomputers.com>
Cc: alsa-devel@alsa-project.org,
Eckhart Mohr <e.mohr@tuxedocomputers.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
tiwai@suse.com, alsa-devel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Add quirk for Intel NUC 10
Date: Wed, 03 Mar 2021 09:24:40 +0100 [thread overview]
Message-ID: <s5h1rcwejav.wl-tiwai@suse.de> (raw)
In-Reply-To: <20210302180414.23194-1-wse@tuxedocomputers.com>
On Tue, 02 Mar 2021 19:04:14 +0100,
Werner Sembach wrote:
>
> ALSA: hda/realtek: Add quirk for Intel NUC 10
I guess you added a subject line twice here. This line can be dropped.
> This adds a new SND_PCI_QUIRK(...) and applies it to the Intel NUC 10
> devices. This fixes the issue of the devices not having audio input and
> output on the headset jack because the kernel does not recognize when
> something is plugged in.
>
> The new quirk was inspired by the quirk for the Intel NUC 8 devices, but
> it turned out that the NUC 10 uses another pin. This information was
> acquired by black box testing likely pins.
>
> Co-developed-by: Eckhart Mohr <e.mohr@tuxedocomputers.com>
> Signed-off-by: Eckhart Mohr <e.mohr@tuxedocomputers.com>
> Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
> Cc: <stable@vger.kernel.org>
> ---
> Resend of this patch with git send-email, because last patch got tabs replaced with spaces.
Applied, thanks.
Takashi
next prev parent reply other threads:[~2021-03-03 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 18:04 [PATCH] ALSA: hda/realtek: Add quirk for Intel NUC 10 Werner Sembach
2021-03-03 8:24 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-02 18:25 Werner Sembach
2021-03-02 11:25 Werner Sembach
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=s5h1rcwejav.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-devel@vger.kernel.org \
--cc=e.mohr@tuxedocomputers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=wse@tuxedocomputers.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