devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Vinod Koul <vkoul@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: dma: arm,pl330: Add missing 'iommus' property
Date: Fri, 2 Sep 2022 11:06:56 -0500	[thread overview]
Message-ID: <20220902160656.GA4168277-robh@kernel.org> (raw)
In-Reply-To: <20220801210237.1501488-1-robh@kernel.org>

On Mon, Aug 01, 2022 at 03:02:37PM -0600, Rob Herring wrote:
> The pl330 can be behind an IOMMU which is the case for Arm Juno board.
> Add the 'iommus' property allowing for 1 IOMMU entry per channel for
> writes and 1 IOMMU entry for reads.
> 
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> v2:
>  - Include IOMMU entry for read channel
> ---
>  Documentation/devicetree/bindings/dma/arm,pl330.yaml | 6 ++++++
>  1 file changed, 6 insertions(+)

Ping!

> 
> diff --git a/Documentation/devicetree/bindings/dma/arm,pl330.yaml b/Documentation/devicetree/bindings/dma/arm,pl330.yaml
> index 2bec69b308f8..4a3dd6f5309b 100644
> --- a/Documentation/devicetree/bindings/dma/arm,pl330.yaml
> +++ b/Documentation/devicetree/bindings/dma/arm,pl330.yaml
> @@ -55,6 +55,12 @@ properties:
>  
>    dma-coherent: true
>  
> +  iommus:
> +    minItems: 1
> +    maxItems: 9
> +    description: Up to 1 IOMMU entry per DMA channel for writes and 1
> +      IOMMU entry for reads.
> +
>    power-domains:
>      maxItems: 1
>  
> -- 
> 2.34.1
> 
> 

  reply	other threads:[~2022-09-02 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 21:02 [PATCH v2] dt-bindings: dma: arm,pl330: Add missing 'iommus' property Rob Herring
2022-09-02 16:06 ` Rob Herring [this message]
2022-09-04 16:11 ` Vinod Koul

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=20220902160656.GA4168277-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vkoul@kernel.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).