From: Vinod Koul <vkoul@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: robh@kernel.org, alsa-devel@alsa-project.org,
bgoswami@codeaurora.org, linux-kernel@vger.kernel.org,
spapothi@codeaurora.org, pierre-louis.bossart@linux.intel.com,
lgirdwood@gmail.com, broonie@kernel.org
Subject: Re: [alsa-devel] [PATCH v6 0/2] soundwire: Add support to Qualcomm SoundWire master
Date: Tue, 14 Jan 2020 12:00:06 +0530 [thread overview]
Message-ID: <20200114063006.GE2818@vkoul-mobl> (raw)
In-Reply-To: <20200113132153.27239-1-srinivas.kandagatla@linaro.org>
On 13-01-20, 13:21, Srinivas Kandagatla wrote:
> Thanks for reviewing the v5 patchset.
> Here is new patchset addressing all the comments from v5
>
> This patchset adds support for Qualcomm SoundWire Master Controller
> found in most of Qualcomm SoCs and WCD audio codecs.
>
> This driver along with WCD934x codec and WSA881x Class-D Smart Speaker
> Amplifier drivers is tested on on DragonBoard DB845c based of SDM845
> SoC and Lenovo YOGA C630 Laptop based on SDM850.
>
> SoundWire controller on SDM845 is integrated in WCD934x audio codec via
> SlimBus interface.
>
> Currently this driver is very minimal and only supports PDM.
>
> Most of the code in this driver is rework of Qualcomm downstream drivers
> used in Andriod. Credits to Banajit Goswami and Patrick Lai's Team.
Applied, thanks
--
~Vinod
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2020-01-14 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 13:21 [alsa-devel] [PATCH v6 0/2] soundwire: Add support to Qualcomm SoundWire master Srinivas Kandagatla
2020-01-13 13:21 ` [alsa-devel] [PATCH v6 1/2] dt-bindings: soundwire: add bindings for Qcom controller Srinivas Kandagatla
2020-01-13 13:21 ` [alsa-devel] [PATCH v6 2/2] soundwire: qcom: add support for SoundWire controller Srinivas Kandagatla
2020-01-14 6:30 ` Vinod Koul [this message]
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=20200114063006.GE2818@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=robh@kernel.org \
--cc=spapothi@codeaurora.org \
--cc=srinivas.kandagatla@linaro.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).