From: Johan Hovold <johan@kernel.org>
To: Simone Flavio Paris <simone.flavio.paris@gmail.com>
Cc: linux-arm-msm@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [BUG REPORT] arm64: dts: qcom: x1e80100: Audio routing issues on ThinkPad T14s Gen 6
Date: Wed, 7 Jan 2026 15:39:44 +0100 [thread overview]
Message-ID: <aV5wMKBZMIESIMbC@hovoldconsulting.com> (raw)
In-Reply-To: <CAG=QoF1cr3cFzgjRicLSr7KbwygQaHju1WKE_LK_U9Qmsgv13g@mail.gmail.com>
On Wed, Jan 07, 2026 at 03:09:10PM +0100, Simone Flavio Paris wrote:
> I am testing the latest experimental kernels on the Lenovo ThinkPad
> T14s Gen 6 (Snapdragon X Elite).
>
> I have encountered a specific issue with the audio subsystem: while
> the DSP and ALSA stack appear fully functional (firmware loads,
> streams are processed without errors), there is no analog output on
> speakers or headphones.
>
> I have performed extensive diagnostics and manual mixer path
> configurations to rule out userspace/UCM issues. Below is a detailed
> technical report of the current status, routing attempts, and logs.
>
> I hope this information helps in refining the machine driver or
> topology profiles for this specific device. I am available to test
> patches if needed.
>
> [Technical Report]
>
> Target Hardware: Lenovo ThinkPad T14s Gen 6 (21N1) - Snapdragon X
> Elite (X1E80100)
> OS: Ubuntu 25.10 (Debian-based)
> Kernel: 6.17.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC aarch64
You need to report this to your distro as this is not a mainline issue.
IIUC, Ubuntu disables audio by default until you pass a kernel parameter
due to the lack of speaker protection.
Johan
prev parent reply other threads:[~2026-01-07 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 14:09 [BUG REPORT] arm64: dts: qcom: x1e80100: Audio routing issues on ThinkPad T14s Gen 6 Simone Flavio Paris
2026-01-07 14:39 ` Johan Hovold [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=aV5wMKBZMIESIMbC@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=simone.flavio.paris@gmail.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.