From: Vinod Koul <vkoul@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: broonie@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, niranjan.hy@ti.com,
shenghao-ding@ti.com, kevin-lu@ti.com, baojun.xu@ti.com,
sen@ti.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH v2 01/18] soundwire: Add a helper function to wait for device initialisation
Date: Mon, 11 May 2026 21:51:44 +0530 [thread overview]
Message-ID: <agICGFaDZCpu_Nym@vaman> (raw)
In-Reply-To: <20260511141029.851125-2-ckeepax@opensource.cirrus.com>
On 11-05-26, 15:10, Charles Keepax wrote:
> Add a new helper function to wait for the device to enumerate
> and be initialised by the SoundWire core. Most of the SoundWire
> drivers have very similar boiler plate code in their runtime
> resume, and that boiler plate tends to access various internals
> of the SoundWire structs which is a mild layering violation.
>
> Adding a new core helper function greatly eases both of these
> issues.
Acked-by: Vinod Koul <vkoul@kernel.org>
--
~Vinod
next prev parent reply other threads:[~2026-05-11 16:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 14:10 [PATCH v2 00/18] Add a new SoundWire enumeration helper Charles Keepax
2026-05-11 14:10 ` [PATCH v2 01/18] soundwire: Add a helper function to wait for device initialisation Charles Keepax
2026-05-11 16:21 ` Vinod Koul [this message]
2026-05-12 0:51 ` Mark Brown
2026-05-12 8:39 ` Charles Keepax
2026-05-11 14:10 ` [PATCH v2 02/18] ASoC: cs35l56: Use new SoundWire enumeration helper Charles Keepax
2026-05-11 14:10 ` [PATCH v2 03/18] ASoC: cs42l42: " Charles Keepax
2026-05-11 14:10 ` [PATCH v2 04/18] ASoC: max98363: " Charles Keepax
2026-05-11 14:10 ` [PATCH v2 05/18] ASoC: max98373: " Charles Keepax
2026-05-11 14:10 ` [PATCH v2 06/18] ASoC: rt700: " Charles Keepax
2026-05-11 14:10 ` [PATCH v2 07/18] ASoC: rt711: " Charles Keepax
2026-05-11 14:10 ` [PATCH v2 08/18] ASoC: rt712: " Charles Keepax
2026-05-11 14:10 ` [PATCH v2 09/18] ASoC: rt715: " Charles Keepax
2026-05-11 14:10 ` [PATCH v2 10/18] ASoc: rt721: " Charles Keepax
2026-05-11 14:10 ` [PATCH v2 11/18] ASoC: rt722: " Charles Keepax
2026-05-11 14:10 ` [PATCH v2 12/18] ASoC: rt1017: " Charles Keepax
2026-05-11 14:10 ` [PATCH v2 13/18] ASoC: rt1308: " Charles Keepax
2026-05-11 14:10 ` [PATCH v2 14/18] ASoC: rt1316: " Charles Keepax
2026-05-11 14:10 ` [PATCH v2 15/18] ASoC: rt1318: " Charles Keepax
2026-05-11 14:10 ` [PATCH v2 16/18] ASoC: rt1320: " Charles Keepax
2026-05-11 14:10 ` [PATCH v2 17/18] ASoC: rt5682: " Charles Keepax
2026-05-11 14:10 ` [PATCH v2 18/18] ASoC: tas2783: " 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=agICGFaDZCpu_Nym@vaman \
--to=vkoul@kernel.org \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=jack.yu@realtek.com \
--cc=kevin-lu@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=niranjan.hy@ti.com \
--cc=oder_chiou@realtek.com \
--cc=patches@opensource.cirrus.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=sen@ti.com \
--cc=shenghao-ding@ti.com \
--cc=shumingf@realtek.com \
--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.