diff for duplicates of <20150311162635.GZ5264@atomide.com> diff --git a/a/1.txt b/N1/1.txt index 505c4c7..fd85652 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -36,11 +36,11 @@ > >>>>> How about do something like this instead (untested): > >>>>> > >>>>> ocp { -> >>>>> l4_wkup: l4_wkup@44c00000 { +> >>>>> l4_wkup: l4_wkup at 44c00000 { > >>>>> compatible = "am335-l4-wkup", "simple-bus"; > >>>>> ranges = <0 0x44c00000 0x3fffff>; > >>>>> -> >>>>> wkup_m3: wkup_m3@44d00000 { +> >>>>> wkup_m3: wkup_m3 at 44d00000 { > >>>>> compatible = "ti,am3353-wkup-m3"; > >>>>> reg = <0x1000000 0x4000>, /* M3 UMEM */ > >>>>> <0x180000 0x2000>; /* M3 DMEM */ @@ -81,7 +81,7 @@ > Suman and I have been looking at this together, so I can comment here. An > implementation like this is what Suman is referring to: > -> + l4_wkup: l4_wkup@44c00000 { +> + l4_wkup: l4_wkup at 44c00000 { > + compatible = "am335-l4-wkup", "simple-bus"; > + #address-cells = <2>; > + #size-cells = <1>; @@ -89,7 +89,7 @@ > + <1 0x0 0x44d00000 0x4000>, > + <2 0x80000 0x44d80000 0x2000>; > + -> + wkup_m3: wkup_m3@1,0 { +> + wkup_m3: wkup_m3 at 1,0 { > + compatible = "ti,am3353-wkup-m3"; > + reg = <1 0x0 0x4000>, /* M3 UMEM */ > + <2 0x80000 0x2000>; /* M3 DMEM */ @@ -101,7 +101,7 @@ > + > > The of_* layer automatically translates everything so the pdata-quirks can still -> match based on wkup_m3@44d00000. The existing wkup_m3_rproc driver works almost +> match based on wkup_m3 at 44d00000. The existing wkup_m3_rproc driver works almost > entirely as is with this, all cpu addresses are read and mapped correctly but > the driver no longer will read the actual device addresses correctly which we > need for understanding where to load the firmware sections. diff --git a/a/content_digest b/N1/content_digest index 253ff94..c98c9ca 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -6,18 +6,10 @@ "ref\054FE33CA.4090709@ti.com\0" "ref\020150310160919.GQ5264@atomide.com\0" "ref\054FF4C32.5070106@ti.com\0" - "From\0Tony Lindgren <tony@atomide.com>\0" - "Subject\0Re: [PATCH v2 2/2] ARM: dts: am33xx: Move wkup_m3 node to soc node and add ranges\0" + "From\0tony@atomide.com (Tony Lindgren)\0" + "Subject\0[PATCH v2 2/2] ARM: dts: am33xx: Move wkup_m3 node to soc node and add ranges\0" "Date\0Wed, 11 Mar 2015 09:26:35 -0700\0" - "To\0Dave Gerlach <d-gerlach@ti.com>\0" - "Cc\0Suman Anna <s-anna@ti.com>" - linux-arm-kernel@lists.infradead.org - linux-kernel@vger.kernel.org - linux-omap@vger.kernel.org - devicetree@vger.kernel.org - Ohad Ben-Cohen <ohad@wizery.com> - Kevin Hilman <khilman@linaro.org> - " Felipe Balbi <balbi@ti.com>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "* Dave Gerlach <d-gerlach@ti.com> [150310 12:55]:\n" @@ -58,11 +50,11 @@ "> >>>>> How about do something like this instead (untested):\n" "> >>>>>\n" "> >>>>> ocp {\n" - "> >>>>> \tl4_wkup: l4_wkup@44c00000 {\n" + "> >>>>> \tl4_wkup: l4_wkup at 44c00000 {\n" "> >>>>> \t\tcompatible = \"am335-l4-wkup\", \"simple-bus\";\n" "> >>>>> \t\tranges = <0 0x44c00000 0x3fffff>;\n" "> >>>>>\n" - "> >>>>> \t\twkup_m3: wkup_m3@44d00000 {\n" + "> >>>>> \t\twkup_m3: wkup_m3 at 44d00000 {\n" "> >>>>> \t\t\tcompatible = \"ti,am3353-wkup-m3\";\n" "> >>>>> \t\t\treg = <0x1000000 0x4000>,\t/* M3 UMEM */\n" "> >>>>> \t\t\t <0x180000\t 0x2000>;\t/* M3 DMEM */\n" @@ -103,7 +95,7 @@ "> Suman and I have been looking at this together, so I can comment here. An\n" "> implementation like this is what Suman is referring to:\n" "> \n" - "> + l4_wkup: l4_wkup@44c00000 {\n" + "> + l4_wkup: l4_wkup at 44c00000 {\n" "> + compatible = \"am335-l4-wkup\", \"simple-bus\";\n" "> + #address-cells = <2>;\n" "> + #size-cells = <1>;\n" @@ -111,7 +103,7 @@ "> + <1 0x0 0x44d00000 0x4000>,\n" "> + <2 0x80000 0x44d80000 0x2000>;\n" "> +\n" - "> + wkup_m3: wkup_m3@1,0 {\n" + "> + wkup_m3: wkup_m3 at 1,0 {\n" "> + compatible = \"ti,am3353-wkup-m3\";\n" "> + reg = <1 0x0 0x4000>, /* M3 UMEM */\n" "> + <2 0x80000 0x2000>; /* M3 DMEM */\n" @@ -123,7 +115,7 @@ "> +\n" "> \n" "> The of_* layer automatically translates everything so the pdata-quirks can still\n" - "> match based on wkup_m3@44d00000. The existing wkup_m3_rproc driver works almost\n" + "> match based on wkup_m3 at 44d00000. The existing wkup_m3_rproc driver works almost\n" "> entirely as is with this, all cpu addresses are read and mapped correctly but\n" "> the driver no longer will read the actual device addresses correctly which we\n" "> need for understanding where to load the firmware sections.\n" @@ -147,4 +139,4 @@ "\n" Tony -73fec7484082c85ce58dc8aaa017c0981e52a62266d2dbc4b5ccdd8d2e5cebce +34a950fc7f459a51700c2a67e86ea35b1413c7a1ddd3503caf4354fa53394f6d
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.