mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Denis Yakovlev <mfthesun@vivaldi.net>
Cc: tiwai@suse.com, perex@perex.cz, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Drop unneeded DAC override for HONOR MagicBook Pro 16 2024
Date: Tue, 06 Oct 2026 16:12:39 +0200	[thread overview]
Message-ID: <87ld8aq5ns.wl-tiwai@suse.de> (raw)
In-Reply-To: <20261005203836.11074-1-mfthesun@vivaldi.net>

On Mon, 05 Oct 2026 22:38:36 +0200,
Denis Yakovlev wrote:
> 
> Commit 1e3e378d63be ("ALSA: hda/realtek: Enable bass speakers on HONOR
> MagicBook Pro 16 2024") restricted the speaker pin 0x1b to DAC 0x02, on
> the assumption that the second speaker pair would otherwise end up on
> DAC 0x03, as channels 3/4 that a stereo stream never reaches. That
> assumption was wrong: without the override, pin 0x1b is still connected
> to DAC 0x02, the only DAC that pin 0x14 can use, so the override changes
> nothing. With and without it the codec routing is identical and the
> speakers behave the same with nothing plugged in, with headphones and
> with a CTIA headset inserted; without it they also keep working after
> suspend/resume.
> 
> That commit also got the speaker roles the wrong way round. Pin 0x1b,
> which the BIOS does configure, drives the bottom speakers, which carry
> the low and mid frequencies; pin 0x14 drives the tweeters next to the
> keyboard, and those are the speakers that stay silent without the quirk.
> Measured with the internal microphones, enabling one pin at a time: at
> 1 kHz the 0x14 pair alone is more than 30 dB below the 0x1b pair alone,
> while at 6 kHz the two are within 10 dB of each other.
> 
> Drop the DAC override and correct the pin comment, so the quirk only
> sets pin configurations, like the one for the sibling M1020 board
> (HONOR MRB-XXX).
> 
> Fixes: 1e3e378d63be ("ALSA: hda/realtek: Enable bass speakers on HONOR MagicBook Pro 16 2024")
> Assisted-by: LLM
> Signed-off-by: Denis Yakovlev <mfthesun@vivaldi.net>

Applied to for-next branch.  Thanks.


Takashi

      reply	other threads:[~2026-10-06 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 20:38 Denis Yakovlev
2026-10-06 14:12 ` Takashi Iwai [this message]

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=87ld8aq5ns.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=mfthesun@vivaldi.net \
    --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

all inboxes | Powered by JetHome®