diff for duplicates of <4FB3D294.4020505@wwwdotorg.org> diff --git a/a/1.txt b/N1/1.txt index 54a9260..196b4eb 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -13,7 +13,7 @@ On 05/16/2012 10:01 AM, Jon Hunter wrote: > > Take your example ... > -> mmc1: mmc@13002000 { +> mmc1: mmc at 13002000 { > ... > dma_tx = <891> //some platform-wide unique value > dma_rx = <927> //some platform-wide unique value @@ -31,7 +31,7 @@ client-defined client channel ID. ... > DMAC's Node:- > -> pdma2: pdma@10800000 { +> pdma2: pdma at 10800000 { > ....... > dma_map = <891, 7>, // Map mmc1_tx onto i/f 7 > <927, 8>, // Map mmc1_rx onto i/f 8 @@ -40,7 +40,7 @@ client-defined client channel ID. ... So this would become: -pdma2: pdma@10800000 { +pdma2: pdma at 10800000 { ....... dma-map = ... entries for channels 0.. 6 @@ -56,7 +56,7 @@ since all you need to do is search for the label "mmc1" throughout the DT. > But now I have another dmac which has the following options ... > -> pdma1: pdma@10000000 { +> pdma1: pdma at 10000000 { > ....... > dma_map = <598, 2>, // Map mmc1_tx onto i/f 2 > <230, 3>, // Map mmc1_rx onto i/f 3 @@ -65,7 +65,7 @@ since all you need to do is search for the label "mmc1" throughout the DT. Which would become something very similar: -pdma1: pdma@10000000 { +pdma1: pdma at 10000000 { ....... dma-map = ... entries for channels 0.. 1 @@ -87,7 +87,7 @@ signal, or not. > One way around this would be to have an enable/disable flag along with > the token such as ... > -> mmc1: mmc@13002000 { +> mmc1: mmc at 13002000 { > ... > dma_tx = <891, 1> // default tx channel > dma_rx = <927, 1> // default rx channel @@ -100,7 +100,7 @@ signal, or not. > phandle instead of the token. So you would have ... > > -> mmc1: mmc@13002000 { +> mmc1: mmc at 13002000 { > ... > // phandle + channel + enable/disable > dma_tx = <pdma0, 7, 1> // default tx channel diff --git a/a/content_digest b/N1/content_digest index 0b026e5..36386ce 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -6,21 +6,10 @@ "ref\0CAJe_ZhcrMycgOWf6EiGEjz25C1ZTkB1W=33Qqp4rFpcq-5QsDg@mail.gmail.com\0" "ref\04FB3A87C.1000000@ti.com\0" "ref\04FB3CF44.4040603@ti.com\0" - "From\0Stephen Warren <swarren@wwwdotorg.org>\0" - "Subject\0Re: [PATCH V3 1/2] of: Add generic device tree DMA helpers\0" + "From\0swarren@wwwdotorg.org (Stephen Warren)\0" + "Subject\0[PATCH V3 1/2] of: Add generic device tree DMA helpers\0" "Date\0Wed, 16 May 2012 10:15:16 -0600\0" - "To\0Jon Hunter <jon-hunter@ti.com>\0" - "Cc\0Jassi Brar <jaswinder.singh@linaro.org>" - Stephen Warren <swarren@nvidia.com> - Benoit Cousson <b-cousson@ti.com> - Arnd Bergmann <arnd@arndb.de> - device-tree <devicetree-discuss@lists.ozlabs.org> - Nicolas Ferre <nicolas.ferre@atmel.com> - Rob Herring <rob.herring@calxeda.com> - Grant Likely <grant.likely@secretlab.ca> - Russell King <linux@arm.linux.org.uk> - linux-omap <linux-omap@vger.kernel.org> - " linux-arm <linux-arm-kernel@lists.infradead.org>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On 05/16/2012 10:01 AM, Jon Hunter wrote:\n" @@ -38,7 +27,7 @@ "> \n" "> Take your example ...\n" "> \n" - "> mmc1: mmc@13002000 {\n" + "> mmc1: mmc at 13002000 {\n" "> ...\n" "> dma_tx = <891> //some platform-wide unique value\n" "> dma_rx = <927> //some platform-wide unique value\n" @@ -56,7 +45,7 @@ "\n" "> DMAC's Node:-\n" "> \n" - "> pdma2: pdma@10800000 {\n" + "> pdma2: pdma at 10800000 {\n" "> .......\n" "> \tdma_map = <891, 7>, // Map mmc1_tx onto i/f 7\n" "> \t\t <927, 8>, // Map mmc1_rx onto i/f 8\n" @@ -65,7 +54,7 @@ "\n" "So this would become:\n" "\n" - "pdma2: pdma@10800000 {\n" + "pdma2: pdma at 10800000 {\n" "\t.......\n" "\tdma-map =\n" "\t\t... entries for channels 0.. 6\n" @@ -81,7 +70,7 @@ "\n" "> But now I have another dmac which has the following options ...\n" "> \n" - "> pdma1: pdma@10000000 {\n" + "> pdma1: pdma at 10000000 {\n" "> .......\n" "> \tdma_map = <598, 2>, // Map mmc1_tx onto i/f 2\n" "> \t\t <230, 3>, // Map mmc1_rx onto i/f 3\n" @@ -90,7 +79,7 @@ "\n" "Which would become something very similar:\n" "\n" - "pdma1: pdma@10000000 {\n" + "pdma1: pdma at 10000000 {\n" "\t.......\n" "\tdma-map =\n" "\t\t... entries for channels 0.. 1\n" @@ -112,7 +101,7 @@ "> One way around this would be to have an enable/disable flag along with\n" "> the token such as ...\n" "> \n" - "> mmc1: mmc@13002000 {\n" + "> mmc1: mmc at 13002000 {\n" "> ...\n" "> dma_tx = <891, 1> // default tx channel\n" "> dma_rx = <927, 1> // default rx channel\n" @@ -125,7 +114,7 @@ "> phandle instead of the token. So you would have ...\n" "> \n" "> \n" - "> mmc1: mmc@13002000 {\n" + "> mmc1: mmc at 13002000 {\n" "> ...\n" "> \t\t// phandle + channel + enable/disable\n" "> dma_tx = <pdma0, 7, 1> // default tx channel\n" @@ -138,4 +127,4 @@ "> Then you could eliminate the random token and dma map from the dmac.\n" > Seems easier to read too. -b3ccff003ed0628f31dbc47295a2aa4680fa2ed5cecf15630ac7b6a8471d6714 +42f2e65336edc75d0547b81dd748fed13989410f093309bfa72f6703da239a3a
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.