From: Takashi Iwai <tiwai@suse.de>
To: "Xu, Baojun" <baojun.xu@ti.com>
Cc: Antheas Kapenekakis <lkml@antheas.dev>,
"Ding, Shenghao" <shenghao-ding@ti.com>,
Takashi Iwai <tiwai@suse.com>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [EXTERNAL] [PATCH v1 1/2] ALSA: hda/tas2781: fix speaker id retrieval for multiple probes
Date: Tue, 18 Nov 2025 07:54:51 +0100 [thread overview]
Message-ID: <87zf8jesp0.wl-tiwai@suse.de> (raw)
In-Reply-To: <7c0d8c96c51c4265aa150ed8c4d785c7@ti.com>
On Tue, 18 Nov 2025 03:31:32 +0100,
Xu, Baojun wrote:
>
> >
> > ________________________________________
> > From: Antheas Kapenekakis <lkml@antheas.dev>
> > Sent: 27 October 2025 03:16
> > To: Ding, Shenghao; Xu, Baojun
> > Cc: Takashi Iwai; linux-sound@vger.kernel.org; linux-kernel@vger.kernel.org; Antheas Kapenekakis; stable@vger.kernel.org
> > Subject: [EXTERNAL] [PATCH v1 1/2] ALSA: hda/tas2781: fix speaker id retrieval for multiple probes
> >
> > Currently, on ASUS projects, the TAS2781 codec attaches the speaker GPIO
> > to the first tasdevice_priv instance using devm. This causes
> > tas2781_read_acpi to fail on subsequent probes since the GPIO is already
> > managed by the first device. This causes a failure on Xbox Ally X,
> > because it has two amplifiers, and prevents us from quirking both the
> > Xbox Ally and Xbox Ally X in the realtek codec driver.
> >
> > It is unnecessary to attach the GPIO to a device as it is static.
> > Therefore, instead of attaching it and then reading it when loading the
> > firmware, read its value directly in tas2781_read_acpi and store it in
> > the private data structure. Then, make reading the value non-fatal so
> > that ASUS projects that miss a speaker pin can still work, perhaps using
> > fallback firmware.
> >
> > Fixes: 4e7035a75da9 ("ALSA: hda/tas2781: Add speaker id check for ASUS projects")
> > Cc: stable@vger.kernel.org # 6.17
> > Signed-off-by: Antheas Kapenekakis <lkml@antheas.dev>
> > ---
> > include/sound/tas2781.h | 2 +-
> > .../hda/codecs/side-codecs/tas2781_hda_i2c.c | 44 +++++++++++--------
> > 2 files changed, 26 insertions(+), 20 deletions(-)
> >
> Reviewed-by: Baojun Xu <baojun.xu@ti.com>
OK, I applied both patches to for-next branch now.
For the remaining issues, let's fix on the top.
thanks,
Takashi
prev parent reply other threads:[~2025-11-18 6:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 19:16 [PATCH v1 1/2] ALSA: hda/tas2781: fix speaker id retrieval for multiple probes Antheas Kapenekakis
2025-10-26 19:16 ` [PATCH v1 2/2] ALSA: hda/realtek: Add match for ASUS Xbox Ally projects Antheas Kapenekakis
2025-10-26 19:19 ` Antheas Kapenekakis
2025-10-27 6:01 ` Matthew Schwartz
2025-10-27 8:23 ` Antheas Kapenekakis
2025-10-27 8:34 ` Antheas Kapenekakis
2025-10-27 19:57 ` Matthew Schwartz
2025-10-28 17:27 ` Antheas Kapenekakis
2025-11-02 17:33 ` Antheas Kapenekakis
2025-11-09 9:19 ` Antheas Kapenekakis
2025-11-17 16:14 ` Takashi Iwai
2025-11-18 2:31 ` [EXTERNAL] [PATCH v1 1/2] ALSA: hda/tas2781: fix speaker id retrieval for multiple probes Xu, Baojun
2025-11-18 6:54 ` 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=87zf8jesp0.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=baojun.xu@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=shenghao-ding@ti.com \
--cc=stable@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.