From: Vinod Koul <vkoul@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
tiwai@suse.de, broonie@kernel.org, gregkh@linuxfoundation.org,
jank@cadence.com, srinivas.kandagatla@linaro.org,
slawomir.blauciak@intel.com,
Bard liao <yung-chuan.liao@linux.intel.com>,
Rander Wang <rander.wang@linux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Subject: Re: [PATCH v5 00/11] soundwire: update ASoC interfaces
Date: Thu, 12 Dec 2019 09:19:26 +0530 [thread overview]
Message-ID: <20191212034926.GK2536@vkoul-mobl> (raw)
In-Reply-To: <20191212014507.28050-1-pierre-louis.bossart@linux.intel.com>
On 11-12-19, 19:44, Pierre-Louis Bossart wrote:
> We need new fields in existing structures to
> a) deal with race conditions on codec probe/enumeration
> b) allow for multi-step ACPI scan/probe/startup on Intel plaforms
> c) deal with MSI issues using a single handler/threads for all audio
> interrupts
> d) deal with access to registers shared across multiple links on Intel
> platforms
>
> These structures for a) will be used by the SOF driver as well as
> codec drivers. The b) c) and d) cases are only for the Intel-specific
> implementation.
>
> To avoid conflicts between ASoC and Soundwire trees, these 11 patches
> are provided out-of-order, before the functionality enabled in these
> header files is added in follow-up patch series which can be applied
> separately in the ASoC and Soundwire trees. As discussed earlier,
> Vinod would need to provide an immutable tag for Mark Brown, and the
> integration on the ASoC side of SOF changes and new codecs drivers can
> proceed in parallel with SoundWire core changes.
>
> I had multiple offline discussions with Vinod/Mark/Takashi on how to
> proceed withe volume of SoundWire changes. Now that v5.5-rc1 is out we
> should go ahead with these interface changes.
>
> The next patchset "[PATCH v3 00/15] soundwire: intel: implement new
> ASoC interfaces" can still be reviewed but will not apply as is due to
> a one-line conflict. An update will be provided when Vinod applies
> this series to avoid noise on mailing lists.
>
> An update for the series "[PATCH v3 00/22] soundwire: code hardening
> and suspend-resume support" is ready but will be provided when both
> the interfaces changes and the implementation changes are merged.
Applied, thanks
I will send the tag tomorrow after it is in next
Thanks
--
~Vinod
next prev parent reply other threads:[~2019-12-12 3:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 1:44 [PATCH v5 00/11] soundwire: update ASoC interfaces Pierre-Louis Bossart
2019-12-12 1:44 ` [PATCH v5 01/11] soundwire: sdw_slave: add probe_complete structure and new fields Pierre-Louis Bossart
2019-12-12 1:44 ` [PATCH v5 02/11] soundwire: sdw_slave: add enumeration_complete structure Pierre-Louis Bossart
2019-12-12 1:44 ` [PATCH v5 03/11] soundwire: sdw_slave: add initialization_complete definition Pierre-Louis Bossart
2019-12-12 1:45 ` [PATCH v5 04/11] soundwire: sdw_slave: track unattach_request to handle all init sequences Pierre-Louis Bossart
2019-12-12 1:45 ` [PATCH v5 05/11] soundwire: intel: update interfaces between ASoC and SoundWire Pierre-Louis Bossart
2019-12-12 1:45 ` [PATCH v5 06/11] soundwire: intel: update stream callbacks for hwparams/free stream operations Pierre-Louis Bossart
2019-12-12 1:45 ` [PATCH v5 07/11] soundwire: intel: update headers for interrupts Pierre-Louis Bossart
2019-12-12 1:45 ` [PATCH v5 08/11] soundwire: intel: add link_list to handle interrupts with a single thread Pierre-Louis Bossart
2019-12-12 1:45 ` [PATCH v5 09/11] soundwire: intel: add prototype for WAKEEN interrupt processing Pierre-Louis Bossart
2019-12-12 1:45 ` [PATCH v5 10/11] soundwire: intel: add mutex for shared SHIM register access Pierre-Louis Bossart
2019-12-12 1:45 ` [PATCH v5 11/11] soundwire: intel: add clock stop quirks Pierre-Louis Bossart
2019-12-12 3:49 ` Vinod Koul [this message]
2019-12-12 14:37 ` [alsa-devel] [PATCH v5 00/11] soundwire: update ASoC interfaces Pierre-Louis Bossart
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=20191212034926.GK2536@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=slawomir.blauciak@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).