Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "René Rebe" <rene@exactco.de>
Cc: linux-sound@vger.kernel.org, kailang@realtek.com
Subject: Re: [PATCH] fixup realtek/alc288 headphone for MS Surface 2, 3 and
Date: Thu, 20 Nov 2025 07:52:36 +0100	[thread overview]
Message-ID: <87wm3lb3gr.wl-tiwai@suse.de> (raw)
In-Reply-To: <3D155CBD-5517-480B-AB15-22DDAA5EF282@exactco.de>

On Wed, 19 Nov 2025 18:17:14 +0100,
René Rebe wrote:
> 
> Hi,
> 
> > On 19. Nov 2025, at 16:44, Takashi Iwai <tiwai@suse.de> wrote:
> > 
> > On Wed, 19 Nov 2025 16:13:32 +0100,
> > Takashi Iwai wrote:
> >> 
> >> On Mon, 17 Nov 2025 21:07:34 +0100,
> >> René Rebe wrote:
> >>> 
> >>> On Mon, 17 Nov 2025 17:20:03 +0100, Takashi Iwai <tiwai@suse.de> wrote:
> >>> 
> >>>> On Sun, 16 Nov 2025 16:26:33 +0100,
> >>>> René Rebe wrote:
> >>>>> 
> >>>>> The Surface Pro 2 and 3 have a strage frequency response and miss most
> >>>>> of the bass. I discovered connecting the HP out to the main DAC fixes
> >>>>> this.  Maybe the other is mono or whatever strangely mixed signal for
> >>>>> the built-in speakers?
> >>>>> 
> >>>>> I later noticed the Lenovo Ideapad 720S (AMD) exhibited the same
> >>>>> problem, so this may be a more wide-spread general bug w/ Realtek
> >>>>> codecs and the hda_auto_parser, ...
> >>>> 
> >>>> Usually in a case like this, we provide a fixed wiring by a static DAC
> >>>> table, or do some other tricks instead of directly writing a verb.
> >>>> 
> >>>> Could you give the alsa-info.sh outputs from those?
> >>> 
> >>> Sure, here is an slightly older 6.16 kernel I had at hand that did had
> >>> my fixes applied:
> >> 
> >> Thanks.  Could you give the output from the unpatched kernel, too?
> >> Just to make sure.
> 
> 
> Sorry, typo, I already had booted an old kernel without the patch.
> 
> > ... and if the purpose is to just swap DAC assignments between the
> > headphone and the speaker pins, a patch like below could work better.
> > (The entry is 
> 
> Something missing? But no worries I will try it out and swap entries if
> needed and send a final patch.

Yes please.  I just wanted to say that the entry PCI SSID was copied
from your patch.


Takashi

      reply	other threads:[~2025-11-20  6:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-16 15:26 [PATCH] fixup realtek/alc288 headphone for MS Surface 2, 3 and René Rebe
2025-11-17 16:20 ` Takashi Iwai
2025-11-17 20:07   ` René Rebe
2025-11-19 15:13     ` Takashi Iwai
2025-11-19 15:44       ` Takashi Iwai
2025-11-19 17:17         ` René Rebe
2025-11-20  6:52           ` 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=87wm3lb3gr.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=kailang@realtek.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=rene@exactco.de \
    /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