From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH v3] ASoC: cs35l56: Fix probe deadlock waiting for SoundWire enumeration
Date: Tue, 1 Sep 2026 16:50:10 +0100 [thread overview]
Message-ID: <17e7b179-bdfd-44a7-be3c-b206910780c7@opensource.cirrus.com> (raw)
In-Reply-To: <627c6780-2a5b-4956-ae26-6ca6d13a41c0@sirena.org.uk>
On 01/09/2026 4:48 pm, Mark Brown wrote:
> On Tue, Sep 01, 2026 at 04:38:37PM +0100, Richard Fitzgerald wrote:
>> On 01/09/2026 4:18 pm, Mark Brown wrote:
>
>>> I'll apply this since it's very much a corner case and there's a real
>>> problem but you should probably check out the kexec case - it looks like
>>> it misses freeze_kernel_threads(). TBH I'm not sure the issue there
>>> isn't on the kexec side, it's not exactly a common case and having a
>>> difference like that feels like asking for trouble.
>
>> I think you are asking for a shutdown() handler that cancels the
>> work.... ?
>
> I didn't really look at what would be a good solution TBHi, that looks
> plausible at first glance.
>
>> If I've got that right, this isn't so urgent that I can't do a V4 with
>> that change.
>
> I've already pushed this version into CI.
Ok. I can do a follow-up patch to add some extra protection.
next prev parent reply other threads:[~2026-09-01 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 12:26 [PATCH v3] ASoC: cs35l56: Fix probe deadlock waiting for SoundWire enumeration Richard Fitzgerald
2026-09-01 15:18 ` Mark Brown
2026-09-01 15:38 ` Richard Fitzgerald
2026-09-01 15:48 ` Mark Brown
2026-09-01 15:50 ` Richard Fitzgerald [this message]
2026-09-01 15:21 ` Mark Brown
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=17e7b179-bdfd-44a7-be3c-b206910780c7@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@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 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.