From: Shreyas NC <shreyas.nc@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 <shreyas.nc@intel.com>,
sanyog.r.kale@intel.com
Subject: [PATCH v8 04/10] Documentation: soundwire: Add documentation for multi link
Date: Fri, 27 Jul 2018 14:44:11 +0530 [thread overview]
Message-ID: <1532682857-604-5-git-send-email-shreyas.nc@intel.com> (raw)
In-Reply-To: <1532682857-604-1-git-send-email-shreyas.nc@intel.com>
From: Sanyog Kale <sanyog.r.kale@intel.com>
Add example and documentation to describe multi link streams
Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Signed-off-by: Sanyog Kale <sanyog.r.kale@intel.com>
Signed-off-by: Vinod Koul <vkoul@kernel.org>
Signed-off-by: Shreyas NC <shreyas.nc@intel.com>
---
Documentation/driver-api/soundwire/stream.rst | 28 +++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/Documentation/driver-api/soundwire/stream.rst b/Documentation/driver-api/soundwire/stream.rst
index 29121aa..19482ee 100644
--- a/Documentation/driver-api/soundwire/stream.rst
+++ b/Documentation/driver-api/soundwire/stream.rst
@@ -101,6 +101,34 @@ interface. ::
+--------------------+ | |
+----------------+
+Example 5: Stereo Stream with L and R channel is rendered by 2 Masters, each
+rendering one channel, and is received by two different Slaves, each
+receiving one channel. Both Masters and both Slaves are using single port. ::
+
+ +---------------+ Clock Signal +---------------+
+ | Master +----------------------------------+ Slave |
+ | Interface | | Interface |
+ | 1 | | 1 |
+ | | Data Signal | |
+ | L +----------------------------------+ L |
+ | (Data) | Data Direction | (Data) |
+ +---------------+ +-----------------------> +---------------+
+
+ +---------------+ Clock Signal +---------------+
+ | Master +----------------------------------+ Slave |
+ | Interface | | Interface |
+ | 2 | | 2 |
+ | | Data Signal | |
+ | R +----------------------------------+ R |
+ | (Data) | Data Direction | (Data) |
+ +---------------+ +-----------------------> +---------------+
+
+Note: In multi-link cases like above, to lock, one would acquire a global
+lock and then go on locking bus instances. But, in this case the caller
+framework(ASoC DPCM) guarantees that stream operations on a card are
+always serialized. So, there is no race condition and hence no need for
+global lock.
+
SoundWire Stream Management flow
================================
--
2.7.4
next prev parent reply other threads:[~2018-07-27 9:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 9:14 [PATCH v8 00/10] soundwire: Add multi link support Shreyas NC
2018-07-27 9:14 ` [PATCH v8 01/10] soundwire: Fix duplicate stream state assignment Shreyas NC
2018-07-27 9:14 ` [PATCH v8 02/10] soundwire: Fix incorrect exit after configuring stream Shreyas NC
2018-07-27 9:14 ` [PATCH v8 03/10] soundwire: Fix acquiring bus lock twice during master release Shreyas NC
2018-07-27 9:14 ` Shreyas NC [this message]
2018-07-27 9:14 ` [PATCH v8 05/10] soundwire: Initialize completion for defer messages Shreyas NC
2018-07-27 9:14 ` [PATCH v8 06/10] soundwire: Add support to lock across bus instances Shreyas NC
2018-07-27 9:14 ` [PATCH v8 07/10] soundwire: Handle multiple master instances in a stream Shreyas NC
2018-07-27 9:14 ` [PATCH v8 08/10] soundwire: keep track of Masters " Shreyas NC
2018-07-27 9:14 ` [PATCH v8 09/10] soundwire: Add support for multi link bank switch Shreyas NC
2018-07-27 9:14 ` [PATCH v8 10/10] soundwire: intel: Add pre/post bank switch ops Shreyas NC
2018-07-27 15:12 ` [PATCH v8 00/10] soundwire: Add multi link support Pierre-Louis Bossart
2018-08-07 6:51 ` Vinod
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=1532682857-604-5-git-send-email-shreyas.nc@intel.com \
--to=shreyas.nc@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=sanyog.r.kale@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).