Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Tobias Bachmann <tobac@mailbox.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
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, 08 May 2026 17:45:19 +0200	[thread overview]
Message-ID: <77iVa-LES8uCgAj99Tw0vA@mailbox.org> (raw)
In-Reply-To: <af3/iDwepJuCaJNm@opensource.cirrus.com>

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:
> > > 
> > > From what I can gather, the audio path doesn't appear to gate on
> > > _STA
> > > for this device:
> > > - soundwire sdw-master-0-0 still reports SDW Slave Addr
> > > 
> > >   3001fa424501
> > > 
> > > - ACPI still announces the SDCA functions: device:29 SmartMic,
> > > 
> > >   device:2a UAJ, device:2b HID
> > > 
> > > - sdca_class still binds and reaches "probe complete"
> > > - sdca_class sdw:0:0:01fa:4245:01: timed out waiting for
> > > 
> > >   device re-attach (5s after probe complete)
> > > 
> > > - No soundcard created
> > 
> > Hmm... yeah I think maybe your kernel is missing:
> > 
> > de67b4ea168f ("soundwire: slave: Don't register devices that are
> > disabled in ACPI")
> > 
> > I think that was only moved into Linus's tree after v7.0. If
> > possible you could pull that in and retest.
> 
> 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 :)

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.

Best wishes,
Tobias




  reply	other threads:[~2026-05-08 15:45 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 [this message]
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=77iVa-LES8uCgAj99Tw0vA@mailbox.org \
    --to=tobac@mailbox.org \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=david.rhodes@cirrus.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.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