diff for duplicates of <HE1PR0401MB24257DC948C69C7A9080ED66E6DF0@HE1PR0401MB2425.eurprd04.prod.outlook.com>
diff --git a/a/1.txt b/N1/1.txt
index 4805389..42c1097 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,16 +1,16 @@
Hi Rob,
> -----Original Message-----
-> From: Rob Herring [mailto:robh@kernel.org]
+> From: Rob Herring [mailto:robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org]
> Sent: Thursday, March 08, 2018 4:10
-> To: Nipun Gupta <nipun.gupta@nxp.com>
-> Cc: will.deacon@arm.com; robin.murphy@arm.com; mark.rutland@arm.com;
-> catalin.marinas@arm.com; devicetree@vger.kernel.org; stuyoder@gmail.com;
-> Bharat Bhushan <bharat.bhushan@nxp.com>; gregkh@linuxfoundation.org;
-> joro@8bytes.org; linuxppc-dev@lists.ozlabs.org; linux-kernel@vger.kernel.org;
-> Leo Li <leoyang.li@nxp.com>; iommu@lists.linux-foundation.org; Laurentiu
-> Tudor <laurentiu.tudor@nxp.com>; shawnguo@kernel.org; hch@lst.de; linux-
-> arm-kernel@lists.infradead.org; m.szyprowski@samsung.com
+> To: Nipun Gupta <nipun.gupta-3arQi8VN3Tc@public.gmane.org>
+> Cc: will.deacon-5wv7dgnIgG8@public.gmane.org; robin.murphy-5wv7dgnIgG8@public.gmane.org; mark.rutland-5wv7dgnIgG8@public.gmane.org;
+> catalin.marinas-5wv7dgnIgG8@public.gmane.org; devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; stuyoder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org;
+> Bharat Bhushan <bharat.bhushan-3arQi8VN3Tc@public.gmane.org>; gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org;
+> joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org; linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org; linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org;
+> Leo Li <leoyang.li-3arQi8VN3Tc@public.gmane.org>; iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org; Laurentiu
+> Tudor <laurentiu.tudor-3arQi8VN3Tc@public.gmane.org>; shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org; hch-jcswGhMUV9g@public.gmane.org; linux-
+> arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org; m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org
> Subject: Re: [PATCH 1/6] Docs: dt: add fsl-mc iommu-parent device-tree binding
>
> On Mon, Mar 05, 2018 at 07:59:21PM +0530, Nipun Gupta wrote:
@@ -18,7 +18,7 @@ Hi Rob,
> > between fsl-mc devices and IOMMUs. This patch adds a binding for
> > mapping fsl-mc devices to IOMMUs, using a new iommu-parent property.
> >
-> > Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
+> > Signed-off-by: Nipun Gupta <nipun.gupta-3arQi8VN3Tc@public.gmane.org>
> > ---
> > .../devicetree/bindings/misc/fsl,qoriq-mc.txt | 31
> ++++++++++++++++++++++
@@ -123,7 +123,7 @@ Nipun
> >
> > _______________________________________________
> > linux-arm-kernel mailing list
-> > linux-arm-kernel@lists.infradead.org
+> > linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
> >
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.infr
> adead.org%2Fmailman%2Flistinfo%2Flinux-arm-
diff --git a/a/content_digest b/N1/content_digest
index 89ab40d..d785e9d 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -8,7 +8,7 @@
"ref\00020180307224019.oowh74pkbi5izuft\@rob-hp-laptop\0"
]
[
- "From\0Nipun Gupta <nipun.gupta\@nxp.com>\0"
+ "From\0Nipun Gupta <nipun.gupta-3arQi8VN3Tc\@public.gmane.org>\0"
]
[
"Subject\0RE: [PATCH 1/6] Docs: dt: add fsl-mc iommu-parent device-tree binding\0"
@@ -17,27 +17,22 @@
"Date\0Thu, 8 Mar 2018 12:32:28 +0000\0"
]
[
- "To\0Rob Herring <robh\@kernel.org>\0"
+ "To\0Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A\@public.gmane.org>\0"
]
[
- "Cc\0will.deacon\@arm.com <will.deacon\@arm.com>",
- " robin.murphy\@arm.com <robin.murphy\@arm.com>",
- " mark.rutland\@arm.com <mark.rutland\@arm.com>",
- " catalin.marinas\@arm.com <catalin.marinas\@arm.com>",
- " devicetree\@vger.kernel.org <devicetree\@vger.kernel.org>",
- " stuyoder\@gmail.com <stuyoder\@gmail.com>",
- " Bharat Bhushan <bharat.bhushan\@nxp.com>",
- " gregkh\@linuxfoundation.org <gregkh\@linuxfoundation.org>",
- " joro\@8bytes.org <joro\@8bytes.org>",
- " linuxppc-dev\@lists.ozlabs.org <linuxppc-dev\@lists.ozlabs.org>",
- " linux-kernel\@vger.kernel.org <linux-kernel\@vger.kernel.org>",
- " Leo Li <leoyang.li\@nxp.com>",
- " iommu\@lists.linux-foundation.org <iommu\@lists.linux-foundation.org>",
- " Laurentiu Tudor <laurentiu.tudor\@nxp.com>",
- " shawnguo\@kernel.org <shawnguo\@kernel.org>",
- " hch\@lst.de <hch\@lst.de>",
- " linux-arm-kernel\@lists.infradead.org <linux-arm-kernel\@lists.infradead.org>",
- " m.szyprowski\@samsung.com <m.szyprowski\@samsung.com>\0"
+ "Cc\0mark.rutland-5wv7dgnIgG8\@public.gmane.org <mark.rutland-5wv7dgnIgG8\@public.gmane.org>",
+ " devicetree-u79uwXL29TY76Z2rM5mHXA\@public.gmane.org <devicetree-u79uwXL29TY76Z2rM5mHXA\@public.gmane.org>",
+ " stuyoder-Re5JQEeQqe8AvxtiuMwx3w\@public.gmane.org <stuyoder-Re5JQEeQqe8AvxtiuMwx3w\@public.gmane.org>",
+ " catalin.marinas-5wv7dgnIgG8\@public.gmane.org <catalin.marinas-5wv7dgnIgG8\@public.gmane.org>",
+ " will.deacon-5wv7dgnIgG8\@public.gmane.org <will.deacon-5wv7dgnIgG8\@public.gmane.org>",
+ " linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ\@public.gmane.org <linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ\@public.gmane.org>",
+ " linux-kernel-u79uwXL29TY76Z2rM5mHXA\@public.gmane.org <linux-kernel-u79uwXL29TY76Z2rM5mHXA\@public.gmane.org>",
+ " iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA\@public.gmane.org <iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA\@public.gmane.org>",
+ " gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r\@public.gmane.org <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r\@public.gmane.org>",
+ " shawnguo-DgEjT+Ai2ygdnm+yROfE0A\@public.gmane.org <shawnguo-DgEjT+Ai2ygdnm+yROfE0A\@public.gmane.org>",
+ " Leo Li <leoyang.li-3arQi8VN3Tc\@public.gmane.org>",
+ " hch-jcswGhMUV9g\@public.gmane.org <hch-jcswGhMUV9g\@public.gmane.org>",
+ " linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r\@public.gmane.org <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r\@public.gmane.org>\0"
]
[
"\0000:1\0"
@@ -49,16 +44,16 @@
"Hi Rob,\n",
"\n",
"> -----Original Message-----\n",
- "> From: Rob Herring [mailto:robh\@kernel.org]\n",
+ "> From: Rob Herring [mailto:robh-DgEjT+Ai2ygdnm+yROfE0A\@public.gmane.org]\n",
"> Sent: Thursday, March 08, 2018 4:10\n",
- "> To: Nipun Gupta <nipun.gupta\@nxp.com>\n",
- "> Cc: will.deacon\@arm.com; robin.murphy\@arm.com; mark.rutland\@arm.com;\n",
- "> catalin.marinas\@arm.com; devicetree\@vger.kernel.org; stuyoder\@gmail.com;\n",
- "> Bharat Bhushan <bharat.bhushan\@nxp.com>; gregkh\@linuxfoundation.org;\n",
- "> joro\@8bytes.org; linuxppc-dev\@lists.ozlabs.org; linux-kernel\@vger.kernel.org;\n",
- "> Leo Li <leoyang.li\@nxp.com>; iommu\@lists.linux-foundation.org; Laurentiu\n",
- "> Tudor <laurentiu.tudor\@nxp.com>; shawnguo\@kernel.org; hch\@lst.de; linux-\n",
- "> arm-kernel\@lists.infradead.org; m.szyprowski\@samsung.com\n",
+ "> To: Nipun Gupta <nipun.gupta-3arQi8VN3Tc\@public.gmane.org>\n",
+ "> Cc: will.deacon-5wv7dgnIgG8\@public.gmane.org; robin.murphy-5wv7dgnIgG8\@public.gmane.org; mark.rutland-5wv7dgnIgG8\@public.gmane.org;\n",
+ "> catalin.marinas-5wv7dgnIgG8\@public.gmane.org; devicetree-u79uwXL29TY76Z2rM5mHXA\@public.gmane.org; stuyoder-Re5JQEeQqe8AvxtiuMwx3w\@public.gmane.org;\n",
+ "> Bharat Bhushan <bharat.bhushan-3arQi8VN3Tc\@public.gmane.org>; gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r\@public.gmane.org;\n",
+ "> joro-zLv9SwRftAIdnm+yROfE0A\@public.gmane.org; linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ\@public.gmane.org; linux-kernel-u79uwXL29TY76Z2rM5mHXA\@public.gmane.org;\n",
+ "> Leo Li <leoyang.li-3arQi8VN3Tc\@public.gmane.org>; iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA\@public.gmane.org; Laurentiu\n",
+ "> Tudor <laurentiu.tudor-3arQi8VN3Tc\@public.gmane.org>; shawnguo-DgEjT+Ai2ygdnm+yROfE0A\@public.gmane.org; hch-jcswGhMUV9g\@public.gmane.org; linux-\n",
+ "> arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r\@public.gmane.org; m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ\@public.gmane.org\n",
"> Subject: Re: [PATCH 1/6] Docs: dt: add fsl-mc iommu-parent device-tree binding\n",
"> \n",
"> On Mon, Mar 05, 2018 at 07:59:21PM +0530, Nipun Gupta wrote:\n",
@@ -66,7 +61,7 @@
"> > between fsl-mc devices and IOMMUs. This patch adds a binding for\n",
"> > mapping fsl-mc devices to IOMMUs, using a new iommu-parent property.\n",
"> >\n",
- "> > Signed-off-by: Nipun Gupta <nipun.gupta\@nxp.com>\n",
+ "> > Signed-off-by: Nipun Gupta <nipun.gupta-3arQi8VN3Tc\@public.gmane.org>\n",
"> > ---\n",
"> > .../devicetree/bindings/misc/fsl,qoriq-mc.txt | 31\n",
"> ++++++++++++++++++++++\n",
@@ -171,7 +166,7 @@
"> >\n",
"> > _______________________________________________\n",
"> > linux-arm-kernel mailing list\n",
- "> > linux-arm-kernel\@lists.infradead.org\n",
+ "> > linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r\@public.gmane.org\n",
"> >\n",
"> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.infr\n",
"> adead.org%2Fmailman%2Flistinfo%2Flinux-arm-\n",
@@ -181,4 +176,4 @@
"> %3D&reserved=0"
]
-9b2c43b4f6af762b8838f7a85a0bc151fe6885b5326bb66d1b404ef27fba1a42
+863a10a689553bd3c74e1640d4fa8384761d3db77379498684748100d5f4a9cf
diff --git a/a/1.txt b/N2/1.txt
index 4805389..aa21362 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -7,12 +7,14 @@ Hi Rob,
> Cc: will.deacon@arm.com; robin.murphy@arm.com; mark.rutland@arm.com;
> catalin.marinas@arm.com; devicetree@vger.kernel.org; stuyoder@gmail.com;
> Bharat Bhushan <bharat.bhushan@nxp.com>; gregkh@linuxfoundation.org;
-> joro@8bytes.org; linuxppc-dev@lists.ozlabs.org; linux-kernel@vger.kernel.org;
+> joro@8bytes.org; linuxppc-dev@lists.ozlabs.org; linux-kernel@vger.kernel.=
+org;
> Leo Li <leoyang.li@nxp.com>; iommu@lists.linux-foundation.org; Laurentiu
> Tudor <laurentiu.tudor@nxp.com>; shawnguo@kernel.org; hch@lst.de; linux-
> arm-kernel@lists.infradead.org; m.szyprowski@samsung.com
-> Subject: Re: [PATCH 1/6] Docs: dt: add fsl-mc iommu-parent device-tree binding
->
+> Subject: Re: [PATCH 1/6] Docs: dt: add fsl-mc iommu-parent device-tree bi=
+nding
+>=20
> On Mon, Mar 05, 2018 at 07:59:21PM +0530, Nipun Gupta wrote:
> > The existing IOMMU bindings cannot be used to specify the relationship
> > between fsl-mc devices and IOMMUs. This patch adds a binding for
@@ -37,27 +39,33 @@ Hi Rob,
> > +For an overview of the DPAA2 architecture and fsl-mc bus see:
> > +drivers/staging/fsl-mc/README.txt
> > +
-> > +As described in the above overview, all DPAA2 objects in a DPRC share the
+> > +As described in the above overview, all DPAA2 objects in a DPRC share =
+the
> > +same hardware "isolation context" and a 10-bit value called an ICID
> > +(isolation context id) is expressed by the hardware to identify
> > +the requester.
> > +
-> > +The generic 'iommus' property is cannot be used to describe the relationship
-> > +between fsl-mc and IOMMUs, so an iommu-parent property is used to define
+> > +The generic 'iommus' property is cannot be used to describe the relati=
+onship
+> > +between fsl-mc and IOMMUs, so an iommu-parent property is used to defi=
+ne
> > +the same.
->
+>=20
> Why not? It is just a link between 2 nodes.
-We have #iommu-cells as '1' i.e. iommu will have one stream ID configured for a device.
-Once USB and other devices start to use IOMMU we will also need this iommu-cells.
+We have #iommu-cells as '1' i.e. iommu will have one stream ID configured f=
+or a device.
+Once USB and other devices start to use IOMMU we will also need this iommu-=
+cells.
-When #iommu-cells is defined as '1' and we have 'iommus=<&smmu>' compilation
+When #iommu-cells is defined as '1' and we have 'iommus=3D<&smmu>' compilat=
+ion
reports warning about the mismatch.
In fsl-mc bus case we do not have any stream id associated with the bus.
As suggested by Robin, we can simply use the iommu-map property.
->
+>=20
> > +
> > +For generic IOMMU bindings, see
> > +Documentation/devicetree/bindings/iommu/iommu.txt.
@@ -70,26 +78,29 @@ As suggested by Robin, we can simply use the iommu-map property.
> > - compatible
> > @@ -88,14 +106,27 @@ Sub-nodes:
> > Value type: <phandle>
-> > Definition: Specifies the phandle to the PHY device node associated
+> > Definition: Specifies the phandle to the PHY device node=
+ associated
> > with the this dpmac.
> > +Optional properties:
> > +
> > +- iommu-parent: Maps the devices on fsl-mc bus to an IOMMU.
> > + The property specifies the IOMMU behind which the devices on
> > + fsl-mc bus are residing.
->
+>=20
> If you want a generic property, this should be documented in the common
> binding.
We can use the iommu-map property which is already documented.
->
+>=20
> Couldn't you have more than 1 IOMMU upstream of a MC?
-There is no such device currently with which fsl-mc bus uses more than one iommu.
+There is no such device currently with which fsl-mc bus uses more than one =
+iommu.
Infact, our current systems have only single IOMMU :).
-Even in future if such devices are there then we can use iommu-map to specify
+Even in future if such devices are there then we can use iommu-map to speci=
+fy
more than one iommu with separate requester ID's (RID's).
Thank you for review...
@@ -97,25 +108,27 @@ Thank you for review...
Regards,
Nipun
->
+>=20
> >
> > Example:
> >
> > + smmu: iommu@5000000 {
-> > + compatible = "arm,mmu-500";
-> > + #iommu-cells = <1>;
-> > + stream-match-mask = <0x7C00>;
+> > + compatible =3D "arm,mmu-500";
+> > + #iommu-cells =3D <1>;
+> > + stream-match-mask =3D <0x7C00>;
> > + ...
> > + };
> > +
> > fsl_mc: fsl-mc@80c000000 {
-> > compatible = "fsl,qoriq-mc";
-> > reg = <0x00000008 0x0c000000 0 0x40>, /* MC portal base */
-> > <0x00000000 0x08340000 0 0x40000>; /* MC control reg */
-> > msi-parent = <&its>;
-> > + iommu-parent = <&smmu>;
-> > #address-cells = <3>;
-> > #size-cells = <1>;
+> > compatible =3D "fsl,qoriq-mc";
+> > reg =3D <0x00000008 0x0c000000 0 0x40>, /* MC porta=
+l base */
+> > <0x00000000 0x08340000 0 0x40000>; /* MC control=
+ reg */
+> > msi-parent =3D <&its>;
+> > + iommu-parent =3D <&smmu>;
+> > #address-cells =3D <3>;
+> > #size-cells =3D <1>;
> >
> > --
> > 1.9.1
@@ -125,9 +138,10 @@ Nipun
> > linux-arm-kernel mailing list
> > linux-arm-kernel@lists.infradead.org
> >
-> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.infr
+> https://emea01.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2Flists=
+.infr
> adead.org%2Fmailman%2Flistinfo%2Flinux-arm-
-> kernel&data=02%7C01%7Cnipun.gupta%40nxp.com%7Cf64b4fe9c5cf45ce8a9a
+> kernel&data=3D02%7C01%7Cnipun.gupta%40nxp.com%7Cf64b4fe9c5cf45ce8a9a
> 08d5847c6919%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C636560
-> 592302736942&sdata=iOwv%2Fzd8UTLm7YCapDOWzrtd48VQeYY2vlufck7eYZI
-> %3D&reserved=0
\ No newline at end of file
+> 592302736942&sdata=3DiOwv%2Fzd8UTLm7YCapDOWzrtd48VQeYY2vlufck7eYZI
+> %3D&reserved=3D0
\ No newline at end of file
diff --git a/a/content_digest b/N2/content_digest
index 89ab40d..d55bc58 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -55,12 +55,14 @@
"> Cc: will.deacon\@arm.com; robin.murphy\@arm.com; mark.rutland\@arm.com;\n",
"> catalin.marinas\@arm.com; devicetree\@vger.kernel.org; stuyoder\@gmail.com;\n",
"> Bharat Bhushan <bharat.bhushan\@nxp.com>; gregkh\@linuxfoundation.org;\n",
- "> joro\@8bytes.org; linuxppc-dev\@lists.ozlabs.org; linux-kernel\@vger.kernel.org;\n",
+ "> joro\@8bytes.org; linuxppc-dev\@lists.ozlabs.org; linux-kernel\@vger.kernel.=\n",
+ "org;\n",
"> Leo Li <leoyang.li\@nxp.com>; iommu\@lists.linux-foundation.org; Laurentiu\n",
"> Tudor <laurentiu.tudor\@nxp.com>; shawnguo\@kernel.org; hch\@lst.de; linux-\n",
"> arm-kernel\@lists.infradead.org; m.szyprowski\@samsung.com\n",
- "> Subject: Re: [PATCH 1/6] Docs: dt: add fsl-mc iommu-parent device-tree binding\n",
- "> \n",
+ "> Subject: Re: [PATCH 1/6] Docs: dt: add fsl-mc iommu-parent device-tree bi=\n",
+ "nding\n",
+ ">=20\n",
"> On Mon, Mar 05, 2018 at 07:59:21PM +0530, Nipun Gupta wrote:\n",
"> > The existing IOMMU bindings cannot be used to specify the relationship\n",
"> > between fsl-mc devices and IOMMUs. This patch adds a binding for\n",
@@ -85,27 +87,33 @@
"> > +For an overview of the DPAA2 architecture and fsl-mc bus see:\n",
"> > +drivers/staging/fsl-mc/README.txt\n",
"> > +\n",
- "> > +As described in the above overview, all DPAA2 objects in a DPRC share the\n",
+ "> > +As described in the above overview, all DPAA2 objects in a DPRC share =\n",
+ "the\n",
"> > +same hardware \"isolation context\" and a 10-bit value called an ICID\n",
"> > +(isolation context id) is expressed by the hardware to identify\n",
"> > +the requester.\n",
"> > +\n",
- "> > +The generic 'iommus' property is cannot be used to describe the relationship\n",
- "> > +between fsl-mc and IOMMUs, so an iommu-parent property is used to define\n",
+ "> > +The generic 'iommus' property is cannot be used to describe the relati=\n",
+ "onship\n",
+ "> > +between fsl-mc and IOMMUs, so an iommu-parent property is used to defi=\n",
+ "ne\n",
"> > +the same.\n",
- "> \n",
+ ">=20\n",
"> Why not? It is just a link between 2 nodes.\n",
"\n",
- "We have #iommu-cells as '1' i.e. iommu will have one stream ID configured for a device.\n",
- "Once USB and other devices start to use IOMMU we will also need this iommu-cells.\n",
+ "We have #iommu-cells as '1' i.e. iommu will have one stream ID configured f=\n",
+ "or a device.\n",
+ "Once USB and other devices start to use IOMMU we will also need this iommu-=\n",
+ "cells.\n",
"\n",
- "When #iommu-cells is defined as '1' and we have 'iommus=<&smmu>' compilation\n",
+ "When #iommu-cells is defined as '1' and we have 'iommus=3D<&smmu>' compilat=\n",
+ "ion\n",
"reports warning about the mismatch.\n",
"In fsl-mc bus case we do not have any stream id associated with the bus.\n",
"\n",
"As suggested by Robin, we can simply use the iommu-map property.\n",
"\n",
- "> \n",
+ ">=20\n",
"> > +\n",
"> > +For generic IOMMU bindings, see\n",
"> > +Documentation/devicetree/bindings/iommu/iommu.txt.\n",
@@ -118,26 +126,29 @@
"> > - compatible\n",
"> > \@\@ -88,14 +106,27 \@\@ Sub-nodes:\n",
"> > Value type: <phandle>\n",
- "> > Definition: Specifies the phandle to the PHY device node associated\n",
+ "> > Definition: Specifies the phandle to the PHY device node=\n",
+ " associated\n",
"> > with the this dpmac.\n",
"> > +Optional properties:\n",
"> > +\n",
"> > +- iommu-parent: Maps the devices on fsl-mc bus to an IOMMU.\n",
"> > + The property specifies the IOMMU behind which the devices on\n",
"> > + fsl-mc bus are residing.\n",
- "> \n",
+ ">=20\n",
"> If you want a generic property, this should be documented in the common\n",
"> binding.\n",
"\n",
"We can use the iommu-map property which is already documented.\n",
"\n",
- "> \n",
+ ">=20\n",
"> Couldn't you have more than 1 IOMMU upstream of a MC?\n",
"\n",
- "There is no such device currently with which fsl-mc bus uses more than one iommu.\n",
+ "There is no such device currently with which fsl-mc bus uses more than one =\n",
+ "iommu.\n",
"Infact, our current systems have only single IOMMU :).\n",
"\n",
- "Even in future if such devices are there then we can use iommu-map to specify\n",
+ "Even in future if such devices are there then we can use iommu-map to speci=\n",
+ "fy\n",
"more than one iommu with separate requester ID's (RID's).\n",
"\n",
"Thank you for review...\n",
@@ -145,25 +156,27 @@
"Regards,\n",
"Nipun\n",
"\n",
- "> \n",
+ ">=20\n",
"> >\n",
"> > Example:\n",
"> >\n",
"> > + smmu: iommu\@5000000 {\n",
- "> > + compatible = \"arm,mmu-500\";\n",
- "> > + #iommu-cells = <1>;\n",
- "> > + stream-match-mask = <0x7C00>;\n",
+ "> > + compatible =3D \"arm,mmu-500\";\n",
+ "> > + #iommu-cells =3D <1>;\n",
+ "> > + stream-match-mask =3D <0x7C00>;\n",
"> > + ...\n",
"> > + };\n",
"> > +\n",
"> > fsl_mc: fsl-mc\@80c000000 {\n",
- "> > compatible = \"fsl,qoriq-mc\";\n",
- "> > reg = <0x00000008 0x0c000000 0 0x40>, /* MC portal base */\n",
- "> > <0x00000000 0x08340000 0 0x40000>; /* MC control reg */\n",
- "> > msi-parent = <&its>;\n",
- "> > + iommu-parent = <&smmu>;\n",
- "> > #address-cells = <3>;\n",
- "> > #size-cells = <1>;\n",
+ "> > compatible =3D \"fsl,qoriq-mc\";\n",
+ "> > reg =3D <0x00000008 0x0c000000 0 0x40>, /* MC porta=\n",
+ "l base */\n",
+ "> > <0x00000000 0x08340000 0 0x40000>; /* MC control=\n",
+ " reg */\n",
+ "> > msi-parent =3D <&its>;\n",
+ "> > + iommu-parent =3D <&smmu>;\n",
+ "> > #address-cells =3D <3>;\n",
+ "> > #size-cells =3D <1>;\n",
"> >\n",
"> > --\n",
"> > 1.9.1\n",
@@ -173,12 +186,13 @@
"> > linux-arm-kernel mailing list\n",
"> > linux-arm-kernel\@lists.infradead.org\n",
"> >\n",
- "> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.infr\n",
+ "> https://emea01.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2Flists=\n",
+ ".infr\n",
"> adead.org%2Fmailman%2Flistinfo%2Flinux-arm-\n",
- "> kernel&data=02%7C01%7Cnipun.gupta%40nxp.com%7Cf64b4fe9c5cf45ce8a9a\n",
+ "> kernel&data=3D02%7C01%7Cnipun.gupta%40nxp.com%7Cf64b4fe9c5cf45ce8a9a\n",
"> 08d5847c6919%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C636560\n",
- "> 592302736942&sdata=iOwv%2Fzd8UTLm7YCapDOWzrtd48VQeYY2vlufck7eYZI\n",
- "> %3D&reserved=0"
+ "> 592302736942&sdata=3DiOwv%2Fzd8UTLm7YCapDOWzrtd48VQeYY2vlufck7eYZI\n",
+ "> %3D&reserved=3D0"
]
-9b2c43b4f6af762b8838f7a85a0bc151fe6885b5326bb66d1b404ef27fba1a42
+957fe59e8cdcfb67af4471aa4aab333bb6805ba1631baf273e5480ec63aa6d77
diff --git a/a/1.txt b/N3/1.txt
index 4805389..ae15a7f 100644
--- a/a/1.txt
+++ b/N3/1.txt
@@ -1,16 +1,16 @@
Hi Rob,
> -----Original Message-----
-> From: Rob Herring [mailto:robh@kernel.org]
+> From: Rob Herring [mailto:robh at kernel.org]
> Sent: Thursday, March 08, 2018 4:10
> To: Nipun Gupta <nipun.gupta@nxp.com>
-> Cc: will.deacon@arm.com; robin.murphy@arm.com; mark.rutland@arm.com;
-> catalin.marinas@arm.com; devicetree@vger.kernel.org; stuyoder@gmail.com;
-> Bharat Bhushan <bharat.bhushan@nxp.com>; gregkh@linuxfoundation.org;
-> joro@8bytes.org; linuxppc-dev@lists.ozlabs.org; linux-kernel@vger.kernel.org;
-> Leo Li <leoyang.li@nxp.com>; iommu@lists.linux-foundation.org; Laurentiu
-> Tudor <laurentiu.tudor@nxp.com>; shawnguo@kernel.org; hch@lst.de; linux-
-> arm-kernel@lists.infradead.org; m.szyprowski@samsung.com
+> Cc: will.deacon at arm.com; robin.murphy at arm.com; mark.rutland at arm.com;
+> catalin.marinas at arm.com; devicetree at vger.kernel.org; stuyoder at gmail.com;
+> Bharat Bhushan <bharat.bhushan@nxp.com>; gregkh at linuxfoundation.org;
+> joro at 8bytes.org; linuxppc-dev at lists.ozlabs.org; linux-kernel at vger.kernel.org;
+> Leo Li <leoyang.li@nxp.com>; iommu at lists.linux-foundation.org; Laurentiu
+> Tudor <laurentiu.tudor@nxp.com>; shawnguo at kernel.org; hch at lst.de; linux-
+> arm-kernel at lists.infradead.org; m.szyprowski at samsung.com
> Subject: Re: [PATCH 1/6] Docs: dt: add fsl-mc iommu-parent device-tree binding
>
> On Mon, Mar 05, 2018 at 07:59:21PM +0530, Nipun Gupta wrote:
@@ -101,14 +101,14 @@ Nipun
> >
> > Example:
> >
-> > + smmu: iommu@5000000 {
+> > + smmu: iommu at 5000000 {
> > + compatible = "arm,mmu-500";
> > + #iommu-cells = <1>;
> > + stream-match-mask = <0x7C00>;
> > + ...
> > + };
> > +
-> > fsl_mc: fsl-mc@80c000000 {
+> > fsl_mc: fsl-mc at 80c000000 {
> > compatible = "fsl,qoriq-mc";
> > reg = <0x00000008 0x0c000000 0 0x40>, /* MC portal base */
> > <0x00000000 0x08340000 0 0x40000>; /* MC control reg */
@@ -123,7 +123,7 @@ Nipun
> >
> > _______________________________________________
> > linux-arm-kernel mailing list
-> > linux-arm-kernel@lists.infradead.org
+> > linux-arm-kernel at lists.infradead.org
> >
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.infr
> adead.org%2Fmailman%2Flistinfo%2Flinux-arm-
diff --git a/a/content_digest b/N3/content_digest
index 89ab40d..9985e7b 100644
--- a/a/content_digest
+++ b/N3/content_digest
@@ -8,36 +8,16 @@
"ref\00020180307224019.oowh74pkbi5izuft\@rob-hp-laptop\0"
]
[
- "From\0Nipun Gupta <nipun.gupta\@nxp.com>\0"
+ "From\0nipun.gupta\@nxp.com (Nipun Gupta)\0"
]
[
- "Subject\0RE: [PATCH 1/6] Docs: dt: add fsl-mc iommu-parent device-tree binding\0"
+ "Subject\0[PATCH 1/6] Docs: dt: add fsl-mc iommu-parent device-tree binding\0"
]
[
"Date\0Thu, 8 Mar 2018 12:32:28 +0000\0"
]
[
- "To\0Rob Herring <robh\@kernel.org>\0"
-]
-[
- "Cc\0will.deacon\@arm.com <will.deacon\@arm.com>",
- " robin.murphy\@arm.com <robin.murphy\@arm.com>",
- " mark.rutland\@arm.com <mark.rutland\@arm.com>",
- " catalin.marinas\@arm.com <catalin.marinas\@arm.com>",
- " devicetree\@vger.kernel.org <devicetree\@vger.kernel.org>",
- " stuyoder\@gmail.com <stuyoder\@gmail.com>",
- " Bharat Bhushan <bharat.bhushan\@nxp.com>",
- " gregkh\@linuxfoundation.org <gregkh\@linuxfoundation.org>",
- " joro\@8bytes.org <joro\@8bytes.org>",
- " linuxppc-dev\@lists.ozlabs.org <linuxppc-dev\@lists.ozlabs.org>",
- " linux-kernel\@vger.kernel.org <linux-kernel\@vger.kernel.org>",
- " Leo Li <leoyang.li\@nxp.com>",
- " iommu\@lists.linux-foundation.org <iommu\@lists.linux-foundation.org>",
- " Laurentiu Tudor <laurentiu.tudor\@nxp.com>",
- " shawnguo\@kernel.org <shawnguo\@kernel.org>",
- " hch\@lst.de <hch\@lst.de>",
- " linux-arm-kernel\@lists.infradead.org <linux-arm-kernel\@lists.infradead.org>",
- " m.szyprowski\@samsung.com <m.szyprowski\@samsung.com>\0"
+ "To\0linux-arm-kernel\@lists.infradead.org\0"
]
[
"\0000:1\0"
@@ -49,16 +29,16 @@
"Hi Rob,\n",
"\n",
"> -----Original Message-----\n",
- "> From: Rob Herring [mailto:robh\@kernel.org]\n",
+ "> From: Rob Herring [mailto:robh at kernel.org]\n",
"> Sent: Thursday, March 08, 2018 4:10\n",
"> To: Nipun Gupta <nipun.gupta\@nxp.com>\n",
- "> Cc: will.deacon\@arm.com; robin.murphy\@arm.com; mark.rutland\@arm.com;\n",
- "> catalin.marinas\@arm.com; devicetree\@vger.kernel.org; stuyoder\@gmail.com;\n",
- "> Bharat Bhushan <bharat.bhushan\@nxp.com>; gregkh\@linuxfoundation.org;\n",
- "> joro\@8bytes.org; linuxppc-dev\@lists.ozlabs.org; linux-kernel\@vger.kernel.org;\n",
- "> Leo Li <leoyang.li\@nxp.com>; iommu\@lists.linux-foundation.org; Laurentiu\n",
- "> Tudor <laurentiu.tudor\@nxp.com>; shawnguo\@kernel.org; hch\@lst.de; linux-\n",
- "> arm-kernel\@lists.infradead.org; m.szyprowski\@samsung.com\n",
+ "> Cc: will.deacon at arm.com; robin.murphy at arm.com; mark.rutland at arm.com;\n",
+ "> catalin.marinas at arm.com; devicetree at vger.kernel.org; stuyoder at gmail.com;\n",
+ "> Bharat Bhushan <bharat.bhushan\@nxp.com>; gregkh at linuxfoundation.org;\n",
+ "> joro at 8bytes.org; linuxppc-dev at lists.ozlabs.org; linux-kernel at vger.kernel.org;\n",
+ "> Leo Li <leoyang.li\@nxp.com>; iommu at lists.linux-foundation.org; Laurentiu\n",
+ "> Tudor <laurentiu.tudor\@nxp.com>; shawnguo at kernel.org; hch at lst.de; linux-\n",
+ "> arm-kernel at lists.infradead.org; m.szyprowski at samsung.com\n",
"> Subject: Re: [PATCH 1/6] Docs: dt: add fsl-mc iommu-parent device-tree binding\n",
"> \n",
"> On Mon, Mar 05, 2018 at 07:59:21PM +0530, Nipun Gupta wrote:\n",
@@ -149,14 +129,14 @@
"> >\n",
"> > Example:\n",
"> >\n",
- "> > + smmu: iommu\@5000000 {\n",
+ "> > + smmu: iommu at 5000000 {\n",
"> > + compatible = \"arm,mmu-500\";\n",
"> > + #iommu-cells = <1>;\n",
"> > + stream-match-mask = <0x7C00>;\n",
"> > + ...\n",
"> > + };\n",
"> > +\n",
- "> > fsl_mc: fsl-mc\@80c000000 {\n",
+ "> > fsl_mc: fsl-mc at 80c000000 {\n",
"> > compatible = \"fsl,qoriq-mc\";\n",
"> > reg = <0x00000008 0x0c000000 0 0x40>, /* MC portal base */\n",
"> > <0x00000000 0x08340000 0 0x40000>; /* MC control reg */\n",
@@ -171,7 +151,7 @@
"> >\n",
"> > _______________________________________________\n",
"> > linux-arm-kernel mailing list\n",
- "> > linux-arm-kernel\@lists.infradead.org\n",
+ "> > linux-arm-kernel at lists.infradead.org\n",
"> >\n",
"> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.infr\n",
"> adead.org%2Fmailman%2Flistinfo%2Flinux-arm-\n",
@@ -181,4 +161,4 @@
"> %3D&reserved=0"
]
-9b2c43b4f6af762b8838f7a85a0bc151fe6885b5326bb66d1b404ef27fba1a42
+319a7e947014b63369fda4ebaa7d6ed0bcce5d9b7d97996d65a54727fa62f204
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.