All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Akhil R <akhilrajeev@nvidia.com>
Cc: ldewangan@nvidia.com, jonathanh@nvidia.com,
	thierry.reding@gmail.com, p.zabel@pengutronix.de,
	dmaengine@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v2 1/3] dt-bindings: dmaengine: Add dma-channel-mask to Tegra GPCDMA
Date: Wed, 19 Oct 2022 19:03:00 +0530	[thread overview]
Message-ID: <Y0/8jF++NeUGtPGM@matsya> (raw)
In-Reply-To: <20221018162812.69673-2-akhilrajeev@nvidia.com>

On 18-10-22, 21:58, Akhil R wrote:
> Add dma-channel-mask property in Tegra GPCDMA document.
> 
> The property would help to specify the channels to be used in
> kernel and reserve few for the firmware. This was previously
> achieved by limiting the channel number to 31 in the driver.
> Now since we can list all 32 channels, update the interrupts
> property as well to list all 32 interrupts.

Pls cc dt folks and ML on DT patches!

> 
> Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
> Acked-by: Thierry Reding <treding@nvidia.com>
> ---
>  .../devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml   | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml b/Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml
> index c8894476b6ab..851bd50ee67f 100644
> --- a/Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml
> +++ b/Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml
> @@ -39,7 +39,7 @@ properties:
>        Should contain all of the per-channel DMA interrupts in
>        ascending order with respect to the DMA channel index.
>      minItems: 1
> -    maxItems: 31
> +    maxItems: 32
>  
>    resets:
>      maxItems: 1
> @@ -52,6 +52,9 @@ properties:
>  
>    dma-coherent: true
>  
> +  dma-channel-mask:
> +    maxItems: 1
> +
>  required:
>    - compatible
>    - reg
> @@ -60,6 +63,7 @@ required:
>    - reset-names
>    - "#dma-cells"
>    - iommus
> +  - dma-channel-mask
>  
>  additionalProperties: false
>  
> @@ -108,5 +112,6 @@ examples:
>          #dma-cells = <1>;
>          iommus = <&smmu TEGRA186_SID_GPCDMA_0>;
>          dma-coherent;
> +        dma-channel-mask = <0xfffffffe>;
>      };
>  ...
> -- 
> 2.17.1

-- 
~Vinod

  reply	other threads:[~2022-10-19 13:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 16:28 [PATCH RESEND v2 0/3] Tegra GCPDMA: Add dma-channel-mask support Akhil R
2022-10-18 16:28 ` [PATCH RESEND v2 1/3] dt-bindings: dmaengine: Add dma-channel-mask to Tegra GPCDMA Akhil R
2022-10-19 13:33   ` Vinod Koul [this message]
2022-10-20  8:35     ` Akhil R
2022-10-18 16:28 ` [PATCH RESEND v2 2/3] arm64: tegra: Add dma-channel-mask in GPCDMA node Akhil R
2022-10-18 16:28 ` [PATCH RESEND v2 3/3] dmaengine: tegra: Add support for dma-channel-mask Akhil R
  -- strict thread matches above, loose matches on Subject: below --
2022-10-20  8:33 [PATCH RESEND v2 0/3] Tegra GCPDMA: Add dma-channel-mask support Akhil R
2022-10-20  8:33 ` [PATCH RESEND v2 1/3] dt-bindings: dmaengine: Add dma-channel-mask to Tegra GPCDMA Akhil R
2022-10-27 13:38   ` Krzysztof Kozlowski

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=Y0/8jF++NeUGtPGM@matsya \
    --to=vkoul@kernel.org \
    --cc=akhilrajeev@nvidia.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=thierry.reding@gmail.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.