From: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>
To: Mark Brown <broonie@kernel.org>
Cc: <agross@kernel.org>, <bjorn.andersson@linaro.org>,
<lgirdwood@gmail.com>, <robh+dt@kernel.org>,
<quic_plai@quicinc.com>, <bgoswami@codeaurora.org>,
<perex@perex.cz>, <tiwai@suse.com>,
<srinivas.kandagatla@linaro.org>, <rohitkr@codeaurora.org>,
<linux-arm-msm@vger.kernel.org>, <alsa-devel@alsa-project.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<swboyd@chromium.org>, <judyhsiao@chromium.org>,
Venkata Prasad Potturu <quic_potturu@quicinc.com>
Subject: Re: [PATCH v13 07/10] ASoC: qcom: Add support for codec dma driver
Date: Mon, 14 Feb 2022 20:10:20 +0530 [thread overview]
Message-ID: <669f2d39-8c14-68b9-6d89-a26e0e2e8857@quicinc.com> (raw)
In-Reply-To: <YgppMcVjs0KuE5y8@sirena.org.uk>
On 2/14/2022 8:07 PM, Mark Brown wrote:
Sorry for inconvenience Mark Brown.
> On Mon, Feb 14, 2022 at 03:29:38PM +0530, Srinivasa Rao Mandadapu wrote:
>> Upadate lpass cpu and platform driver to support audio over codec dma
>> in ADSP bypass use case.
> I only have this patch from both v12 and v13, which were sent very close
> together. Please check what's going on here.
As only one patch has update, so sent only one patch. will do resend all
patches if needed.
next prev parent reply other threads:[~2022-02-14 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 9:59 [PATCH v13 00/10] Add support for audio on SC7280 based targets Srinivasa Rao Mandadapu
2022-02-14 9:59 ` [PATCH v13 07/10] ASoC: qcom: Add support for codec dma driver Srinivasa Rao Mandadapu
2022-02-14 14:37 ` Mark Brown
2022-02-14 14:40 ` Srinivasa Rao Mandadapu [this message]
2022-02-14 16:21 ` Mark Brown
2022-02-14 17:34 ` Srinivasa Rao Mandadapu
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=669f2d39-8c14-68b9-6d89-a26e0e2e8857@quicinc.com \
--to=quic_srivasam@quicinc.com \
--cc=agross@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=judyhsiao@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=quic_plai@quicinc.com \
--cc=quic_potturu@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=rohitkr@codeaurora.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=swboyd@chromium.org \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).