From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Srinivas Kandagatla <srini@kernel.org>
Cc: broonie@kernel.org, vkoul@kernel.org, lee@kernel.org,
lgirdwood@gmail.com, pierre-louis.bossart@linux.dev,
yung-chuan.liao@linux.intel.com, peter.ujfalusi@linux.intel.com,
oder_chiou@realtek.com, jack.yu@realtek.com,
shumingf@realtek.com, linux-sound@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH v2 01/10] soundwire: Always wait for initialisation of unattached devices
Date: Fri, 5 Jun 2026 17:10:58 +0100 [thread overview]
Message-ID: <aiL1El3HOOKAja7q@opensource.cirrus.com> (raw)
In-Reply-To: <371781e9-6c5f-486f-a0ca-ef6e59b91a1e@kernel.org>
On Fri, Jun 05, 2026 at 12:43:24PM +0100, Srinivas Kandagatla wrote:
> some minor typos in commit msg.
>
> On 6/5/26 9:48 AM, Charles Keepax wrote:
> > Currently in sdw_slave_wait_for_init() the waiting can be skipped
> > if unattach_request is not set. Doing so was added in [1] likely
> > because the core used to do a complete() on the completion so
> > waiting in the case an unattach hadn't actually happened would
> > block for the full timeout. However patch [2] updated the core to
> > use complete_all() which means that the wait_for_completion() will
> > now simply return if the device is already attached skipping the
> > completion doesn't add much.
> >
> > Additionally, unatttach_request is only set if the host initiates
>
> s/unatttach/unattach
>
> > a bus reset. However, the host doing a bus reset is not the only
> > reason a device may be unattached from the bus. Other options
> > could include the driver probing before the device enumerates, a
> > sync-loss, or the device itself powering down.
> >
> > Removing the skip using unattached_request, doesn't cost much in
> > terms of efficiency and allows the sdw_slave_wiat_for_init() helper
> s/wiat/wait
>
Thanks I will do a spin early next week for these typos.
Thanks,
Charles
next prev parent reply other threads:[~2026-06-05 16:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 8:48 [PATCH v2 00/10] Expand SoundWire enumeration helper coverage Charles Keepax
2026-06-05 8:48 ` [PATCH v2 01/10] soundwire: Always wait for initialisation of unattached devices Charles Keepax
2026-06-05 11:43 ` Srinivas Kandagatla
2026-06-05 16:10 ` Charles Keepax [this message]
2026-06-05 8:48 ` [PATCH v2 02/10] ASoC: wsa881x: Use new SoundWire enumeration helper Charles Keepax
2026-06-05 8:48 ` [PATCH v2 03/10] mfd: cs42l43: " Charles Keepax
2026-06-05 8:48 ` [PATCH v2 04/10] ASoC: rt5682: " Charles Keepax
2026-06-05 8:48 ` [PATCH v2 05/10] ASoC: pm4125: " Charles Keepax
2026-06-05 8:48 ` [PATCH v2 06/10] ASoC: wcd937x: " Charles Keepax
2026-06-05 8:48 ` [PATCH v2 07/10] ASoC: wcd938x: " Charles Keepax
2026-06-05 8:48 ` [PATCH v2 08/10] ASoC: wcd939x: " Charles Keepax
2026-06-05 8:48 ` [PATCH v2 09/10] ASoC: SDCA: " Charles Keepax
2026-06-05 8:48 ` [PATCH v2 10/10] ASoC: cs35l56: Remove unnecessary conditionals waiting for enumeration Charles Keepax
2026-06-05 11:42 ` [PATCH v2 00/10] Expand SoundWire enumeration helper coverage Srinivas Kandagatla
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=aiL1El3HOOKAja7q@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=jack.yu@realtek.com \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=patches@opensource.cirrus.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=shumingf@realtek.com \
--cc=srini@kernel.org \
--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 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.