From: Samuel Dionne-Riel <samuel@dionne-riel.com>
To: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: Samuel Dionne-Riel <samuel@dionne-riel.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] ALSA: hda/realtek: Add quirk for Minisforum V3 SE
Date: Sun, 1 Feb 2026 18:12:13 -0500 [thread overview]
Message-ID: <20260201231216.1655154-1-samuel@dionne-riel.com> (raw)
Hi!
These changes fix audio for the Minisforum V3 SE.
While I didn't tag as RFC, as it might be just fine the way it is, I am
open to suggestions regarding how I implemented the first commit.
The main goal being it uses and exposes a generic name for this specific
fixup, while keeping to a minimal change. As mentioned in the commentary
for that patch, there are a couple other fixup functions that may aim at
applying the same fix, but it's hard to be sure without testing with the
original hardware this fixed.
There are more details about each change in their respective email, in
the commentary past the commit message.
Thank you for your time!
Samuel Dionne-Riel (2):
ALSA: hda/realtek: Add generic quirk for Bass speaker DAC avoidance
ALSA: hda/realtek: Add quirk for Minisforum V3 SE
sound/hda/codecs/realtek/alc269.c | 8 ++++++++
1 file changed, 8 insertions(+)
base-commit: 63804fed149a6750ffd28610c5c1c98cce6bd377
--
2.51.0
next reply other threads:[~2026-02-01 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 23:12 Samuel Dionne-Riel [this message]
2026-02-01 23:12 ` [PATCH 1/2] ALSA: hda/realtek: Add generic quirk for Bass speaker DAC avoidance Samuel Dionne-Riel
2026-02-02 10:03 ` Takashi Iwai
2026-02-01 23:12 ` [PATCH 2/2] ALSA: hda/realtek: Add quirk for Minisforum V3 SE Samuel Dionne-Riel
2026-02-02 10:00 ` 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=20260201231216.1655154-1-samuel@dionne-riel.com \
--to=samuel@dionne-riel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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