From: Srinivasa Rao Mandadapu <srivasam@codeaurora.org>
To: Mark Brown <broonie@kernel.org>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
lgirdwood@gmail.com, robh+dt@kernel.org, plai@codeaurora.org,
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
Subject: Re: [PATCH v4 00/10] Add support for audio on SC7280 based targets
Date: Fri, 26 Nov 2021 17:18:51 +0530 [thread overview]
Message-ID: <e69ac087-f78c-65e0-4ea9-dc408a69255c@codeaurora.org> (raw)
In-Reply-To: <YZ+z+XPyecvDJA88@sirena.org.uk>
On 11/25/2021 9:34 PM, Mark Brown wrote:
> On Thu, Nov 18, 2021 at 03:35:46PM +0530, Srinivasa Rao Mandadapu wrote:
>> On 11/17/2021 8:08 PM, Mark Brown wrote:
>>> On Tue, Nov 02, 2021 at 01:00:55PM +0530, Srinivasa Rao Mandadapu wrote:
>>>
>>>> This patch set depends on:
>>>> -- https://patchwork.kernel.org/project/alsa-devel/list/?series=570161
>>>> -- https://patchwork.kernel.org/project/alsa-devel/list/?series=572615
>>>> -- https://patchwork.kernel.org/project/alsa-devel/list/?series=559677
>>> None of those links seem to show any patches (or errors)?
>> Sorry for Inconvenience Rob. I think due to it's status change patches are
>> not being appeared on provided link.
> I'm not Rob...
Sorry.. Brown.😁
>
>> With removing filter able to see patch set. Below are the links with view
>> filter change.
>>
>> --
>> https://patchwork.kernel.org/project/alsa-devel/list/?series=570161&archive=both&state=*
> Please note this bit of the mail:
>
>>> Please include human readable descriptions of things like commits and
>>> issues being discussed in e-mail in your mails, this makes them much
>>> easier for humans to read especially when they have no internet access.
>>> I do frequently catch up on my mail on flights or while otherwise
>>> travelling so this is even more pressing for me than just being about
>>> making things a bit easier to read.
> So it looks like we still depend on at least the sc7280 machine driver?
Yes. Currently it depends on Machine driver.
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc.,
is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.
prev parent reply other threads:[~2021-11-26 11:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 7:30 [PATCH v4 00/10] Add support for audio on SC7280 based targets Srinivasa Rao Mandadapu
2021-11-02 7:30 ` [PATCH v4 01/10] ASoC: qcom: Move lpass_pcm_data structure to lpass header Srinivasa Rao Mandadapu
2021-11-02 7:30 ` [PATCH v4 02/10] ASoC: qcom: lpass: Add dma fields for codec dma lpass interface Srinivasa Rao Mandadapu
2021-11-02 7:30 ` [PATCH v4 03/10] ASoC: qcom: Add register definition for codec rddma and wrdma Srinivasa Rao Mandadapu
2021-11-02 7:30 ` [PATCH v4 04/10] ASoC: qcom: Add lpass CPU driver for codec dma control Srinivasa Rao Mandadapu
2021-11-02 7:31 ` [PATCH v4 05/10] ASoC: qcom: Add helper function to get dma control and lpaif handle Srinivasa Rao Mandadapu
2021-11-02 7:31 ` [PATCH v4 06/10] ASoC: qcom: Add support for codec dma driver Srinivasa Rao Mandadapu
2021-11-02 7:31 ` [PATCH v4 07/10] ASoC: qcom: Add regmap config " Srinivasa Rao Mandadapu
2021-11-02 7:31 ` [PATCH v4 08/10] ASoC: dt-bindings: Add SC7280 sound card bindings Srinivasa Rao Mandadapu
2021-11-02 12:38 ` Rob Herring
2021-11-02 7:31 ` [PATCH v4 09/10] ASoC: qcom: lpass-sc7280: Add platform driver for lpass audio Srinivasa Rao Mandadapu
2021-11-02 7:31 ` [PATCH v4 10/10] ASoC: qcom: SC7280: Update config for building codec dma drivers Srinivasa Rao Mandadapu
2021-11-17 14:38 ` [PATCH v4 00/10] Add support for audio on SC7280 based targets Mark Brown
2021-11-18 10:05 ` Srinivasa Rao Mandadapu
2021-11-25 16:04 ` Mark Brown
2021-11-26 11:48 ` Srinivasa Rao Mandadapu [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=e69ac087-f78c-65e0-4ea9-dc408a69255c@codeaurora.org \
--to=srivasam@codeaurora.org \
--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=plai@codeaurora.org \
--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