From: Andreas Herrmann <andreas.herrmann-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
To: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Cc: "iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH v2 1/3] documentation: iommu: add description of ARM System MMU binding
Date: Tue, 25 Jun 2013 23:24:46 +0200 [thread overview]
Message-ID: <20130625212446.GO2743@alberich> (raw)
In-Reply-To: <1372095086-15681-2-git-send-email-will.deacon-5wv7dgnIgG8@public.gmane.org>
On Mon, Jun 24, 2013 at 01:31:24PM -0400, Will Deacon wrote:
> This patch adds a description of the device tree binding for the ARM
> System MMU architecture.
>
> Cc: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Cc: Andreas Herrmann <andreas.herrmann-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
> Cc: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
> Acked-by: Grant Likely <grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> Signed-off-by: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Acked-by: Andreas Herrmann <andreas.herrmann-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
> ---
> .../devicetree/bindings/iommu/arm,smmu.txt | 70 ++++++++++++++++++++++
> 1 file changed, 70 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iommu/arm,smmu.txt
>
> diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu.txt b/Documentation/devicetree/bindings/iommu/arm,smmu.txt
> new file mode 100644
> index 0000000..e34c6cd
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iommu/arm,smmu.txt
> @@ -0,0 +1,70 @@
> +* ARM System MMU Architecture Implementation
> +
> +ARM SoCs may contain an implementation of the ARM System Memory
> +Management Unit Architecture, which can be used to provide 1 or 2 stages
> +of address translation to bus masters external to the CPU.
> +
> +The SMMU may also raise interrupts in response to various fault
> +conditions.
> +
> +** System MMU required properties:
> +
> +- compatible : Should be one of:
> +
> + "arm,smmu-v1"
> + "arm,smmu-v2"
> + "arm,mmu-400"
> + "arm,mmu-500"
> +
> + depending on the particular implementation and/or the
> + version of the architecture implemented.
> +
> +- reg : Base address and size of the SMMU.
> +
> +- #global-interrupts : The number of global interrupts exposed by the
> + device.
> +
> +- interrupts : Interrupt list, with the first #global-irqs entries
> + corresponding to the global interrupts and any
> + following entries corresponding to context interrupts,
> + specified in order of their indexing by the SMMU.
> +
> + For SMMUv2 implementations, there must be exactly one
> + interrupt per context bank. In the case of a single,
> + combined interrupt, it must be listed multiple times.
> +
> +- mmu-masters : A list of phandles to device nodes representing bus
> + masters for which the SMMU can provide a translation
> + and their corresponding StreamIDs (see example below).
> + Each device node linked from this list must have a
> + "#stream-id-cells" property, indicating the number of
> + StreamIDs associated with it.
> +
> +** System MMU optional properties:
> +
> +- smmu-parent : When multiple SMMUs are chained together, this
> + property can be used to provide a phandle to the
> + parent SMMU (that is the next SMMU on the path going
> + from the mmu-masters towards memory) node for this
> + SMMU.
> +
> +Example:
> +
> + smmu {
> + compatible = "arm,smmu-v1";
> + reg = <0xba5e0000 0x10000>;
> + #global-interrupts = <2>;
> + interrupts = <0 32 4>,
> + <0 33 4>,
> + <0 34 4>, /* This is the first context interrupt */
> + <0 35 4>,
> + <0 36 4>,
> + <0 37 4>;
> +
> + /*
> + * Two DMA controllers, the first with two StreamIDs (0xd01d
> + * and 0xd01e) and the second with only one (0xd11c).
> + */
> + mmu-masters = <&dma0 0xd01d 0xd01e>,
> + <&dma1 0xd11c>;
> + };
> --
> 1.8.2.2
>
WARNING: multiple messages have this Message-ID (diff)
From: andreas.herrmann@calxeda.com (Andreas Herrmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] documentation: iommu: add description of ARM System MMU binding
Date: Tue, 25 Jun 2013 23:24:46 +0200 [thread overview]
Message-ID: <20130625212446.GO2743@alberich> (raw)
In-Reply-To: <1372095086-15681-2-git-send-email-will.deacon@arm.com>
On Mon, Jun 24, 2013 at 01:31:24PM -0400, Will Deacon wrote:
> This patch adds a description of the device tree binding for the ARM
> System MMU architecture.
>
> Cc: Rob Herring <robherring2@gmail.com>
> Cc: Andreas Herrmann <andreas.herrmann@calxeda.com>
> Cc: Joerg Roedel <joro@8bytes.org>
> Acked-by: Grant Likely <grant.likely@linaro.org>
> Signed-off-by: Will Deacon <will.deacon@arm.com>
Acked-by: Andreas Herrmann <andreas.herrmann@calxeda.com>
> ---
> .../devicetree/bindings/iommu/arm,smmu.txt | 70 ++++++++++++++++++++++
> 1 file changed, 70 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iommu/arm,smmu.txt
>
> diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu.txt b/Documentation/devicetree/bindings/iommu/arm,smmu.txt
> new file mode 100644
> index 0000000..e34c6cd
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iommu/arm,smmu.txt
> @@ -0,0 +1,70 @@
> +* ARM System MMU Architecture Implementation
> +
> +ARM SoCs may contain an implementation of the ARM System Memory
> +Management Unit Architecture, which can be used to provide 1 or 2 stages
> +of address translation to bus masters external to the CPU.
> +
> +The SMMU may also raise interrupts in response to various fault
> +conditions.
> +
> +** System MMU required properties:
> +
> +- compatible : Should be one of:
> +
> + "arm,smmu-v1"
> + "arm,smmu-v2"
> + "arm,mmu-400"
> + "arm,mmu-500"
> +
> + depending on the particular implementation and/or the
> + version of the architecture implemented.
> +
> +- reg : Base address and size of the SMMU.
> +
> +- #global-interrupts : The number of global interrupts exposed by the
> + device.
> +
> +- interrupts : Interrupt list, with the first #global-irqs entries
> + corresponding to the global interrupts and any
> + following entries corresponding to context interrupts,
> + specified in order of their indexing by the SMMU.
> +
> + For SMMUv2 implementations, there must be exactly one
> + interrupt per context bank. In the case of a single,
> + combined interrupt, it must be listed multiple times.
> +
> +- mmu-masters : A list of phandles to device nodes representing bus
> + masters for which the SMMU can provide a translation
> + and their corresponding StreamIDs (see example below).
> + Each device node linked from this list must have a
> + "#stream-id-cells" property, indicating the number of
> + StreamIDs associated with it.
> +
> +** System MMU optional properties:
> +
> +- smmu-parent : When multiple SMMUs are chained together, this
> + property can be used to provide a phandle to the
> + parent SMMU (that is the next SMMU on the path going
> + from the mmu-masters towards memory) node for this
> + SMMU.
> +
> +Example:
> +
> + smmu {
> + compatible = "arm,smmu-v1";
> + reg = <0xba5e0000 0x10000>;
> + #global-interrupts = <2>;
> + interrupts = <0 32 4>,
> + <0 33 4>,
> + <0 34 4>, /* This is the first context interrupt */
> + <0 35 4>,
> + <0 36 4>,
> + <0 37 4>;
> +
> + /*
> + * Two DMA controllers, the first with two StreamIDs (0xd01d
> + * and 0xd01e) and the second with only one (0xd11c).
> + */
> + mmu-masters = <&dma0 0xd01d 0xd01e>,
> + <&dma1 0xd11c>;
> + };
> --
> 1.8.2.2
>
next prev parent reply other threads:[~2013-06-25 21:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 17:31 [PATCH v2 0/3] Add support for ARM SMMU architectures 1 and 2 Will Deacon
2013-06-24 17:31 ` Will Deacon
[not found] ` <1372095086-15681-1-git-send-email-will.deacon-5wv7dgnIgG8@public.gmane.org>
2013-06-24 17:31 ` [PATCH v2 1/3] documentation: iommu: add description of ARM System MMU binding Will Deacon
2013-06-24 17:31 ` Will Deacon
[not found] ` <1372095086-15681-2-git-send-email-will.deacon-5wv7dgnIgG8@public.gmane.org>
2013-06-25 21:24 ` Andreas Herrmann [this message]
2013-06-25 21:24 ` Andreas Herrmann
2013-06-24 17:31 ` [PATCH v2 2/3] iommu: add support for ARM Ltd. System MMU architecture Will Deacon
2013-06-24 17:31 ` Will Deacon
[not found] ` <1372095086-15681-3-git-send-email-will.deacon-5wv7dgnIgG8@public.gmane.org>
2013-06-25 21:25 ` Andreas Herrmann
2013-06-25 21:25 ` Andreas Herrmann
2013-06-26 9:00 ` Will Deacon
2013-06-26 9:00 ` Will Deacon
2013-07-08 16:34 ` Olav Haugan
2013-07-08 16:34 ` Olav Haugan
[not found] ` <51DAEA0F.2030808-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2013-07-09 7:48 ` Will Deacon
2013-07-09 7:48 ` Will Deacon
2013-06-24 17:31 ` [PATCH v2 3/3] MAINTAINERS: add entry for ARM system MMU driver Will Deacon
2013-06-24 17:31 ` Will Deacon
2013-06-26 9:48 ` [PATCH v2 0/3] Add support for ARM SMMU architectures 1 and 2 Joerg Roedel
2013-06-26 9:48 ` Joerg Roedel
[not found] ` <20130626094805.GS11309-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2013-06-26 11:32 ` Will Deacon
2013-06-26 11:32 ` Will Deacon
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=20130625212446.GO2743@alberich \
--to=andreas.herrmann-bsgfqqb8/dxbdgjk7y7tuq@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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 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.