From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: alsa-devel@alsa-project.org
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
tiwai@suse.de, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
vkoul@kernel.org, broonie@kernel.org,
srinivas.kandagatla@linaro.org, jank@cadence.com,
slawomir.blauciak@intel.com,
Bard liao <yung-chuan.liao@linux.intel.com>,
Rander Wang <rander.wang@linux.intel.com>
Subject: [alsa-devel] [PATCH v2 0/5] soundwire: update ASoC interfaces
Date: Wed, 6 Nov 2019 13:00:29 -0600 [thread overview]
Message-ID: <20191106190034.4619-1-pierre-louis.bossart@linux.intel.com> (raw)
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
To avoid conflicts between ASoC and Soundwire trees, these 4 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 (of course after Vinod and
Mark sync-up so that these patches are present in both trees).
Changes since v1 (no feedback received since October 23)
additional initialization_complete utility to help codec drivers with
their resume operation, waiting for the enumeration to complete is not
always enough.
Pierre-Louis Bossart (4):
soundwire: sdw_slave: add new fields to track probe status
soundwire: add enumeration_complete structure
soundwire: add initialization_complete definition
soundwire: intel: update interfaces between ASoC and SoundWire
Rander Wang (1):
soundwire: intel: update stream callbacks for hwparams/free stream
operations
drivers/soundwire/intel.c | 20 ++++--
drivers/soundwire/intel.h | 13 ++--
drivers/soundwire/intel_init.c | 31 +++------
include/linux/soundwire/sdw.h | 13 ++++
include/linux/soundwire/sdw_intel.h | 103 +++++++++++++++++++++++++---
5 files changed, 137 insertions(+), 43 deletions(-)
--
2.20.1
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2019-11-06 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 19:00 Pierre-Louis Bossart [this message]
2019-11-06 19:00 ` [alsa-devel] [PATCH v2 1/5] soundwire: sdw_slave: add new fields to track probe status Pierre-Louis Bossart
2019-11-06 19:00 ` [alsa-devel] [PATCH v2 2/5] soundwire: add enumeration_complete structure Pierre-Louis Bossart
2019-11-06 19:00 ` [alsa-devel] [PATCH v2 3/5] soundwire: add initialization_complete definition Pierre-Louis Bossart
2019-11-06 19:00 ` [alsa-devel] [PATCH v2 4/5] soundwire: intel: update interfaces between ASoC and SoundWire Pierre-Louis Bossart
2019-11-06 19:00 ` [alsa-devel] [PATCH v2 5/5] soundwire: intel: update stream callbacks for hwparams/free stream operations 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=20191106190034.4619-1-pierre-louis.bossart@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--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=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=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;
as well as URLs for NNTP newsgroup(s).