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 08/10] soundwire: keep track of Masters in a stream
Date: Fri, 27 Jul 2018 14:44:15 +0530 [thread overview]
Message-ID: <1532682857-604-9-git-send-email-shreyas.nc@intel.com> (raw)
In-Reply-To: <1532682857-604-1-git-send-email-shreyas.nc@intel.com>
A multi link bankswitch can be done if the hardware supports and
the stream is handled by multiple Master(s).
This preparatory patch adds support to track m_rt in a stream.
Modifying m_rt_count and usage is added as part of the next patch.
Signed-off-by: Shreyas NC <shreyas.nc@intel.com>
---
drivers/soundwire/stream.c | 1 +
include/linux/soundwire/sdw.h | 2 ++
2 files changed, 3 insertions(+)
diff --git a/drivers/soundwire/stream.c b/drivers/soundwire/stream.c
index 0d04d84..088b939 100644
--- a/drivers/soundwire/stream.c
+++ b/drivers/soundwire/stream.c
@@ -759,6 +759,7 @@ struct sdw_stream_runtime *sdw_alloc_stream(char *stream_name)
stream->name = stream_name;
INIT_LIST_HEAD(&stream->master_list);
stream->state = SDW_STREAM_ALLOCATED;
+ stream->m_rt_count = 0;
return stream;
}
diff --git a/include/linux/soundwire/sdw.h b/include/linux/soundwire/sdw.h
index 03df709..214e146 100644
--- a/include/linux/soundwire/sdw.h
+++ b/include/linux/soundwire/sdw.h
@@ -771,6 +771,7 @@ struct sdw_stream_params {
* @master_list: List of Master runtime(s) in this stream.
* master_list can contain only one m_rt per Master instance
* for a stream
+ * @m_rt_count: Count of Master runtime(s) in this stream
*/
struct sdw_stream_runtime {
char *name;
@@ -778,6 +779,7 @@ struct sdw_stream_runtime {
enum sdw_stream_state state;
enum sdw_stream_type type;
struct list_head master_list;
+ int m_rt_count;
};
struct sdw_stream_runtime *sdw_alloc_stream(char *stream_name);
--
2.7.4
next prev parent reply other threads:[~2018-07-27 9:15 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 ` [PATCH v8 04/10] Documentation: soundwire: Add documentation for multi link Shreyas NC
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 ` Shreyas NC [this message]
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-9-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).