From: Rob Herring <robh@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: robh@kernel.org, vkoul@kernel.org, broonie@kernel.org,
bgoswami@codeaurora.org, pierre-louis.bossart@linux.intel.com,
devicetree@vger.kernel.org, lgirdwood@gmail.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
spapothi@codeaurora.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH v4 1/2] dt-bindings: soundwire: add bindings for Qcom controller
Date: Mon, 4 Nov 2019 19:49:06 -0600 [thread overview]
Message-ID: <20191105014906.GA32550@bogus> (raw)
In-Reply-To: <20191030153150.18303-2-srinivas.kandagatla@linaro.org>
On Wed, 30 Oct 2019 15:31:49 +0000, Srinivas Kandagatla wrote:
> This patch adds bindings for Qualcomm soundwire controller.
>
> Qualcomm SoundWire Master controller is present in most Qualcomm SoCs
> either integrated as part of WCD audio codecs via slimbus or
> as part of SOC I/O.
>
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> ---
> .../bindings/soundwire/qcom,sdw.txt | 179 ++++++++++++++++++
> 1 file changed, 179 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/soundwire/qcom,sdw.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-11-05 1:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 15:31 [PATCH v4 0/2] soundwire: Add support to Qualcomm SoundWire master Srinivas Kandagatla
2019-10-30 15:31 ` [PATCH v4 1/2] dt-bindings: soundwire: add bindings for Qcom controller Srinivas Kandagatla
2019-11-05 1:49 ` Rob Herring [this message]
2019-10-30 15:31 ` [PATCH v4 2/2] soundwire: qcom: add support for SoundWire controller Srinivas Kandagatla
2019-10-30 16:28 ` [alsa-devel] " Pierre-Louis Bossart
2019-11-01 16:17 ` Srinivas Kandagatla
2019-11-01 16:39 ` Pierre-Louis Bossart
2019-11-01 17:22 ` Srinivas Kandagatla
2019-11-01 17:52 ` Pierre-Louis Bossart
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=20191105014906.GA32550@bogus \
--to=robh@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=spapothi@codeaurora.org \
--cc=srinivas.kandagatla@linaro.org \
--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).