From: Vinod Koul <vkoul@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: lee@kernel.org, yung-chuan.liao@linux.intel.com,
pierre-louis.bossart@linux.dev, linux-sound@vger.kernel.org,
patches@opensource.cirrus.com, mfd@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] soundwire: Add a helper function to indicate a device will detach
Date: Sat, 3 Oct 2026 09:56:59 +0200 [thread overview]
Message-ID: <asC1SwHb4DZkJ4Pr@parshuram> (raw)
In-Reply-To: <20260831140157.1736905-2-ckeepax@opensource.cirrus.com>
On 31-08-26, 15:01, Charles Keepax wrote:
> SoundWire devices will sometimes need to reset themselves,
> typical times might include when taking over the device to ensure
> a consistent state or after downloading a firmware update to boot
> into the new version. Often such a reset will also result in the
> device detaching from the SoundWire bus, in this case the driver
> has to be careful. Naively calling sdw_slave_wait_for_init()
> after doing the reset could immediately succeed if the bus hasn't
> seen the detach yet, causing the driver to proceed attempting
> to communicate with the device whilst it is detached.
>
> Add a helper function that a driver can call to indicate it is
> about to initiate an action that will cause the device to detach
> from the bus. This will reinit the completions in the peripheral
> for device attach, ensuring that the next sdw_slave_wait_for_init()
> will not complete before the detach has been seen by the core.
Acked-by: Vinod Koul <vkoul@kernel.org>
--
~Vinod
next prev parent reply other threads:[~2026-10-03 7:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 14:01 [PATCH v2 0/2] Add SoundWire detach helper Charles Keepax
2026-08-31 14:01 ` [PATCH v2 1/2] soundwire: Add a helper function to indicate a device will detach Charles Keepax
2026-10-03 7:56 ` Vinod Koul [this message]
2026-08-31 14:01 ` [PATCH v2 2/2] mfd: cs42l43: Move to core detach helper Charles Keepax
2026-09-16 15:21 ` Lee Jones
2026-09-16 16:01 ` Charles Keepax
2026-09-04 7:20 ` [PATCH v2 0/2] Add SoundWire " Pierre-Louis Bossart
2026-09-17 10:59 ` Lee Jones
2026-10-03 7:58 ` Vinod Koul
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=asC1SwHb4DZkJ4Pr@parshuram \
--to=vkoul@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mfd@lists.linux.dev \
--cc=patches@opensource.cirrus.com \
--cc=pierre-louis.bossart@linux.dev \
--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®