diff for duplicates of <20150311173212.GC5264@atomide.com> diff --git a/a/1.txt b/N1/1.txt index 2c98de5..5ed8c58 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -4,7 +4,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>; @@ -21,7 +21,7 @@ > and the M3 DMEM entry below will be adjusted as <1 0x80000 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 */ @@ -33,7 +33,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 fc12796..41ad884 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -8,18 +8,10 @@ "ref\054FF4C32.5070106@ti.com\0" "ref\020150311162635.GZ5264@atomide.com\0" "ref\0550078D5.7080700@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 10:32:13 -0700\0" - "To\0Suman Anna <s-anna@ti.com>\0" - "Cc\0Dave Gerlach <d-gerlach@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" "* Suman Anna <s-anna@ti.com> [150311 10:18]:\n" @@ -28,7 +20,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" @@ -45,7 +37,7 @@ "> and the M3 DMEM entry below will be adjusted as <1 0x80000 0x2000>.\n" "> \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" @@ -57,7 +49,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" @@ -92,4 +84,4 @@ "\n" Tony -76065353cfc0e5a169c9d7c038d4a925e6aeda334557b4d5e20c4da9dfcf2724 +955ac716d4c2cee330716ba8a935aa9252a16c04118b0bd2bc804978d768fa7c
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.