diff for duplicates of <52D1FB94.1030006@gmail.com> diff --git a/a/1.txt b/N1/1.txt index 86b4748..9c733d8 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -112,18 +112,18 @@ inside clock ops. >>>>> + >>>> >>>> What do you think about adding those parameters (like CPU dividers) ->>>> as an attribute to /cpus/cpu@0 node? +>>>> as an attribute to /cpus/cpu at 0 node? >>> >>> Not in CPU node but may be in clock controller node since these values >>> are actually used by the clock controller. >> ->> /cpus/cpu@0 seems like a good place for them (since those DIVs are +>> /cpus/cpu at 0 seems like a good place for them (since those DIVs are >> related to core) > > DIVs belong to the clock controller, not the CPU, and are addressed > from the clock controller address space. -I also think that the contents of cpu@0 node should be limited only to +I also think that the contents of cpu at 0 node should be limited only to CPU specific data. Personally I don't even like the idea of having operating points there - I would rather see frequency limits there, i.e. maximum frequency allowed at given voltage; specific frequency values diff --git a/a/content_digest b/N1/content_digest index 96e843f..5e9d903 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,21 +4,10 @@ "ref\0CAJuA9aidWvkPPXFfOysqQCQ4d7q_y51zbYxHCK9d-E8+ojfN_w@mail.gmail.com\0" "ref\020140110151812.5104cc92@amdc2363\0" "ref\0CAJuA9aj3ca9VNsQ9cadVH8pUpyYeaht3DufT3DW4jXuEN5BudA@mail.gmail.com\0" - "From\0Tomasz Figa <tomasz.figa@gmail.com>\0" - "Subject\0Re: [PATCH 3/6] clk: samsung: register cpu clock provider for exynos4210 SoC\0" + "From\0tomasz.figa@gmail.com (Tomasz Figa)\0" + "Subject\0[PATCH 3/6] clk: samsung: register cpu clock provider for exynos4210 SoC\0" "Date\0Sun, 12 Jan 2014 03:19:00 +0100\0" - "To\0Thomas Abraham <ta.omasab@gmail.com>" - " Lukasz Majewski <l.majewski@samsung.com>\0" - "Cc\0linux-samsung-soc@vger.kernel.org" - cpufreq@vger.kernel.org - devicetree@vger.kernel.org - linux-arm-kernel@lists.infradead.org - t.figa@samsung.com - kgene.kim@samsung.com - Viresh Kumar <viresh.kumar@linaro.org> - Shawn Guo <shawn.guo@linaro.org> - thomas.ab@samsung.com - " Lukasz Majewski <l.majewski@majess.pl>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On 11.01.2014 06:25, Thomas Abraham wrote:\n" @@ -135,18 +124,18 @@ ">>>>> +\n" ">>>>\n" ">>>> What do you think about adding those parameters (like CPU dividers)\n" - ">>>> as an attribute to /cpus/cpu@0 node?\n" + ">>>> as an attribute to /cpus/cpu at 0 node?\n" ">>>\n" ">>> Not in CPU node but may be in clock controller node since these values\n" ">>> are actually used by the clock controller.\n" ">>\n" - ">> /cpus/cpu@0 seems like a good place for them (since those DIVs are\n" + ">> /cpus/cpu at 0 seems like a good place for them (since those DIVs are\n" ">> related to core)\n" ">\n" "> DIVs belong to the clock controller, not the CPU, and are addressed\n" "> from the clock controller address space.\n" "\n" - "I also think that the contents of cpu@0 node should be limited only to \n" + "I also think that the contents of cpu at 0 node should be limited only to \n" "CPU specific data. Personally I don't even like the idea of having \n" "operating points there - I would rather see frequency limits there, i.e. \n" "maximum frequency allowed at given voltage; specific frequency values \n" @@ -386,4 +375,4 @@ "Best regards,\n" Tomasz -89ebd117365186972ee5d3ace6ed0e5572bc838496c5d7e277e6f18c048ff8d4 +566dcaa5494b850e31cebb5d642492f4017e6af5c536a9745fb180f51d9aa9df
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.