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: Fri, 8 May 2026 16:56:49 +0100	[thread overview]
Message-ID: <af4HwRd7ePL/Ildc@opensource.cirrus.com> (raw)
In-Reply-To: <77iVa-LES8uCgAj99Tw0vA@mailbox.org>

On Fri, May 08, 2026 at 05:45:19PM +0200, Tobias Bachmann wrote:
> On Fri, May 08, 2026 at 5:21:44PM CEST, Charles Keepax wrote:
> > On Fri, May 08, 2026 at 04:16:19PM +0100, Charles Keepax wrote:
> > > On Fri, May 08, 2026 at 04:56:03PM +0200, Tobias Bachmann wrote:
> > > > On Fri, May 08, 2026 at 10:41:10AM CEST, Charles Keepax wrote:
> > Although I am little worried more might be required looking
> > more closely. But let me know if you can test how it gets on
> > otherwise I will add it to my list to poke. I think last time I
> > tested that it was for a device that didn't also have a bunch of
> > SDCA stuff and some of that runs through a different path so
> > little nervous that might need a gate too.
> 
> Fortunately not. Tested on 7.1.0-rc2 and the speakers work fine. Lovely 
> stuff :)

Awesome sauce. Always nice when things go slightly better than
expected.

> This is probably a very unique solution to a unique problem. But I'd be 
> happy to test patches etc if you can use this information to foolproof 
> the architecture, which might help others.

Thanks, that is very generous of you. Full disclosure, most of
this SDCA stuff is still fairly new to the kernel so the basics
are keeping me/us pretty busy at the moment. Unlikely I am
going to get time to look at this in a lot of detail in the short
term. But it would be nice if we can do something here in the
future.

I think the biggest hurdle really is that a lot of this soundcard
stuff is decided before the devices themselves actually bind to
drivers. So it's easy to make it conditional off the contents of
the ACPI but hard to make it conditional off the dynamic state
of the system.

Thanks,
Charles

      reply	other threads:[~2026-05-08 15:57 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
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 [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=af4HwRd7ePL/Ildc@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