From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Tobias Bachmann <tobac@mailbox.org>
Cc: linux-sound@vger.kernel.org,
Richard Fitzgerald <rf@opensource.cirrus.com>,
David Rhodes <david.rhodes@cirrus.com>,
patches@opensource.cirrus.com, Mark Brown <broonie@kernel.org>
Subject: Re: ASoC: cs42l43: SDCA reattach timeout on Dell XPS 14 Panther Lake; chip stuck across distros and kernels; worked initially; still working at hardware level
Date: Thu, 7 May 2026 16:35:54 +0100 [thread overview]
Message-ID: <afyxWuMCcawIE2+v@opensource.cirrus.com> (raw)
In-Reply-To: <y6AZlQCPSdCp46upW40QCA@mailbox.org>
On Thu, May 07, 2026 at 02:32:21PM +0200, Tobias Bachmann wrote:
> thank you for picking this up so quickly, much appreciated.
No problem :-)
> On Thur, May 07, 2026, 11:20:52 CEST, Charles Keepax wrote:
> Does this mean faulty hardware is the most likely option? This laptop
> is barely a week old. Or is it possible the driver left the chip in a non-
> working (but potentially recoverable) state?
Yeah I am afraid this looks like a hardware problem, enumerating
on the SoundWire bus is pretty much only dependant on power
rails.
As you say there is a tiny hope the device has got into a weird
state but isn't reset on a reboot. However, given it looks from
the log like the amps were reset:
[ 14.603448] cs35l56 sdw:0:2:01fa:3557:01:2: Cirrus Logic CS35L57 Rev B2 OTP1 fw:4.2.1 (patched=0)
That patched=0 means the firmware has been wiped and that only
happens on a reset and as far as I know the resets are tied
together on this model. The very very long shot would be to let
the battery run down and leave the device for a bit to try and
super make sure the power rails went down which would also fully
reset the device. But it is definitely a long shot.
Thanks,
Charles
next prev parent reply other threads:[~2026-05-07 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 19:38 ASoC: cs42l43: SDCA reattach timeout on Dell XPS 14 Panther Lake; chip stuck across distros and kernels; worked initially; still working at hardware level Tobias Bachmann
2026-05-07 9:20 ` Charles Keepax
2026-05-07 12:32 ` Tobias Bachmann
2026-05-07 15:35 ` Charles Keepax [this message]
2026-05-07 18:53 ` Tobias Bachmann
2026-05-08 8:41 ` Charles Keepax
2026-05-08 14:56 ` Tobias Bachmann
2026-05-08 15:16 ` Charles Keepax
2026-05-08 15:21 ` Charles Keepax
2026-05-08 15:45 ` Tobias Bachmann
2026-05-08 15:56 ` Charles Keepax
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=afyxWuMCcawIE2+v@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=david.rhodes@cirrus.com \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=tobac@mailbox.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 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.