From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: vkoul@kernel.org, yung-chuan.liao@linux.intel.com
Cc: pierre-louis.bossart@linux.intel.com, sanyog.r.kale@intel.com,
gregkh@linuxfoundation.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: [RFC PATCH 0/2] soundwire: add static port mapping support
Date: Wed, 20 Jan 2021 18:01:08 +0000 [thread overview]
Message-ID: <20210120180110.8357-1-srinivas.kandagatla@linaro.org> (raw)
Some of the soundwire controllers can have static functions assigned
to each port.
One Example : Master Port Num 1 and 2 are for PCM streams
Master Port 3, 4 can do PDM streams
Now Codecs that are on PDM should only assign Port 3 and 4.
simillarly PCM Codecs should be assigned port 1 and 2.
Other examples can include some usecase based mappings.
In such cases its not correct to assign/map any free port on master.
Currently there is no way to pass this static mapping from Slave to Master ports.
This patch provides a way to pass mapped port number along with the existing
port config structure during stream config, so that master can assign correct
ports based on the provided static mapping.
Srinivas Kandagatla (2):
soundwire: add support for static port mapping
soundwire: qcom: add support for static port mapping
drivers/soundwire/bus.h | 4 ++++
drivers/soundwire/qcom.c | 11 +++++++++--
drivers/soundwire/stream.c | 4 ++++
include/linux/soundwire/sdw.h | 4 ++++
4 files changed, 21 insertions(+), 2 deletions(-)
--
2.21.0
next reply other threads:[~2021-01-20 18:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 18:01 Srinivas Kandagatla [this message]
2021-01-20 18:01 ` [RFC PATCH 1/2] soundwire: add support for static port mapping Srinivas Kandagatla
2021-01-20 22:15 ` Pierre-Louis Bossart
2021-01-21 11:35 ` Srinivas Kandagatla
2021-01-21 14:56 ` Pierre-Louis Bossart
2021-01-21 15:41 ` Srinivas Kandagatla
2021-01-21 18:00 ` Pierre-Louis Bossart
2021-01-21 18:41 ` Srinivas Kandagatla
2021-01-21 21:30 ` Pierre-Louis Bossart
2021-01-22 7:05 ` Srinivas Kandagatla
2021-01-22 15:32 ` Pierre-Louis Bossart
2021-01-22 15:46 ` Srinivas Kandagatla
2021-01-22 16:42 ` Pierre-Louis Bossart
2021-01-25 16:23 ` Srinivas Kandagatla
2021-02-01 10:27 ` Vinod Koul
2021-02-19 10:35 ` Srinivas Kandagatla
2021-02-19 19:52 ` Pierre-Louis Bossart
2021-02-22 13:40 ` Srinivas Kandagatla
2021-01-20 18:01 ` [RFC PATCH 2/2] soundwire: qcom: " Srinivas Kandagatla
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=20210120180110.8357-1-srinivas.kandagatla@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--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
all inboxes | Powered by JetHome®