linux-kernel - Re: [PATCH v2] ALSA: hda/realtek: Add quirk for Minisforum V3 SE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87343hlx0q.wl-tiwai@suse.de>
Date: Tue, 03 Feb 2026 15:30:45 +0100
From: Takashi Iwai <tiwai@...e.de>
To: Samuel Dionne-Riel <samuel@...nne-riel.com>
Cc: Jaroslav Kysela <perex@...ex.cz>,
	Takashi Iwai <tiwai@...e.com>,
	linux-sound@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] ALSA: hda/realtek: Add quirk for Minisforum V3 SE

On Tue, 03 Feb 2026 02:01:33 +0100,
Samuel Dionne-Riel wrote:
> 
> First, adding a generic quirk for Bass speaker DAC avoidance.
> 
> This pattern (re-routing the bass speakers off of a DAC without volume
> control) seems common enough that having a "model" to match against and
> quickly use to verify may be worthwhile.
> 
> The alc285_fixup_thinkpad_x1_gen7 routing was selected, amongst the
> different options, as it should allow tuning the ratio between both
> speaker set.
> 
> The routing was verified using `hda-verb`, and picking either 0x00 or
> 0x01. Either routing made the volume of the bass speakers controllable.
> 
>     hda-verb /dev/snd/hwC1D0 0x17 SET_CONNECT_SEL 0x01
> 
> This likely will apply for the Minisforum V3, though there isn't a lot
> of information to confirm whether or not the identifiers are the same.
> 
> This was verified on the Minisforum V3 SE, and the root cause (the bass
> speakers routing) was found out by using pink noise, and playing with
> the mixers.
> 
> Signed-off-by: Samuel Dionne-Riel <samuel@...nne-riel.com>
> 
> ---
> 
> Hi!
> 
> > Indeed it looks like that we can cleanup a lot regarding this DAC
> > routing fix-ups.  Though, *_thinkpad_x1_gen7() has more workarounds
> > about the control element renames -- which needs to be verified
> > whether the very same workaround is applicable to other cases.
> 
> The renames were the reason I picked this particular fixup. It matches
> the fact these are distinct speakers, and matches the role.
> 
> > IIUC, this kcontrol names (DAC1/DAC2) match with your device
> > configuration?  Could you give alsa-info.sh output?
> 
> Indeed! Here is the output:
> 
>  - https://alsa-project.org/db/?f=69517ae9d95e21b50eddc64538c7094aaf356a07
> 
> 
> See also v1 for the methodology additional commentary.
>  - https://lore.kernel.org/linux-sound/20260201231216.1655154-1-samuel@dionne-riel.com/
> 
> Changes since v1:
>  - Combined commits
>  - Fixed order of the fixup table
> 
> Thank you for your time!
> 
> Signed-off-by: Samuel Dionne-Riel <samuel@...nne-riel.com>

Now I applied to for-next branch, as it's no urgent fix.
I slightly modified the patch to adapt to the latest tree.


thanks,

Takashi