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: "open list:DMA GENERIC OFFLOAD ENGINE SUBSYSTEM" 
	<dmaengine@vger.kernel.org>,
	devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: dma: arm,pl330: Add missing 'iommus' property
Date: Thu, 28 Jul 2022 15:50:27 -0600	[thread overview]
Message-ID: <CAL_JsqKGmL7BTibEJM0NWRmazOJBsNDLAWFtvth=oBOQQmn_VQ@mail.gmail.com> (raw)
In-Reply-To: <20220728185512.1270964-1-robh@kernel.org>

On Thu, Jul 28, 2022 at 12:55 PM Rob Herring <robh@kernel.org> wrote:
>
> The pl330 can be behind an IOMMU which is the case for Arm Juno board.
> Add the 'iommus' property allowing for 1 IOMMU per channel.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
>  Documentation/devicetree/bindings/dma/arm,pl330.yaml | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/dma/arm,pl330.yaml b/Documentation/devicetree/bindings/dma/arm,pl330.yaml
> index 2bec69b308f8..b9c4bee178ae 100644
> --- a/Documentation/devicetree/bindings/dma/arm,pl330.yaml
> +++ b/Documentation/devicetree/bindings/dma/arm,pl330.yaml
> @@ -55,6 +55,11 @@ properties:
>
>    dma-coherent: true
>
> +  iommus:
> +    minItems: 1
> +    maxItems: 8

Off by 1. Juno has 9 entries. I think it's 8 entries for write the
read side has 1 entry. The TRM isn't too clear.

Rob

> +    description: Up to 1 IOMMU per DMA channel
> +
>    power-domains:
>      maxItems: 1
>
> --
> 2.34.1
>

      reply	other threads:[~2022-07-28 21:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 18:55 [PATCH] dt-bindings: dma: arm,pl330: Add missing 'iommus' property Rob Herring
2022-07-28 21:50 ` Rob Herring [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='CAL_JsqKGmL7BTibEJM0NWRmazOJBsNDLAWFtvth=oBOQQmn_VQ@mail.gmail.com' \
    --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).