From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: devicetree@vger.kernel.org, mark.rutland@arm.com,
laurent.pinchart+renesas@ideasonboard.com,
geert+renesas@glider.be, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, joro@8bytes.org,
linux-sh@vger.kernel.org, iommu@lists.linux-foundation.org,
robh+dt@kernel.org, galak@codeaurora.org,
horms+renesas@verge.net.au
Subject: Re: [PATCH] iommu/ipmmu-vmsa: Include SoC part number in DT binding docs
Date: Mon, 19 Oct 2015 09:44:04 +0300 [thread overview]
Message-ID: <9833652.FLB0aRvpVP@avalon> (raw)
In-Reply-To: <20151019031003.7878.28510.sendpatchset@little-apple>
Hi Magnus,
Thank you for the patch.
On Monday 19 October 2015 12:10:03 Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
>
> Add part numbers for APE6 and current set of R-Car Gen2 SoCs to the
> IPMMU DT binding documentation. The example is also updated to show
> how the generic compatible string may be used as fallback.
I'd use a wording stronger than "may" here, as the generic compatible value is
required. I would also explicitly state that in the bindings documentation.
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> ---
>
> Documentation/devicetree/bindings/iommu/renesas,ipmmu-vmsa.txt | 12
> ++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-)
>
> --- 0001/Documentation/devicetree/bindings/iommu/renesas,ipmmu-vmsa.txt
> +++
> work/Documentation/devicetree/bindings/iommu/renesas,ipmmu-vmsa.txt
2015-10
> -18 15:53:08.850513000 +0900 @@ -7,7 +7,15 @@ connected to the IPMMU through
> a port ca
>
> Required Properties:
>
> - - compatible: Must contain "renesas,ipmmu-vmsa".
> + - compatible: Must contain one of the following:
> +
> + - "renesas,ipmmu-r8a73a4" for the R8A73A4 (R-Mobile APE6) IPMMU.
> + - "renesas,ipmmu-r8a7790" for the R8A7790 (R-Car H2) IPMMU.
> + - "renesas,ipmmu-r8a7791" for the R8A7791 (R-Car M2-W) IPMMU.
> + - "renesas,ipmmu-r8a7793" for the R8A7793 (R-Car M2-N) IPMMU.
> + - "renesas,ipmmu-r8a7794" for the R8A7794 (R-Car E2) IPMMU.
> + - "renesas,ipmmu-vmsa" for generic R-Car Gen2 VMSA-compatible IPMMU.
> +
> - reg: Base address and size of the IPMMU registers.
> - interrupts: Specifiers for the MMU fault interrupts. For instances that
> support secure mode two interrupts must be specified, for non-secure and @@
> -27,7 +35,7 @@ node with the following property:
> Example: R8A7791 IPMMU-MX and VSP1-D0 bus master
>
> ipmmu_mx: mmu@fe951000 {
> - compatible = "renasas,ipmmu-vmsa";
> + compatible = "renasas,ipmmu-r8a7791", "renasas,ipmmu-vmsa";
> reg = <0 0xfe951000 0 0x1000>;
> interrupts = <0 222 IRQ_TYPE_LEVEL_HIGH>,
> <0 221 IRQ_TYPE_LEVEL_HIGH>;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-10-19 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 3:10 [PATCH] iommu/ipmmu-vmsa: Include SoC part number in DT binding docs Magnus Damm
2015-10-19 6:44 ` Laurent Pinchart [this message]
2015-10-20 8:58 ` Magnus Damm
2015-10-20 10:27 ` Laurent Pinchart
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=9833652.FLB0aRvpVP@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=ijc+devicetree@hellion.org.uk \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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).