diff for duplicates of <1374515600.15592.8@snotra> diff --git a/a/1.txt b/N1/1.txt index 42dad14..f82afee 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,19 +1,19 @@ On 07/22/2013 12:55:38 AM, hongbo.zhang@freescale.com wrote: > From: Hongbo Zhang <hongbo.zhang@freescale.com> ->=20 -> This updates the discription of each type of DMA controller and its =20 +> +> This updates the discription of each type of DMA controller and its > channels, -> it is preparation for adding another new DMA controller binding, also =20 +> it is preparation for adding another new DMA controller binding, also > fixes > some defects of indent for text alignment at the same time. ->=20 +> > Signed-off-by: Hongbo Zhang <hongbo.zhang@freescale.com> > --- -> .../devicetree/bindings/powerpc/fsl/dma.txt | 56 =20 +> .../devicetree/bindings/powerpc/fsl/dma.txt | 56 > +++++++++++--------- > 1 file changed, 30 insertions(+), 26 deletions(-) ->=20 -> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt =20 +> +> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt > b/Documentation/devicetree/bindings/powerpc/fsl/dma.txt > index 2a4b4bc..0650171 100644 > --- a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt @@ -21,72 +21,72 @@ On 07/22/2013 12:55:38 AM, hongbo.zhang@freescale.com wrote: > @@ -1,33 +1,33 @@ > -* Freescale 83xx DMA Controller > +* Freescale DMA Controllers ->=20 +> > -Freescale PowerPC 83xx have on chip general purpose DMA controllers. > +** Freescale ELO DMA Controller > + This is a little-endian DMA controller. > + Used in Freescale PowerPC 83xx series, such as: -> + mpc8313, mpc8315, mpc8323, mpc8347, mpc8349, mpc8360, mpc8377, =20 +> + mpc8313, mpc8315, mpc8323, mpc8347, mpc8349, mpc8360, mpc8377, > mpc8378, mpc8379. -You don't need to list every single chip... What happens when new =20 -chips come out (not so likely with mpc83xx, but more likely for =20 -eloplus/elo3)? Do we keep updating this, or have a list that looks =20 +You don't need to list every single chip... What happens when new +chips come out (not so likely with mpc83xx, but more likely for +eloplus/elo3)? Do we keep updating this, or have a list that looks complete but isn't? -My point in suggesting that some examples be given is just so that the =20 -reader knows where to find a manual that documents a particular version =20 +My point in suggesting that some examples be given is just so that the +reader knows where to find a manual that documents a particular version of "elo", and to give a rough idea of what product families use it. -> -Freescale PowerPC 85xx/86xx have on chip general purpose DMA =20 +> -Freescale PowerPC 85xx/86xx have on chip general purpose DMA > controllers. > +** Freescale ELOPLUS DMA Controller > + This is DMA controller with extended addresses and chaining. -> + Used in Freescale PowerPC 85xx/86xx and pxxx series chips, such =20 +> + Used in Freescale PowerPC 85xx/86xx and pxxx series chips, such > as: > + [1] mpc8540, mpc8541, mpc8555, mpc8560, mpc8610, mpc8641, -> + [2] mpc8536, mpc8544, mpc8548, mpc8568, mpc8569, mpc8572, p1010, =20 +> + [2] mpc8536, mpc8544, mpc8548, mpc8568, mpc8569, mpc8572, p1010, > p1020, p1021, -> + p1022, p1023, p2020, p2041, p3041, p4080, p5020, p5040, and =20 +> + p1022, p1023, p2020, p2041, p3041, p4080, p5020, p5040, and > also bsc9131. What do [1] and [2] signify here? -Oh, I see. It's weird for footnotes to come before the place they're =20 +Oh, I see. It's weird for footnotes to come before the place they're referenced... > Required properties: ->=20 +> > -- compatible : compatible list, contains 2 entries, first is > - "fsl,CHIP-dma", where CHIP is the processor > - (mpc8540, mpc8540, etc.) and the second is > - "fsl,eloplus-dma" -> +- compatible : compatible list, contains 2 entries for chips =20 +> +- compatible : compatible list, contains 2 entries for chips > in above -> + list[1], the first is "fsl,CHIP-dma", where =20 +> + list[1], the first is "fsl,CHIP-dma", where > CHIP is the -> + processor and the second is "fsl,eloplus-dma". =20 +> + processor and the second is "fsl,eloplus-dma". > contains -> + only one "fsl,eloplus-dma" for chips in above =20 +> + only one "fsl,eloplus-dma" for chips in above > list[2] -Don't encode this difference in the binding document. It wasn't on =20 -purpose, but rather an artifact of factoring things out into dtsi =20 +Don't encode this difference in the binding document. It wasn't on +purpose, but rather an artifact of factoring things out into dtsi files. Just make it optional. -Why can't we just talk about what compatible must include, as I =20 +Why can't we just talk about what compatible must include, as I suggested earlier, rather than what it must *be*? > - reg : <registers mapping for DMA general status reg> > - cell-index : controller index. 0 for controller @ 0x21000, > 1 for controller @ 0xc000 -> -- ranges : Should be defined as specified in 1) to =20 +> -- ranges : Should be defined as specified in 1) to > describe the > - DMA controller channels. -> +- ranges : physical address range of DMA controller =20 +> +- ranges : physical address range of DMA controller > channels -ranges will not have physical addresses at this level. They'll only =20 +ranges will not have physical addresses at this level. They'll only become physical addresses when translated by the ccsr node's ranges. --Scott= +-Scott diff --git a/a/content_digest b/N1/content_digest index f93a9db..593ff6c 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,32 +2,32 @@ "From\0Scott Wood <scottwood@freescale.com>\0" "Subject\0Re: [PATCH v4 1/3] DMA: Freescale: revise device tree binding document\0" "Date\0Mon, 22 Jul 2013 12:53:20 -0500\0" - "To\0<hongbo.zhang@freescale.com>\0" "Cc\0vinod.koul@intel.com" + djbw@fb.com + leoli@freescale.com + linuxppc-dev@lists.ozlabs.org devicetree-discuss@lists.ozlabs.org linux-kernel@vger.kernel.org vakul@freescale.com - Hongbo Zhang <hongbo.zhang@freescale.com> - djbw@fb.com - " linuxppc-dev@lists.ozlabs.org\0" + " Hongbo Zhang <hongbo.zhang@freescale.com>\0" "\00:1\0" "b\0" "On 07/22/2013 12:55:38 AM, hongbo.zhang@freescale.com wrote:\n" "> From: Hongbo Zhang <hongbo.zhang@freescale.com>\n" - ">=20\n" - "> This updates the discription of each type of DMA controller and its =20\n" + "> \n" + "> This updates the discription of each type of DMA controller and its \n" "> channels,\n" - "> it is preparation for adding another new DMA controller binding, also =20\n" + "> it is preparation for adding another new DMA controller binding, also \n" "> fixes\n" "> some defects of indent for text alignment at the same time.\n" - ">=20\n" + "> \n" "> Signed-off-by: Hongbo Zhang <hongbo.zhang@freescale.com>\n" "> ---\n" - "> .../devicetree/bindings/powerpc/fsl/dma.txt | 56 =20\n" + "> .../devicetree/bindings/powerpc/fsl/dma.txt | 56 \n" "> +++++++++++---------\n" "> 1 file changed, 30 insertions(+), 26 deletions(-)\n" - ">=20\n" - "> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt =20\n" + "> \n" + "> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt \n" "> b/Documentation/devicetree/bindings/powerpc/fsl/dma.txt\n" "> index 2a4b4bc..0650171 100644\n" "> --- a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt\n" @@ -35,74 +35,74 @@ "> @@ -1,33 +1,33 @@\n" "> -* Freescale 83xx DMA Controller\n" "> +* Freescale DMA Controllers\n" - ">=20\n" + "> \n" "> -Freescale PowerPC 83xx have on chip general purpose DMA controllers.\n" "> +** Freescale ELO DMA Controller\n" "> + This is a little-endian DMA controller.\n" "> + Used in Freescale PowerPC 83xx series, such as:\n" - "> + mpc8313, mpc8315, mpc8323, mpc8347, mpc8349, mpc8360, mpc8377, =20\n" + "> + mpc8313, mpc8315, mpc8323, mpc8347, mpc8349, mpc8360, mpc8377, \n" "> mpc8378, mpc8379.\n" "\n" - "You don't need to list every single chip... What happens when new =20\n" - "chips come out (not so likely with mpc83xx, but more likely for =20\n" - "eloplus/elo3)? Do we keep updating this, or have a list that looks =20\n" + "You don't need to list every single chip... What happens when new \n" + "chips come out (not so likely with mpc83xx, but more likely for \n" + "eloplus/elo3)? Do we keep updating this, or have a list that looks \n" "complete but isn't?\n" "\n" - "My point in suggesting that some examples be given is just so that the =20\n" - "reader knows where to find a manual that documents a particular version =20\n" + "My point in suggesting that some examples be given is just so that the \n" + "reader knows where to find a manual that documents a particular version \n" "of \"elo\", and to give a rough idea of what product families use it.\n" "\n" - "> -Freescale PowerPC 85xx/86xx have on chip general purpose DMA =20\n" + "> -Freescale PowerPC 85xx/86xx have on chip general purpose DMA \n" "> controllers.\n" "> +** Freescale ELOPLUS DMA Controller\n" "> + This is DMA controller with extended addresses and chaining.\n" - "> + Used in Freescale PowerPC 85xx/86xx and pxxx series chips, such =20\n" + "> + Used in Freescale PowerPC 85xx/86xx and pxxx series chips, such \n" "> as:\n" "> + [1] mpc8540, mpc8541, mpc8555, mpc8560, mpc8610, mpc8641,\n" - "> + [2] mpc8536, mpc8544, mpc8548, mpc8568, mpc8569, mpc8572, p1010, =20\n" + "> + [2] mpc8536, mpc8544, mpc8548, mpc8568, mpc8569, mpc8572, p1010, \n" "> p1020, p1021,\n" - "> + p1022, p1023, p2020, p2041, p3041, p4080, p5020, p5040, and =20\n" + "> + p1022, p1023, p2020, p2041, p3041, p4080, p5020, p5040, and \n" "> also bsc9131.\n" "\n" "What do [1] and [2] signify here?\n" "\n" - "Oh, I see. It's weird for footnotes to come before the place they're =20\n" + "Oh, I see. It's weird for footnotes to come before the place they're \n" "referenced...\n" "\n" "> Required properties:\n" - ">=20\n" + "> \n" "> -- compatible : compatible list, contains 2 entries, first is\n" "> -\t\t \"fsl,CHIP-dma\", where CHIP is the processor\n" "> -\t\t (mpc8540, mpc8540, etc.) and the second is\n" "> -\t\t \"fsl,eloplus-dma\"\n" - "> +- compatible : compatible list, contains 2 entries for chips =20\n" + "> +- compatible : compatible list, contains 2 entries for chips \n" "> in above\n" - "> + list[1], the first is \"fsl,CHIP-dma\", where =20\n" + "> + list[1], the first is \"fsl,CHIP-dma\", where \n" "> CHIP is the\n" - "> + processor and the second is \"fsl,eloplus-dma\". =20\n" + "> + processor and the second is \"fsl,eloplus-dma\". \n" "> contains\n" - "> + only one \"fsl,eloplus-dma\" for chips in above =20\n" + "> + only one \"fsl,eloplus-dma\" for chips in above \n" "> list[2]\n" "\n" - "Don't encode this difference in the binding document. It wasn't on =20\n" - "purpose, but rather an artifact of factoring things out into dtsi =20\n" + "Don't encode this difference in the binding document. It wasn't on \n" + "purpose, but rather an artifact of factoring things out into dtsi \n" "files. Just make it optional.\n" "\n" - "Why can't we just talk about what compatible must include, as I =20\n" + "Why can't we just talk about what compatible must include, as I \n" "suggested earlier, rather than what it must *be*?\n" "\n" "> - reg : <registers mapping for DMA general status reg>\n" "> - cell-index : controller index. 0 for controller @ 0x21000,\n" "> 1 for controller @ 0xc000\n" - "> -- ranges\t\t: Should be defined as specified in 1) to =20\n" + "> -- ranges\t\t: Should be defined as specified in 1) to \n" "> describe the\n" "> -\t\t DMA controller channels.\n" - "> +- ranges : physical address range of DMA controller =20\n" + "> +- ranges : physical address range of DMA controller \n" "> channels\n" "\n" - "ranges will not have physical addresses at this level. They'll only =20\n" + "ranges will not have physical addresses at this level. They'll only \n" "become physical addresses when translated by the ccsr node's ranges.\n" "\n" - -Scott= + -Scott -71399025542b224b2c6d6f3cec1312555bd225848bee719e0d8aa144fa8d81a1 +79e6ee125ec2a95ab181ce01fe0f548bcfd2fe2e00e94b3484195fea515c22e9
diff --git a/a/1.txt b/N2/1.txt index 42dad14..f82afee 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,19 +1,19 @@ On 07/22/2013 12:55:38 AM, hongbo.zhang@freescale.com wrote: > From: Hongbo Zhang <hongbo.zhang@freescale.com> ->=20 -> This updates the discription of each type of DMA controller and its =20 +> +> This updates the discription of each type of DMA controller and its > channels, -> it is preparation for adding another new DMA controller binding, also =20 +> it is preparation for adding another new DMA controller binding, also > fixes > some defects of indent for text alignment at the same time. ->=20 +> > Signed-off-by: Hongbo Zhang <hongbo.zhang@freescale.com> > --- -> .../devicetree/bindings/powerpc/fsl/dma.txt | 56 =20 +> .../devicetree/bindings/powerpc/fsl/dma.txt | 56 > +++++++++++--------- > 1 file changed, 30 insertions(+), 26 deletions(-) ->=20 -> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt =20 +> +> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt > b/Documentation/devicetree/bindings/powerpc/fsl/dma.txt > index 2a4b4bc..0650171 100644 > --- a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt @@ -21,72 +21,72 @@ On 07/22/2013 12:55:38 AM, hongbo.zhang@freescale.com wrote: > @@ -1,33 +1,33 @@ > -* Freescale 83xx DMA Controller > +* Freescale DMA Controllers ->=20 +> > -Freescale PowerPC 83xx have on chip general purpose DMA controllers. > +** Freescale ELO DMA Controller > + This is a little-endian DMA controller. > + Used in Freescale PowerPC 83xx series, such as: -> + mpc8313, mpc8315, mpc8323, mpc8347, mpc8349, mpc8360, mpc8377, =20 +> + mpc8313, mpc8315, mpc8323, mpc8347, mpc8349, mpc8360, mpc8377, > mpc8378, mpc8379. -You don't need to list every single chip... What happens when new =20 -chips come out (not so likely with mpc83xx, but more likely for =20 -eloplus/elo3)? Do we keep updating this, or have a list that looks =20 +You don't need to list every single chip... What happens when new +chips come out (not so likely with mpc83xx, but more likely for +eloplus/elo3)? Do we keep updating this, or have a list that looks complete but isn't? -My point in suggesting that some examples be given is just so that the =20 -reader knows where to find a manual that documents a particular version =20 +My point in suggesting that some examples be given is just so that the +reader knows where to find a manual that documents a particular version of "elo", and to give a rough idea of what product families use it. -> -Freescale PowerPC 85xx/86xx have on chip general purpose DMA =20 +> -Freescale PowerPC 85xx/86xx have on chip general purpose DMA > controllers. > +** Freescale ELOPLUS DMA Controller > + This is DMA controller with extended addresses and chaining. -> + Used in Freescale PowerPC 85xx/86xx and pxxx series chips, such =20 +> + Used in Freescale PowerPC 85xx/86xx and pxxx series chips, such > as: > + [1] mpc8540, mpc8541, mpc8555, mpc8560, mpc8610, mpc8641, -> + [2] mpc8536, mpc8544, mpc8548, mpc8568, mpc8569, mpc8572, p1010, =20 +> + [2] mpc8536, mpc8544, mpc8548, mpc8568, mpc8569, mpc8572, p1010, > p1020, p1021, -> + p1022, p1023, p2020, p2041, p3041, p4080, p5020, p5040, and =20 +> + p1022, p1023, p2020, p2041, p3041, p4080, p5020, p5040, and > also bsc9131. What do [1] and [2] signify here? -Oh, I see. It's weird for footnotes to come before the place they're =20 +Oh, I see. It's weird for footnotes to come before the place they're referenced... > Required properties: ->=20 +> > -- compatible : compatible list, contains 2 entries, first is > - "fsl,CHIP-dma", where CHIP is the processor > - (mpc8540, mpc8540, etc.) and the second is > - "fsl,eloplus-dma" -> +- compatible : compatible list, contains 2 entries for chips =20 +> +- compatible : compatible list, contains 2 entries for chips > in above -> + list[1], the first is "fsl,CHIP-dma", where =20 +> + list[1], the first is "fsl,CHIP-dma", where > CHIP is the -> + processor and the second is "fsl,eloplus-dma". =20 +> + processor and the second is "fsl,eloplus-dma". > contains -> + only one "fsl,eloplus-dma" for chips in above =20 +> + only one "fsl,eloplus-dma" for chips in above > list[2] -Don't encode this difference in the binding document. It wasn't on =20 -purpose, but rather an artifact of factoring things out into dtsi =20 +Don't encode this difference in the binding document. It wasn't on +purpose, but rather an artifact of factoring things out into dtsi files. Just make it optional. -Why can't we just talk about what compatible must include, as I =20 +Why can't we just talk about what compatible must include, as I suggested earlier, rather than what it must *be*? > - reg : <registers mapping for DMA general status reg> > - cell-index : controller index. 0 for controller @ 0x21000, > 1 for controller @ 0xc000 -> -- ranges : Should be defined as specified in 1) to =20 +> -- ranges : Should be defined as specified in 1) to > describe the > - DMA controller channels. -> +- ranges : physical address range of DMA controller =20 +> +- ranges : physical address range of DMA controller > channels -ranges will not have physical addresses at this level. They'll only =20 +ranges will not have physical addresses at this level. They'll only become physical addresses when translated by the ccsr node's ranges. --Scott= +-Scott diff --git a/a/content_digest b/N2/content_digest index f93a9db..ebbe2a6 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -3,31 +3,32 @@ "Subject\0Re: [PATCH v4 1/3] DMA: Freescale: revise device tree binding document\0" "Date\0Mon, 22 Jul 2013 12:53:20 -0500\0" "To\0<hongbo.zhang@freescale.com>\0" - "Cc\0vinod.koul@intel.com" - devicetree-discuss@lists.ozlabs.org - linux-kernel@vger.kernel.org - vakul@freescale.com - Hongbo Zhang <hongbo.zhang@freescale.com> - djbw@fb.com - " linuxppc-dev@lists.ozlabs.org\0" + "Cc\0<vinod.koul@intel.com>" + <djbw@fb.com> + <leoli@freescale.com> + <linuxppc-dev@lists.ozlabs.org> + <devicetree-discuss@lists.ozlabs.org> + <linux-kernel@vger.kernel.org> + <vakul@freescale.com> + " Hongbo Zhang <hongbo.zhang@freescale.com>\0" "\00:1\0" "b\0" "On 07/22/2013 12:55:38 AM, hongbo.zhang@freescale.com wrote:\n" "> From: Hongbo Zhang <hongbo.zhang@freescale.com>\n" - ">=20\n" - "> This updates the discription of each type of DMA controller and its =20\n" + "> \n" + "> This updates the discription of each type of DMA controller and its \n" "> channels,\n" - "> it is preparation for adding another new DMA controller binding, also =20\n" + "> it is preparation for adding another new DMA controller binding, also \n" "> fixes\n" "> some defects of indent for text alignment at the same time.\n" - ">=20\n" + "> \n" "> Signed-off-by: Hongbo Zhang <hongbo.zhang@freescale.com>\n" "> ---\n" - "> .../devicetree/bindings/powerpc/fsl/dma.txt | 56 =20\n" + "> .../devicetree/bindings/powerpc/fsl/dma.txt | 56 \n" "> +++++++++++---------\n" "> 1 file changed, 30 insertions(+), 26 deletions(-)\n" - ">=20\n" - "> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt =20\n" + "> \n" + "> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt \n" "> b/Documentation/devicetree/bindings/powerpc/fsl/dma.txt\n" "> index 2a4b4bc..0650171 100644\n" "> --- a/Documentation/devicetree/bindings/powerpc/fsl/dma.txt\n" @@ -35,74 +36,74 @@ "> @@ -1,33 +1,33 @@\n" "> -* Freescale 83xx DMA Controller\n" "> +* Freescale DMA Controllers\n" - ">=20\n" + "> \n" "> -Freescale PowerPC 83xx have on chip general purpose DMA controllers.\n" "> +** Freescale ELO DMA Controller\n" "> + This is a little-endian DMA controller.\n" "> + Used in Freescale PowerPC 83xx series, such as:\n" - "> + mpc8313, mpc8315, mpc8323, mpc8347, mpc8349, mpc8360, mpc8377, =20\n" + "> + mpc8313, mpc8315, mpc8323, mpc8347, mpc8349, mpc8360, mpc8377, \n" "> mpc8378, mpc8379.\n" "\n" - "You don't need to list every single chip... What happens when new =20\n" - "chips come out (not so likely with mpc83xx, but more likely for =20\n" - "eloplus/elo3)? Do we keep updating this, or have a list that looks =20\n" + "You don't need to list every single chip... What happens when new \n" + "chips come out (not so likely with mpc83xx, but more likely for \n" + "eloplus/elo3)? Do we keep updating this, or have a list that looks \n" "complete but isn't?\n" "\n" - "My point in suggesting that some examples be given is just so that the =20\n" - "reader knows where to find a manual that documents a particular version =20\n" + "My point in suggesting that some examples be given is just so that the \n" + "reader knows where to find a manual that documents a particular version \n" "of \"elo\", and to give a rough idea of what product families use it.\n" "\n" - "> -Freescale PowerPC 85xx/86xx have on chip general purpose DMA =20\n" + "> -Freescale PowerPC 85xx/86xx have on chip general purpose DMA \n" "> controllers.\n" "> +** Freescale ELOPLUS DMA Controller\n" "> + This is DMA controller with extended addresses and chaining.\n" - "> + Used in Freescale PowerPC 85xx/86xx and pxxx series chips, such =20\n" + "> + Used in Freescale PowerPC 85xx/86xx and pxxx series chips, such \n" "> as:\n" "> + [1] mpc8540, mpc8541, mpc8555, mpc8560, mpc8610, mpc8641,\n" - "> + [2] mpc8536, mpc8544, mpc8548, mpc8568, mpc8569, mpc8572, p1010, =20\n" + "> + [2] mpc8536, mpc8544, mpc8548, mpc8568, mpc8569, mpc8572, p1010, \n" "> p1020, p1021,\n" - "> + p1022, p1023, p2020, p2041, p3041, p4080, p5020, p5040, and =20\n" + "> + p1022, p1023, p2020, p2041, p3041, p4080, p5020, p5040, and \n" "> also bsc9131.\n" "\n" "What do [1] and [2] signify here?\n" "\n" - "Oh, I see. It's weird for footnotes to come before the place they're =20\n" + "Oh, I see. It's weird for footnotes to come before the place they're \n" "referenced...\n" "\n" "> Required properties:\n" - ">=20\n" + "> \n" "> -- compatible : compatible list, contains 2 entries, first is\n" "> -\t\t \"fsl,CHIP-dma\", where CHIP is the processor\n" "> -\t\t (mpc8540, mpc8540, etc.) and the second is\n" "> -\t\t \"fsl,eloplus-dma\"\n" - "> +- compatible : compatible list, contains 2 entries for chips =20\n" + "> +- compatible : compatible list, contains 2 entries for chips \n" "> in above\n" - "> + list[1], the first is \"fsl,CHIP-dma\", where =20\n" + "> + list[1], the first is \"fsl,CHIP-dma\", where \n" "> CHIP is the\n" - "> + processor and the second is \"fsl,eloplus-dma\". =20\n" + "> + processor and the second is \"fsl,eloplus-dma\". \n" "> contains\n" - "> + only one \"fsl,eloplus-dma\" for chips in above =20\n" + "> + only one \"fsl,eloplus-dma\" for chips in above \n" "> list[2]\n" "\n" - "Don't encode this difference in the binding document. It wasn't on =20\n" - "purpose, but rather an artifact of factoring things out into dtsi =20\n" + "Don't encode this difference in the binding document. It wasn't on \n" + "purpose, but rather an artifact of factoring things out into dtsi \n" "files. Just make it optional.\n" "\n" - "Why can't we just talk about what compatible must include, as I =20\n" + "Why can't we just talk about what compatible must include, as I \n" "suggested earlier, rather than what it must *be*?\n" "\n" "> - reg : <registers mapping for DMA general status reg>\n" "> - cell-index : controller index. 0 for controller @ 0x21000,\n" "> 1 for controller @ 0xc000\n" - "> -- ranges\t\t: Should be defined as specified in 1) to =20\n" + "> -- ranges\t\t: Should be defined as specified in 1) to \n" "> describe the\n" "> -\t\t DMA controller channels.\n" - "> +- ranges : physical address range of DMA controller =20\n" + "> +- ranges : physical address range of DMA controller \n" "> channels\n" "\n" - "ranges will not have physical addresses at this level. They'll only =20\n" + "ranges will not have physical addresses at this level. They'll only \n" "become physical addresses when translated by the ccsr node's ranges.\n" "\n" - -Scott= + -Scott -71399025542b224b2c6d6f3cec1312555bd225848bee719e0d8aa144fa8d81a1 +16c7f3e47ec47f85b7a9964152543109676accf432e58849118db8d3261cac75
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.