All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivasa Rao Mandadapu <srivasam@codeaurora.org>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Boyd <swboyd@chromium.org>,
	agross@kernel.org, alsa-devel@alsa-project.org,
	bgoswami@codeaurora.org, bjorn.andersson@linaro.org,
	devicetree@vger.kernel.org, judyhsiao@chromium.org,
	lgirdwood@gmail.com, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, perex@perex.cz,
	plai@codeaurora.org, robh+dt@kernel.org, rohitkr@codeaurora.org,
	srinivas.kandagatla@linaro.org, tiwai@suse.com
Subject: Re: [PATCH] ASoC: dt-bindings: lpass: add binding headers for digital codecs
Date: Wed, 8 Sep 2021 18:36:40 +0530	[thread overview]
Message-ID: <0f6aa59a-5350-684d-c90c-b250e6d2977a@codeaurora.org> (raw)
In-Reply-To: <20210908102300.GA4112@sirena.org.uk>

Thanks for Your Time Mark Brown!!!

On 9/8/2021 3:53 PM, Mark Brown wrote:
> On Wed, Sep 08, 2021 at 10:08:33AM +0530, Srinivasa Rao Mandadapu wrote:
>> On 9/8/2021 1:54 AM, Stephen Boyd wrote:
>>> Quoting Srinivasa Rao Mandadapu (2021-09-06 06:27:34)
>>>> +#define LPASS_CDC_DMA_VA0 8
>>>> +#define LPASS_MAX_PORTS 9
>>> Do we need LPASS_MAX_PORTS in the binding?
>> Yes.  based on this creating array of streams in machine driver. So to make
>> upper limit introduced this macro.
> That's saying it's useful to have it in the code, do we need it in the
> binding itself though?
Okay.  Got it. will remove it and share new patch.

-- 
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc.,
is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.


WARNING: multiple messages have this Message-ID (diff)
From: Srinivasa Rao Mandadapu <srivasam@codeaurora.org>
To: Mark Brown <broonie@kernel.org>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
	bgoswami@codeaurora.org, linux-arm-msm@vger.kernel.org,
	plai@codeaurora.org, tiwai@suse.com, lgirdwood@gmail.com,
	robh+dt@kernel.org, bjorn.andersson@linaro.org,
	agross@kernel.org, rohitkr@codeaurora.org,
	Stephen Boyd <swboyd@chromium.org>,
	judyhsiao@chromium.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: dt-bindings: lpass: add binding headers for digital codecs
Date: Wed, 8 Sep 2021 18:36:40 +0530	[thread overview]
Message-ID: <0f6aa59a-5350-684d-c90c-b250e6d2977a@codeaurora.org> (raw)
In-Reply-To: <20210908102300.GA4112@sirena.org.uk>

Thanks for Your Time Mark Brown!!!

On 9/8/2021 3:53 PM, Mark Brown wrote:
> On Wed, Sep 08, 2021 at 10:08:33AM +0530, Srinivasa Rao Mandadapu wrote:
>> On 9/8/2021 1:54 AM, Stephen Boyd wrote:
>>> Quoting Srinivasa Rao Mandadapu (2021-09-06 06:27:34)
>>>> +#define LPASS_CDC_DMA_VA0 8
>>>> +#define LPASS_MAX_PORTS 9
>>> Do we need LPASS_MAX_PORTS in the binding?
>> Yes.  based on this creating array of streams in machine driver. So to make
>> upper limit introduced this macro.
> That's saying it's useful to have it in the code, do we need it in the
> binding itself though?
Okay.  Got it. will remove it and share new patch.

-- 
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc.,
is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.


  reply	other threads:[~2021-09-08 13:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06 13:27 [PATCH] ASoC: dt-bindings: lpass: add binding headers for digital codecs Srinivasa Rao Mandadapu
2021-09-07 20:24 ` Stephen Boyd
2021-09-07 20:24   ` Stephen Boyd
2021-09-08  4:38   ` Srinivasa Rao Mandadapu
2021-09-08 10:23     ` Mark Brown
2021-09-08 10:23       ` Mark Brown
2021-09-08 13:06       ` Srinivasa Rao Mandadapu [this message]
2021-09-08 13:06         ` Srinivasa Rao Mandadapu
2021-09-08  9:41 ` Srinivas Kandagatla
2021-09-08 13:05   ` Srinivasa Rao Mandadapu
2021-09-13 10:53 ` Mark Brown

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=0f6aa59a-5350-684d-c90c-b250e6d2977a@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.