From: Vinod Koul <vkoul@kernel.org>
To: broonie@kernel.org, Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: robh@kernel.org, devicetree@vger.kernel.org,
yung-chuan.liao@linux.intel.com,
pierre-louis.bossart@linux.intel.com, sanyog.r.kale@intel.com,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH v4 4/5] ASoC: dt-bindings: wsa881x: add bindings for port mapping
Date: Tue, 30 Mar 2021 14:31:59 +0530 [thread overview]
Message-ID: <YGLpBxw0DV3km1wM@vkoul-mobl.Dlink> (raw)
In-Reply-To: <20210315165650.13392-5-srinivas.kandagatla@linaro.org>
On 15-03-21, 16:56, Srinivas Kandagatla wrote:
> WSA881x SoundWire device ports are statically assigned to master ports
> at design time. So add bindings required to specify these mappings!
Mark, are you okay for 4, 5 to go thru sdw tree with your ack? The
patches lgtm
--
~Vinod
next prev parent reply other threads:[~2021-03-30 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 16:56 [PATCH v4 0/5] soundwire: add static port map support Srinivas Kandagatla
2021-03-15 16:56 ` [PATCH v4 1/5] soundwire: add static port mapping support Srinivas Kandagatla
2021-03-15 16:56 ` [PATCH v4 2/5] soundwire: qcom: update port map allocation bit mask Srinivas Kandagatla
2021-03-15 16:56 ` [PATCH v4 3/5] soundwire: qcom: add static port map support Srinivas Kandagatla
2021-03-15 16:56 ` [PATCH v4 4/5] ASoC: dt-bindings: wsa881x: add bindings for port mapping Srinivas Kandagatla
2021-03-24 18:22 ` Rob Herring
2021-03-30 9:01 ` Vinod Koul [this message]
2021-03-15 16:56 ` [PATCH v4 5/5] ASoC: codecs: wsa881x: add static port map support Srinivas Kandagatla
2021-03-15 17:10 ` [PATCH v4 0/5] soundwire: " Pierre-Louis Bossart
2021-04-01 7:22 ` Vinod Koul
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=YGLpBxw0DV3km1wM@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=robh@kernel.org \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.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®