diff for duplicates of <1375142451.30721.68@snotra> diff --git a/a/1.txt b/N1/1.txt index 13982a0..f964ec2 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,13 +1,13 @@ On 07/27/2013 08:03:42 AM, Shaveta Leekha wrote: > Signed-off-by: Shaveta Leekha <shaveta@freescale.com> > --- -> .../devicetree/bindings/powerpc/fsl/maple.txt | 50 =20 +> .../devicetree/bindings/powerpc/fsl/maple.txt | 50 > ++++++++++++++++++++ > 1 files changed, 50 insertions(+), 0 deletions(-) -> create mode 100644 =20 +> create mode 100644 > Documentation/devicetree/bindings/powerpc/fsl/maple.txt ->=20 -> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/maple.txt =20 +> +> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/maple.txt > b/Documentation/devicetree/bindings/powerpc/fsl/maple.txt > new file mode 100644 > index 0000000..23b80a7 @@ -26,31 +26,31 @@ On 07/27/2013 08:03:42 AM, Shaveta Leekha wrote: > + This identifies Multi Accelerator Platform Engine > + Baseband 3 block. > + -> +- reg: offset and length of the register set for the =20 +> +- reg: offset and length of the register set for the > device > + > +- interrupts > + Usage: required > + Value type: <prop_encoded-array> -> + Definition: Specifies the interrupts generated by this =20 +> + Definition: Specifies the interrupts generated by this > device. The -> + value of the interrupts property consists of =20 +> + value of the interrupts property consists of > one interrupt -> + specifier. The format of the specifier is =20 +> + specifier. The format of the specifier is > defined by the -> + binding document describing the node's =20 +> + binding document describing the node's > interrupt parent. Please clean up whitespace so the text aligns. > + -> + A single IRQ that handles error conditions is specified =20 +> + A single IRQ that handles error conditions is specified > by > + this property. (Typically shared with port-write). > + -> +Devices that have LIODNs need to specify links to the parent PAMU =20 +> +Devices that have LIODNs need to specify links to the parent PAMU > controller -> +(the actual PAMU controller that this device is connected to) and a =20 +> +(the actual PAMU controller that this device is connected to) and a > pointer to > +the LIODN register, if applicable. > + @@ -58,34 +58,34 @@ Please clean up whitespace so the text aligns. > + : <phandle> > + This property should be present > + -> +- status =3D "disabled" +> +- status = "disabled" > + In this example, status is set "disabled", -> + As Maple device wouldn't be used by PPC Linux. This =20 +> + As Maple device wouldn't be used by PPC Linux. This > representation is required > + for doing the PAMU programming on the Linux side. -Is it proper for Linux to even set the LIODN on a device that is =20 -"disabled"? Perhaps the compatible should be different, such as =20 -"fsl,maple-b3-liodn" to indicate that that is the only portion of the =20 +Is it proper for Linux to even set the LIODN on a device that is +"disabled"? Perhaps the compatible should be different, such as +"fsl,maple-b3-liodn" to indicate that that is the only portion of the device that is owned by this partition. > +Example: > + /* B4860 */ > + > + maple@800000 { -> + #address-cells =3D <0>; -> + #size-cells =3D <0>; -> + status =3D "disabled"; -> + compatible =3D "fsl,maple-b3"; -> + reg =3D <0x8000000 0x10000>; -> + interrupts =3D <16 2 1 18>; -> + fsl,iommu-parent =3D <&pamu1>; +> + #address-cells = <0>; +> + #size-cells = <0>; +> + status = "disabled"; +> + compatible = "fsl,maple-b3"; +> + reg = <0x8000000 0x10000>; +> + interrupts = <16 2 1 18>; +> + fsl,iommu-parent = <&pamu1>; > + }; -This error interrupt is documented as 13, not 18. b4860 (and maybe =20 -other b4?) have an erratum that says that error interrupts are =20 -reversed, but this is generally implemented in b4si-post.dtsi, not in =20 -block-specific include files. Will no chip without the erratum ever =20 +This error interrupt is documented as 13, not 18. b4860 (and maybe +other b4?) have an erratum that says that error interrupts are +reversed, but this is generally implemented in b4si-post.dtsi, not in +block-specific include files. Will no chip without the erratum ever have maple? --Scott= +-Scott diff --git a/a/content_digest b/N1/content_digest index e3fc7d5..2eba5bc 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,7 +2,6 @@ "From\0Scott Wood <scottwood@freescale.com>\0" "Subject\0Re: [PATCH] Add device file bindings for MAPLE\0" "Date\0Mon, 29 Jul 2013 19:00:51 -0500\0" - "To\0Shaveta Leekha <shaveta@freescale.com>\0" "Cc\0Shaveta Leekha <shaveta@freescale.com>" devicetree-discuss@lists.ozlabs.org " linuxppc-dev@lists.ozlabs.org\0" @@ -11,13 +10,13 @@ "On 07/27/2013 08:03:42 AM, Shaveta Leekha wrote:\n" "> Signed-off-by: Shaveta Leekha <shaveta@freescale.com>\n" "> ---\n" - "> .../devicetree/bindings/powerpc/fsl/maple.txt | 50 =20\n" + "> .../devicetree/bindings/powerpc/fsl/maple.txt | 50 \n" "> ++++++++++++++++++++\n" "> 1 files changed, 50 insertions(+), 0 deletions(-)\n" - "> create mode 100644 =20\n" + "> create mode 100644 \n" "> Documentation/devicetree/bindings/powerpc/fsl/maple.txt\n" - ">=20\n" - "> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/maple.txt =20\n" + "> \n" + "> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/maple.txt \n" "> b/Documentation/devicetree/bindings/powerpc/fsl/maple.txt\n" "> new file mode 100644\n" "> index 0000000..23b80a7\n" @@ -36,31 +35,31 @@ "> +\t\tThis identifies Multi Accelerator Platform Engine\n" "> +\t\tBaseband 3 block.\n" "> +\n" - "> +- reg:\t\toffset and length of the register set for the =20\n" + "> +- reg:\t\toffset and length of the register set for the \n" "> device\n" "> +\n" "> +- interrupts\n" "> +\tUsage: required\n" "> +\tValue type: <prop_encoded-array>\n" - "> +\tDefinition: Specifies the interrupts generated by this =20\n" + "> +\tDefinition: Specifies the interrupts generated by this \n" "> device. The\n" - "> +\t\t\tvalue of the interrupts property consists of =20\n" + "> +\t\t\tvalue of the interrupts property consists of \n" "> one interrupt\n" - "> +\t\t\tspecifier. The format of the specifier is =20\n" + "> +\t\t\tspecifier. The format of the specifier is \n" "> defined by the\n" - "> +\t\t\tbinding document describing the node's =20\n" + "> +\t\t\tbinding document describing the node's \n" "> interrupt parent.\n" "\n" "Please clean up whitespace so the text aligns.\n" "\n" "> +\n" - "> +\t\tA single IRQ that handles error conditions is specified =20\n" + "> +\t\tA single IRQ that handles error conditions is specified \n" "> by\n" "> +\t\tthis property. (Typically shared with port-write).\n" "> +\n" - "> +Devices that have LIODNs need to specify links to the parent PAMU =20\n" + "> +Devices that have LIODNs need to specify links to the parent PAMU \n" "> controller\n" - "> +(the actual PAMU controller that this device is connected to) and a =20\n" + "> +(the actual PAMU controller that this device is connected to) and a \n" "> pointer to\n" "> +the LIODN register, if applicable.\n" "> +\n" @@ -68,36 +67,36 @@ "> +\t\t: <phandle>\n" "> +\t\tThis property should be present\n" "> +\n" - "> +- status =3D \"disabled\"\n" + "> +- status = \"disabled\"\n" "> +\t\tIn this example, status is set \"disabled\",\n" - "> +\t\tAs Maple device wouldn't be used by PPC Linux. This =20\n" + "> +\t\tAs Maple device wouldn't be used by PPC Linux. This \n" "> representation is required\n" "> +\t\tfor doing the PAMU programming on the Linux side.\n" "\n" - "Is it proper for Linux to even set the LIODN on a device that is =20\n" - "\"disabled\"? Perhaps the compatible should be different, such as =20\n" - "\"fsl,maple-b3-liodn\" to indicate that that is the only portion of the =20\n" + "Is it proper for Linux to even set the LIODN on a device that is \n" + "\"disabled\"? Perhaps the compatible should be different, such as \n" + "\"fsl,maple-b3-liodn\" to indicate that that is the only portion of the \n" "device that is owned by this partition.\n" "\n" "> +Example:\n" "> +\t/* B4860 */\n" "> +\n" "> +\tmaple@800000 {\n" - "> +\t\t#address-cells =3D <0>;\n" - "> +\t\t#size-cells =3D <0>;\n" - "> +\t\tstatus =3D \"disabled\";\n" - "> +\t\tcompatible =3D \"fsl,maple-b3\";\n" - "> +\t\treg =3D <0x8000000 0x10000>;\n" - "> +\t\tinterrupts =3D <16 2 1 18>;\n" - "> +\t\tfsl,iommu-parent =3D <&pamu1>;\n" + "> +\t\t#address-cells = <0>;\n" + "> +\t\t#size-cells = <0>;\n" + "> +\t\tstatus = \"disabled\";\n" + "> +\t\tcompatible = \"fsl,maple-b3\";\n" + "> +\t\treg = <0x8000000 0x10000>;\n" + "> +\t\tinterrupts = <16 2 1 18>;\n" + "> +\t\tfsl,iommu-parent = <&pamu1>;\n" "> +\t};\n" "\n" - "This error interrupt is documented as 13, not 18. b4860 (and maybe =20\n" - "other b4?) have an erratum that says that error interrupts are =20\n" - "reversed, but this is generally implemented in b4si-post.dtsi, not in =20\n" - "block-specific include files. Will no chip without the erratum ever =20\n" + "This error interrupt is documented as 13, not 18. b4860 (and maybe \n" + "other b4?) have an erratum that says that error interrupts are \n" + "reversed, but this is generally implemented in b4si-post.dtsi, not in \n" + "block-specific include files. Will no chip without the erratum ever \n" "have maple?\n" "\n" - -Scott= + -Scott -0e5fe7d3a4ef2115fbea5a8597d8de665ec98b45b8725c8067759e83c9ca3134 +53fdccb6617cf8317face9e9c83a84c5a77e8df6eca3bd69e34afe9ccfd76811
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.