From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: Charles Keepax <ckeepax@opensource.cirrus.com>, vkoul@kernel.org
Cc: yung-chuan.liao@linux.intel.com, peter.ujfalusi@linux.intel.com,
linux-sound@vger.kernel.org, patches@opensource.cirrus.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Allow SoundWire devices to communicate during remove
Date: Tue, 29 Sep 2026 20:34:54 +0200 [thread overview]
Message-ID: <5aab68e8-7ce9-46e1-9dd1-5cc226560096@linux.dev> (raw)
In-Reply-To: <20260925154216.3520136-1-ckeepax@opensource.cirrus.com>
On 9/25/26 17:42, Charles Keepax wrote:
> Currently on Intel systems SoundWire drivers can't communicate with the
> device during driver removal. This is primarily because the IRQs are
> disabled before the driver remove callback is run. The result of this is
> such transactions timeout causing a) a lot of errors in the log and b)
> driver remove to take a very long time.
>
> This issue affects cs42l43 and cs42l45, primarily due to both using
> regmap IRQ.
>
> soundwire_intel soundwire_intel.link.0: IO transfer timed out, cmd 3 device 6 addr 5d len 1
> soundwire sdw-master-0-0: trf on Slave 6 failed:-110 write addr 5d count 0
> sdca_class sdw:0:0:01fa:4245:01: Failed to sync masks in 5d
>
> As regmap IRQ is torn down it will mask the interrupts that are
> removed. However, there are many valid reasons a driver might want
> communicate with the device during removal, others would include
> disabling jack detection, putting the device into the lowest possible
> power state to save power, etc.
>
> This patch set attempts to address this problem trying to locate the
> reason interrupts are disabled, fixing that and then leaving the IRQs
> enabled for the remove callback.
>
> Thanks,
> Charles
>
> Changes since v1:
> - Add a new helper to destroy the children on the bus separately, this
> allows the IRQs to be disabled for final cleanup.
> - Split device_unregister into device_del and put_device.
>
> Changes since v1:
> - Add a new helper to destroy the children on the bus separately, this
> allows the IRQs to be disabled for final cleanup.
> - Split device_unregister into device_del and put_device.
>
> Charles Keepax (3):
> soundwire: bus: Don't unassign dev_num before unregistering device
> soundwire: bus: Expose a helper to remove devices from the bus
> soundwire: intel_auxdevice: Don't disable IRQs before removing
> children
I've run out of objections and can't think of a better solution, so for
the patchset:
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
Thanks Charles!
prev parent reply other threads:[~2026-09-29 18:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 15:42 Charles Keepax
2026-09-25 15:42 ` [PATCH v2 1/3] soundwire: bus: Don't unassign dev_num before unregistering device Charles Keepax
2026-09-25 15:42 ` [PATCH v2 2/3] soundwire: bus: Expose a helper to remove devices from the bus Charles Keepax
2026-09-25 15:42 ` [PATCH v2 3/3] soundwire: intel_auxdevice: Don't disable IRQs before removing children Charles Keepax
2026-09-26 15:55 ` Pierre-Louis Bossart
2026-09-28 8:39 ` Charles Keepax
2026-09-29 8:34 ` Pierre-Louis Bossart
2026-09-29 12:40 ` Charles Keepax
2026-09-29 18:31 ` Pierre-Louis Bossart
2026-09-29 18:34 ` Pierre-Louis Bossart [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=5aab68e8-7ce9-46e1-9dd1-5cc226560096@linux.dev \
--to=pierre-louis.bossart@linux.dev \
--cc=ckeepax@opensource.cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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
all inboxes | Powered by JetHome®