Linux Sound subsystem development
 help / color / mirror / Atom feed
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 10:20:52 +0100	[thread overview]
Message-ID: <afxZdCOyzzwocQON@opensource.cirrus.com> (raw)
In-Reply-To: <cLVwl4lrR76pLtv8VxMSaA@mailbox.org>

On Wed, May 06, 2026 at 09:38:27PM +0200, Tobias Bachmann wrote:
> Hi all,
> 
> I'm hitting a persistent CS42L43 SDCA reattach timeout on a Dell XPS 14
> (Panther Lake) that I haven't been able to clear via any software means. Audio 
> worked correctly for several days after Arch Linux (with CachyOS kernel) 
> install, then stopped without any change in hardware, kernel version or audio-
> related software stack and has not recovered since across multiple kernels and 
> distributions.

Could I just double check when you say the sound is working
under Windows/Dell SupportAssist does that definitely include
the headphones?

The cs42l45 (note it is l45 here) only drives the headphones
and the cs35l57 drives the speakers. On Linux as these are all
bundled together into a soundcard, the cs42l45 failing to probe
will be affecting all audio, however on Windows I suspect each
is treated separately. So the speakers may continue to function
even if the headphones are broken.

Thanks for reporting this, apologies for the trouble. We will
have a look through the logs and see what we can come up with.

Thanks,
Charles

  reply	other threads:[~2026-05-07  9:21 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 [this message]
2026-05-07 12:32   ` Tobias Bachmann
2026-05-07 15:35     ` Charles Keepax
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=afxZdCOyzzwocQON@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox