From: Sanyog Kale <sanyog.r.kale@intel.com>
To: alsa-devel@alsa-project.org
Cc: patches.audio@intel.com, gregkh@linuxfoundation.org,
pierre-louis.bossart@linux.intel.com, vkoul@kernel.org,
shreyas.nc@intel.com, sanyog.r.kale@intel.com
Subject: [PATCH v6 00/10] soundwire: Add multi link support
Date: Tue, 17 Jul 2018 00:17:03 +0530 [thread overview]
Message-ID: <20180716184713.13356-1-sanyog.r.kale@intel.com> (raw)
Currently, in the SoundWire subsystem, the concept of stream is limited
to a Master and one or more Slaves(Codecs). This series aims to add
support for multiple Master(s) sharing the same reference clock and
synchronized in the hardware.
This patch series adds:
- Fix to avoid duplicate stream state assignment
- Avoid incorrect stream release after configuring Master
- Helpers to lock bus instances part of the stream
- Boiler plate conversion of code to support a list of Master runtime
- Support multi link bank switch to support synchronization between
multiple masters
- Add Intel platform ops for pre/post bank switch
- Fix to avoid bus lock acquired twice
changes in v6:
- Add patch to fix acquiring bus lock twice during master release
- In sdw_stream_add_master(), perform multi link check at start of
function as suggested by Pierre
- Minor comment fixes
changes in v5:
- Add patch to fix duplicate stream state assignment
- fix incorrect exit which was releasing the stream after configuring master
- In sdw_release_bus_lock(), release the mutex in reverse order as
suggested by Takashi
changes in v4:
- Added changes in sdw_stream_runtime structure to track Masters
added to stream
- Add changes to support ml_bankswitch only if both the hardware supports
and the stream is handled by multiple masters
Sanyog Kale (3):
Documentation: soundwire: Add documentation for multi link
soundwire: Add support to lock across bus instances
soundwire: Fix acquiring bus lock twice during master release
Shreyas NC (6):
soundwire: Initialize completion for defer messages
soundwire: Fix duplicate stream state assignment
soundwire: fix incorrect exit after configuring stream
soundwire: keep track of Masters in a stream
soundwire: Add support for multi link bank switch
soundwire: intel: Add pre/post bank switch ops
Vinod Koul (1):
soundwire: Handle multiple master instances in a stream
Documentation/driver-api/soundwire/stream.rst | 28 ++
drivers/soundwire/bus.c | 6 +
drivers/soundwire/bus.h | 4 +
drivers/soundwire/intel.c | 65 ++++
drivers/soundwire/stream.c | 511 +++++++++++++++++++-------
include/linux/soundwire/sdw.h | 12 +-
6 files changed, 489 insertions(+), 137 deletions(-)
--
2.13.0
next reply other threads:[~2018-07-16 18:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 18:47 Sanyog Kale [this message]
2018-07-16 18:47 ` [PATCH v6 01/10] Documentation: soundwire: Add documentation for multi link Sanyog Kale
2018-07-16 18:47 ` [PATCH v6 02/10] soundwire: Initialize completion for defer messages Sanyog Kale
2018-07-16 18:47 ` [PATCH v6 03/10] soundwire: Fix duplicate stream state assignment Sanyog Kale
2018-07-16 18:47 ` [PATCH v6 04/10] soundwire: fix incorrect exit after configuring stream Sanyog Kale
2018-07-16 18:47 ` [PATCH v6 05/10] soundwire: Add support to lock across bus instances Sanyog Kale
2018-07-16 18:47 ` [PATCH v6 06/10] soundwire: Handle multiple master instances in a stream Sanyog Kale
2018-07-16 18:47 ` [PATCH v6 07/10] soundwire: keep track of Masters " Sanyog Kale
2018-07-19 15:06 ` Pierre-Louis Bossart
2018-07-20 4:43 ` Vinod
2018-07-23 4:00 ` Sanyog Kale
2018-07-23 3:50 ` Sanyog Kale
2018-07-16 18:47 ` [PATCH v6 08/10] soundwire: Add support for multi link bank switch Sanyog Kale
2018-07-16 18:47 ` [PATCH v6 09/10] soundwire: intel: Add pre/post bank switch ops Sanyog Kale
2018-07-16 18:47 ` [PATCH v6 10/10] soundwire: Fix acquiring bus lock twice during master release Sanyog Kale
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=20180716184713.13356-1-sanyog.r.kale@intel.com \
--to=sanyog.r.kale@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=gregkh@linuxfoundation.org \
--cc=patches.audio@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=shreyas.nc@intel.com \
--cc=vkoul@kernel.org \
/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).