From: David Wronek <david@mainlining.org>
To: Linux Sound <linux-sound@vger.kernel.org>
Cc: David Rhodes <david.rhodes@cirrus.com>,
Lucas Tanure <lucas.tanure@cirrus.com>,
linux-kernel@vger.kernel.org
Subject: cs35l41: Enable(1) failed: -110
Date: Tue, 18 Mar 2025 11:11:43 +0100 [thread overview]
Message-ID: <f7c97d53a38fb82ba8dab3b5c0c28b48@mainlining.org> (raw)
Hi,
I am trying to get the Cirrus CS35L41 amps working on the Lenovo Xiaoxin
Pad Pro 2021 on mainline Linux.
Unfortunately, while enabling the speakers, I encounter the following
error with non-working speakers:
```
[ 104.028258] cs35l41 4-0041: Enable(1) failed: -110
[ 104.028597] cs35l41 4-0041: ASoC: PRE_PMU: SPK2 Main AMP event
failed: -110
```
I have looked into the driver and it seems like it timing out while
polling the CS35L41_IRQ1_STATUS1 register.
According to the downstream device tree, the amps are connected over
MI2S and are using an internal boost. Switching to a shared boost does
not work, because the interrupt is never called.
I am not sure what I might be missing here. Sadly, Lenovo has not
released the kernel sources used in the Xiaoxin Pad Pro 2021 which is
why I can't easily check the downstream driver for potential quirks.
Here is my setup:
- Full dmesg:
https://paste.mainlining.org/ungeskriptet/66855caf17f342e9b030ffe0640e84de
- Device tree:
https://github.com/mainlining/linux/blob/f14a883/arch/arm64/boot/dts/qcom/sm8250-lenovo-j716f.dts
- ALSA UCM file:
https://paste.mainlining.org/ungeskriptet/33fe4907c000413fac94e5052215b1ea
Help would be greatly appreciated.
--
Best regards,
David Wronek <david@mainlining.org>
reply other threads:[~2025-03-18 10:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f7c97d53a38fb82ba8dab3b5c0c28b48@mainlining.org \
--to=david@mainlining.org \
--cc=david.rhodes@cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=lucas.tanure@cirrus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox