diff for duplicates of <53342E64.5060505@samsung.com> diff --git a/a/1.txt b/N1/1.txt index 1478104..bfb4cf0 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -6,7 +6,7 @@ On 27/03/14 14:24, Laurent Pinchart wrote: >> as specified in clock-parents, clock-rates DT properties for a consumer >> device and a call to it before driver is bound to a device. >> ->> Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com> +>> Signed-off-by: Sylwester Nawrocki <s.nawrocki-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org> >> --- [...] >> --- @@ -39,7 +39,7 @@ On 27/03/14 14:24, Laurent Pinchart wrote: >> +a list of parent clocks in form of phandle and clock specifier pairs, the >> +latter the list of assigned clock frequency values (one cell each). >> + ->> + uart at a000 { +>> + uart@a000 { >> + compatible = "fsl,imx-uart"; >> + reg = <0xa000 0x1000>; >> + ... @@ -59,7 +59,7 @@ On 27/03/14 14:24, Laurent Pinchart wrote: > for instance, who should win ? Shouldn't a warning be printed ? In general, the assumption is that the <&clkcon 3> clock would be used only -by the uart at a000 device. If a clock is shared I'd say it shouldn't be put +by the uart@a000 device. If a clock is shared I'd say it shouldn't be put in a multiple consumer device nodes. Instead it should be put in a clock provider node, as I was trying to explain in the sentence below. @@ -99,3 +99,7 @@ Naturally it's this just an RFC, any critics or suggestions are welcome.:) -- Regards, Sylwester +-- +To unsubscribe from this list: send the line "unsubscribe devicetree" in +the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 35068ca..c61baa4 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,10 +1,24 @@ "ref\01395922579-28547-1-git-send-email-s.nawrocki@samsung.com\0" "ref\01395922579-28547-3-git-send-email-s.nawrocki@samsung.com\0" "ref\077553409.zvN7VkNGe7@avalon\0" - "From\0s.nawrocki@samsung.com (Sylwester Nawrocki)\0" - "Subject\0[PATCH RFC v3 2/2] clk: Add handling of clk parent and rate assigned from DT\0" + "From\0Sylwester Nawrocki <s.nawrocki-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>\0" + "Subject\0Re: [PATCH RFC v3 2/2] clk: Add handling of clk parent and rate assigned from DT\0" "Date\0Thu, 27 Mar 2014 14:57:56 +0100\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Laurent Pinchart <laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>" + " linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org\0" + "Cc\0mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org" + mark.rutland-5wv7dgnIgG8@public.gmane.org + devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org + gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org + t.figa-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org + sw0312.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org + linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org + robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org + galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org + grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org + " m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org\0" "\00:1\0" "b\0" "Hi Laurent,\n" @@ -15,7 +29,7 @@ ">> as specified in clock-parents, clock-rates DT properties for a consumer\n" ">> device and a call to it before driver is bound to a device.\n" ">>\n" - ">> Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>\n" + ">> Signed-off-by: Sylwester Nawrocki <s.nawrocki-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>\n" ">> ---\n" "[...]\n" ">> ---\n" @@ -48,7 +62,7 @@ ">> +a list of parent clocks in form of phandle and clock specifier pairs, the\n" ">> +latter the list of assigned clock frequency values (one cell each).\n" ">> +\n" - ">> + uart at a000 {\n" + ">> + uart@a000 {\n" ">> + compatible = \"fsl,imx-uart\";\n" ">> + reg = <0xa000 0x1000>;\n" ">> + ...\n" @@ -68,7 +82,7 @@ "> for instance, who should win ? Shouldn't a warning be printed ?\n" "\n" "In general, the assumption is that the <&clkcon 3> clock would be used only\n" - "by the uart at a000 device. If a clock is shared I'd say it shouldn't be put\n" + "by the uart@a000 device. If a clock is shared I'd say it shouldn't be put\n" "in a multiple consumer device nodes. Instead it should be put in a clock\n" "provider node, as I was trying to explain in the sentence below.\n" "\n" @@ -107,6 +121,10 @@ "\n" "--\n" "Regards,\n" - Sylwester + "Sylwester\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe devicetree\" in\n" + "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -8c2537cfb5d643c274c2e8e554ef4b4d2e3f0d6390e55908df59e4b6a9e8e691 +f931ae7534edff45091889ff97605c40857e0491d81757c90fe6a99b52feba24
diff --git a/a/1.txt b/N2/1.txt index 1478104..e1ca27e 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -39,7 +39,7 @@ On 27/03/14 14:24, Laurent Pinchart wrote: >> +a list of parent clocks in form of phandle and clock specifier pairs, the >> +latter the list of assigned clock frequency values (one cell each). >> + ->> + uart at a000 { +>> + uart@a000 { >> + compatible = "fsl,imx-uart"; >> + reg = <0xa000 0x1000>; >> + ... @@ -59,7 +59,7 @@ On 27/03/14 14:24, Laurent Pinchart wrote: > for instance, who should win ? Shouldn't a warning be printed ? In general, the assumption is that the <&clkcon 3> clock would be used only -by the uart at a000 device. If a clock is shared I'd say it shouldn't be put +by the uart@a000 device. If a clock is shared I'd say it shouldn't be put in a multiple consumer device nodes. Instead it should be put in a clock provider node, as I was trying to explain in the sentence below. diff --git a/a/content_digest b/N2/content_digest index 35068ca..b42c64d 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,10 +1,24 @@ "ref\01395922579-28547-1-git-send-email-s.nawrocki@samsung.com\0" "ref\01395922579-28547-3-git-send-email-s.nawrocki@samsung.com\0" "ref\077553409.zvN7VkNGe7@avalon\0" - "From\0s.nawrocki@samsung.com (Sylwester Nawrocki)\0" - "Subject\0[PATCH RFC v3 2/2] clk: Add handling of clk parent and rate assigned from DT\0" + "From\0Sylwester Nawrocki <s.nawrocki@samsung.com>\0" + "Subject\0Re: [PATCH RFC v3 2/2] clk: Add handling of clk parent and rate assigned from DT\0" "Date\0Thu, 27 Mar 2014 14:57:56 +0100\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Laurent Pinchart <laurent.pinchart@ideasonboard.com>" + " linux-arm-kernel@lists.infradead.org\0" + "Cc\0mturquette@linaro.org" + mark.rutland@arm.com + devicetree@vger.kernel.org + linux@arm.linux.org.uk + gregkh@linuxfoundation.org + t.figa@samsung.com + sw0312.kim@samsung.com + linux-kernel@vger.kernel.org + kyungmin.park@samsung.com + robh+dt@kernel.org + galak@codeaurora.org + grant.likely@linaro.org + " m.szyprowski@samsung.com\0" "\00:1\0" "b\0" "Hi Laurent,\n" @@ -48,7 +62,7 @@ ">> +a list of parent clocks in form of phandle and clock specifier pairs, the\n" ">> +latter the list of assigned clock frequency values (one cell each).\n" ">> +\n" - ">> + uart at a000 {\n" + ">> + uart@a000 {\n" ">> + compatible = \"fsl,imx-uart\";\n" ">> + reg = <0xa000 0x1000>;\n" ">> + ...\n" @@ -68,7 +82,7 @@ "> for instance, who should win ? Shouldn't a warning be printed ?\n" "\n" "In general, the assumption is that the <&clkcon 3> clock would be used only\n" - "by the uart at a000 device. If a clock is shared I'd say it shouldn't be put\n" + "by the uart@a000 device. If a clock is shared I'd say it shouldn't be put\n" "in a multiple consumer device nodes. Instead it should be put in a clock\n" "provider node, as I was trying to explain in the sentence below.\n" "\n" @@ -109,4 +123,4 @@ "Regards,\n" Sylwester -8c2537cfb5d643c274c2e8e554ef4b4d2e3f0d6390e55908df59e4b6a9e8e691 +f0c56abf2cfc02fd4a5203e568e23cbe8e42efc2213a957ebdf719dfe07941c8
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.