Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Matthew Schwartz <matthew.schwartz@linux.dev>
To: Baojun Xu <baojun.xu@ti.com>, Shenghao Ding <shenghao-ding@ti.com>
Cc: linux-sound@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Antheas Kapenekakis <lkml@antheas.dev>,
	tiwai@suse.de
Subject: [BUG] hda/tas2781: ASUS ROG Xbox Ally X audio issues with default firmware
Date: Wed, 3 Dec 2025 17:47:33 -0800	[thread overview]
Message-ID: <0ba100d0-9b6f-4a3b-bffa-61abe1b46cd5@linux.dev> (raw)

Hello,

I have an ASUS ROG Xbox Ally X which uses hda/tas2781 for the speaker amplifiers. I am splitting this out into a new thread based on the suggestion from [1] to fix the remaining issues with the device's audio separately. 

I built a kernel from tags/sound-6.19-rc1 in tiwai/sound and included [2], which seemed potentially relevant to the issue that I describe below.

By default, my system loads /usr/lib/firmware/ti/audio/tas2781/TAS2XXX13840.bin.zst. With this firmware file, any sound above the 70% volume limit range starts to become distorted and frequently drop out from either one or both speakers. I've included an alsa-info.sh report with this default firmware at [3].

If I run sudo mv /usr/lib/firmware/ti/audio/tas2781/TAS2XXX13841.bin.zst /usr/lib/firmware/ti/audio/tas2781/TAS2XXX13840.bin.zst and force the other firmware file for Xbox Ally models, my speakers work up to 100% without any of the drop outs I experience on the default firmware. I've included an alsa-info.sh report with this renamed firmware at [4].

I took an acpidump at [5] and extracted the dsdt table at [6]. Please let me know if there's any additional information I can provide from the device to further debug the sound issues with the default selected firmware.

Thanks,
Matt

[1]: https://lore.kernel.org/linux-sound/87zf8jesp0.wl-tiwai@suse.de/
[2]: https://lore.kernel.org/all/20251126141434.11110-1-baojun.xu@ti.com/
[3]: https://alsa-project.org/db/?f=840337cab11f6aa70cf48b15d55ac45e4027ff41
[4]: https://alsa-project.org/db/?f=6e482f72765d89520ea171f15641228bcadefcf0
[5]: https://gist.githubusercontent.com/matte-schwartz/d7ff3c857b45cca197f3d3adc16df0bc/raw/2e3267b8d1a9d619ecd8157e4da426be756b6497/acpidump.txt
[6]: https://gist.githubusercontent.com/matte-schwartz/4042dcd3779c3738af60536a9d4050d6/raw/5227717c6d40a2dc4012b95f7fefc6cd50ba784d/dsdt.dsl

             reply	other threads:[~2025-12-04  1:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04  1:47 Matthew Schwartz [this message]
2025-12-04 21:28 ` [BUG] hda/tas2781: ASUS ROG Xbox Ally X audio issues with default firmware Antheas Kapenekakis
2025-12-08 21:37 ` Matthew Schwartz
2025-12-09  4:00   ` Matthew Schwartz
2025-12-30 20:43     ` Matthew Schwartz
2026-01-02 17:12       ` Antheas Kapenekakis
2026-01-02 19:16         ` Matthew Schwartz
2026-01-02 23:13           ` Antheas Kapenekakis
2026-01-03  0:31             ` Matthew Schwartz
2026-01-03 11:48               ` Antheas Kapenekakis
2026-01-04  8:58                 ` [EXTERNAL] " Xu, Baojun
2026-01-04  9:29                   ` Matthew Schwartz
2026-01-07  8:31                     ` 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=0ba100d0-9b6f-4a3b-bffa-61abe1b46cd5@linux.dev \
    --to=matthew.schwartz@linux.dev \
    --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=tiwai@suse.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