diff for duplicates of <525C063C.9080908@ti.com> diff --git a/a/1.txt b/N1/1.txt index 27514bc..459abcb 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -16,17 +16,17 @@ On 10/14/2013 02:45 AM, Paul Walmsley wrote: > > /ocp { > -> prm@4a306000 { +> prm at 4a306000 { > compatible = xxx; > regs = <0x4a306000 xxxx>; > }; > -> cm1@4a004000 { +> cm1 at 4a004000 { > compatible = xxx; > regs = <0x4a004000 xxxx>; > }; > -> cm2@4a008000 { +> cm2 at 4a008000 { > compatible = xxx; > regs = <0x4a008000 xxxx>; > }; @@ -42,10 +42,10 @@ On 10/14/2013 02:45 AM, Paul Walmsley wrote: > would belong to the "cm1" device, since that's where its control registers > are located. Something like this: > -> cm1@4a004000 { +> cm1 at 4a004000 { > ... > clocks { -> dpll_per_ck@.... { +> dpll_per_ck at .... { > <clock data goes here> > }; > }; @@ -90,10 +90,10 @@ On 10/14/2013 02:45 AM, Paul Walmsley wrote: > 4. Use relative register offsets from the top of the containing IP block's > base address, rather than absolute addresses. > -> cm1@4a004000 { +> cm1 at 4a004000 { > ... > clocks { -> dpll_per_ck@4140 { +> dpll_per_ck at 4140 { > <clock data goes here> > }; > }; @@ -121,14 +121,14 @@ clock. > IP block that contains them: > > -> cm1@4a004000 { +> cm1 at 4a004000 { > ... > clocks { > ... > }; > > clockdomains { -> l3_init_clkdm: l3_init_clkdm@... { +> l3_init_clkdm: l3_init_clkdm at ... { > ... > }; > }; @@ -171,7 +171,7 @@ than to try to introduce multiple new drivers with a single set. > A. It seems pretty odd and unnecessarily obscure to do something like > this: > -> dpll_usb_ck: dpll_usb_ck@... { +> dpll_usb_ck: dpll_usb_ck at ... { > ... > reg = <0x4a008180 0x4>, <0x4a008184 0x4>, <0x4a008188 0x4>, <0x4a00818c 0x4>; > ... @@ -179,7 +179,7 @@ than to try to introduce multiple new drivers with a single set. > > It's at least self-documenting to do something like this: > -> dpll_usb_ck: dpll_usb_ck@... { +> dpll_usb_ck: dpll_usb_ck at ... { > ... > control-reg = < ... >; > idlest-reg = < ... >; diff --git a/a/content_digest b/N1/content_digest index f30e22f..ebd0442 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -12,22 +12,10 @@ "ref\0alpine.DEB.2.02.1310112226130.27397@utopia.booyaka.com\0" "ref\0525923AB.4030807@ti.com\0" "ref\0alpine.DEB.2.02.1310132023240.27397@utopia.booyaka.com\0" - "From\0Tero Kristo <t-kristo@ti.com>\0" - "Subject\0Re: [PATCHv7 00/36] ARM: OMAP: clock data conversion to DT\0" + "From\0t-kristo@ti.com (Tero Kristo)\0" + "Subject\0[PATCHv7 00/36] ARM: OMAP: clock data conversion to DT\0" "Date\0Mon, 14 Oct 2013 17:57:00 +0300\0" - "To\0Paul Walmsley <paul@pwsan.com>\0" - "Cc\0devicetree@vger.kernel.org" - Tony Lindgren <tony@atomide.com> - mturquette@linaro.org - linux-omap@vger.kernel.org - nm@ti.com - khilman@linaro.org - pdeschrijver@nvidia.com - rnayak@ti.com - bcousson@baylibre.com - linux-arm-kernel@lists.infradead.org - swarren@nvidia.com - " mark.rutland@arm.com\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "Hi Paul,\n" @@ -48,17 +36,17 @@ ">\n" "> /ocp {\n" ">\n" - "> prm@4a306000 {\n" + "> prm at 4a306000 {\n" "> \tcompatible = xxx;\n" "> \tregs = <0x4a306000 xxxx>;\n" "> };\n" ">\n" - "> cm1@4a004000 {\n" + "> cm1 at 4a004000 {\n" "> \tcompatible = xxx;\n" "> \tregs = <0x4a004000 xxxx>;\n" "> };\n" ">\n" - "> cm2@4a008000 {\n" + "> cm2 at 4a008000 {\n" "> \tcompatible = xxx;\n" "> \tregs = <0x4a008000 xxxx>;\n" "> };\n" @@ -74,10 +62,10 @@ "> would belong to the \"cm1\" device, since that's where its control registers\n" "> are located. Something like this:\n" ">\n" - "> cm1@4a004000 {\n" + "> cm1 at 4a004000 {\n" "> ...\n" "> clocks {\n" - "> dpll_per_ck@.... {\n" + "> dpll_per_ck at .... {\n" "> \t\t<clock data goes here>\n" "> };\n" "> };\n" @@ -122,10 +110,10 @@ "> 4. Use relative register offsets from the top of the containing IP block's\n" "> base address, rather than absolute addresses.\n" ">\n" - "> cm1@4a004000 {\n" + "> cm1 at 4a004000 {\n" "> ...\n" "> clocks {\n" - "> dpll_per_ck@4140 {\n" + "> dpll_per_ck at 4140 {\n" "> <clock data goes here>\n" "> };\n" "> };\n" @@ -153,14 +141,14 @@ "> IP block that contains them:\n" ">\n" ">\n" - "> cm1@4a004000 {\n" + "> cm1 at 4a004000 {\n" "> ...\n" "> clocks {\n" "> \t ...\n" "> };\n" ">\n" "> clockdomains {\n" - "> l3_init_clkdm: l3_init_clkdm@... {\n" + "> l3_init_clkdm: l3_init_clkdm at ... {\n" "> ...\n" "> };\n" "> };\n" @@ -203,7 +191,7 @@ "> A. It seems pretty odd and unnecessarily obscure to do something like\n" "> this:\n" ">\n" - "> dpll_usb_ck: dpll_usb_ck@... {\n" + "> dpll_usb_ck: dpll_usb_ck at ... {\n" "> ...\n" "> reg = <0x4a008180 0x4>, <0x4a008184 0x4>, <0x4a008188 0x4>, <0x4a00818c 0x4>;\n" "> ...\n" @@ -211,7 +199,7 @@ " >\n" "> It's at least self-documenting to do something like this:\n" ">\n" - "> dpll_usb_ck: dpll_usb_ck@... {\n" + "> dpll_usb_ck: dpll_usb_ck at ... {\n" "> ...\n" "> control-reg = < ... >;\n" "> idlest-reg = < ... >;\n" @@ -256,4 +244,4 @@ "\n" -Tero -232ca7f337e05608668c24f4a32381de2b723628141641f7fce3e417aea18d1d +7caecb85e7ddee38717084a75080f508f1e178ea346c0167060c91620ea8d810
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.