public inbox for linux-sound@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Samantha Glocker <iam@anislandsomewhere.com>
Cc: linux-sound@vger.kernel.org, tiwai@suse.de
Subject: Re: possible issue with ALSA: hda/realtek: Use codec SSID matching for Lenovo devices
Date: Wed, 22 Jan 2025 08:21:26 +0100	[thread overview]
Message-ID: <87a5bj8gax.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAGPQRHYd48U__UKYj2jJnT4+dnNNoWRBi+wj6zPRn=JpNMBUrg@mail.gmail.com>

On Wed, 22 Jan 2025 01:58:16 +0100,
Samantha Glocker wrote:
> 
> Hi, I'm a kernel maintainer from nobara and ASUS-Linux.
> 
> I've bifurcated an issue with sound on Lenovo Legion laptop(s)
> starting from mainline 6.12.5, verified on Fedora proper, Nobara, and
> CachyOS.
> 
> From the changelog,
> https://patch.msgid.link/20241008120233.7154-4-tiwai@suse.de looks
> like a likely candidate due to touching TAS2781 / TIA2781.
> 
> The issue will possibly affect sound on any or all Lenovo Legion Gen 8 and 9.
> 
> The obvious difference in dmesg on my Legion Pro 7 Gen 8 (16ARX8H) on
> 6.12.5, is the following line is completely missing:
> [    4.761665] snd_hda_codec_realtek hdaudioC1D0: bound
> i2c-TIAS2781:00 (ops tas2781_hda_comp_ops
> [snd_hda_scodec_tas2781_i2c])
> 
> This suggests the TI amplifier is never identified.

What's the exact problem?  Is it a regression?  Any original report on
the bug tracker or such?


thanks,

Takashi

  reply	other threads:[~2025-01-22  7:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22  0:58 possible issue with ALSA: hda/realtek: Use codec SSID matching for Lenovo devices Samantha Glocker
2025-01-22  7:21 ` Takashi Iwai [this message]
2025-01-22  7:23   ` Takashi Iwai
2025-01-22  8:53     ` Takashi Iwai
2025-01-23  2:00       ` Samantha Glocker
2025-01-23 11:07         ` Takashi Iwai
     [not found]           ` <CAGPQRHYG_BUSjWSN4LH4oPeM5h4E30WSyfaRynYhrcDYT95dXg@mail.gmail.com>
2025-01-24 22:58             ` Samantha Glocker
2025-01-25 12:05               ` 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=87a5bj8gax.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=iam@anislandsomewhere.com \
    --cc=linux-sound@vger.kernel.org \
    /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