diff for duplicates of <6675833.8DAAvDYooL@diego> diff --git a/a/1.txt b/N1/1.txt index 3f3fe50..13efc57 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,36 +1,27 @@ Am Montag, 14. September 2015, 15:19:21 schrieb Mark Rutland: -> On Sun, Sep 13, 2015 at 12:20:36PM +0100, Heiko St=FCbner wrote: +> On Sun, Sep 13, 2015 at 12:20:36PM +0100, Heiko Stübner wrote: > > Again a result of the gpio-clock-liberation the rk3368 needs the > > pclk_pd_pmu marked as critical, to boot successfully. -> >=20 +> > > > Reported-by: Mark Rutland <mark.rutland@arm.com> > > Signed-off-by: Heiko Stuebner <heiko@sntech.de> ->=20 +> > FWIW: Tested-by: Mark Rutland <mark.rutland@arm.com> ->=20 -> I'm surprised that we don't describe these as critical in the DT, giv= -en -> that this isn't really an internal property of the clock controller, = -but +> +> I'm surprised that we don't describe these as critical in the DT, given +> that this isn't really an internal property of the clock controller, but > rather what happens to be attached to it. That ship appears to have > sailed, however. -I wouldn't necessarily think so ... what is called critical only means = -"don't=20 +I wouldn't necessarily think so ... what is called critical only means "don't turn off when walking the clock-tree upwards". -The pclk_pd_pmu for example simply supplies some more clocks we don't h= -andle=20 -at all currently (pclk_pmu_noc, ...). That we currently choose to ignor= -e those=20 -[because we don't have any code nor dt-bindings to handle the component= -s=20 -supplied] sounds very much like an implementation-specific detail, not=20= - +The pclk_pd_pmu for example simply supplies some more clocks we don't handle +at all currently (pclk_pmu_noc, ...). That we currently choose to ignore those +[because we don't have any code nor dt-bindings to handle the components +supplied] sounds very much like an implementation-specific detail, not something about the hardware. -I really like the concept of critical clock handling Mike is working on= -, which=20 -implements some sort of hand-off and keeps so marked clocks on until a = -real=20 +I really like the concept of critical clock handling Mike is working on, which +implements some sort of hand-off and keeps so marked clocks on until a real components picks them up. diff --git a/a/content_digest b/N1/content_digest index 4fc3559..1f222d8 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -12,40 +12,31 @@ "\00:1\0" "b\0" "Am Montag, 14. September 2015, 15:19:21 schrieb Mark Rutland:\n" - "> On Sun, Sep 13, 2015 at 12:20:36PM +0100, Heiko St=FCbner wrote:\n" + "> On Sun, Sep 13, 2015 at 12:20:36PM +0100, Heiko St\303\274bner wrote:\n" "> > Again a result of the gpio-clock-liberation the rk3368 needs the\n" "> > pclk_pd_pmu marked as critical, to boot successfully.\n" - "> >=20\n" + "> > \n" "> > Reported-by: Mark Rutland <mark.rutland@arm.com>\n" "> > Signed-off-by: Heiko Stuebner <heiko@sntech.de>\n" - ">=20\n" + "> \n" "> FWIW: Tested-by: Mark Rutland <mark.rutland@arm.com>\n" - ">=20\n" - "> I'm surprised that we don't describe these as critical in the DT, giv=\n" - "en\n" - "> that this isn't really an internal property of the clock controller, =\n" - "but\n" + "> \n" + "> I'm surprised that we don't describe these as critical in the DT, given\n" + "> that this isn't really an internal property of the clock controller, but\n" "> rather what happens to be attached to it. That ship appears to have\n" "> sailed, however.\n" "\n" - "I wouldn't necessarily think so ... what is called critical only means =\n" - "\"don't=20\n" + "I wouldn't necessarily think so ... what is called critical only means \"don't \n" "turn off when walking the clock-tree upwards\".\n" "\n" - "The pclk_pd_pmu for example simply supplies some more clocks we don't h=\n" - "andle=20\n" - "at all currently (pclk_pmu_noc, ...). That we currently choose to ignor=\n" - "e those=20\n" - "[because we don't have any code nor dt-bindings to handle the component=\n" - "s=20\n" - "supplied] sounds very much like an implementation-specific detail, not=20=\n" - "\n" + "The pclk_pd_pmu for example simply supplies some more clocks we don't handle \n" + "at all currently (pclk_pmu_noc, ...). That we currently choose to ignore those \n" + "[because we don't have any code nor dt-bindings to handle the components \n" + "supplied] sounds very much like an implementation-specific detail, not \n" "something about the hardware.\n" "\n" - "I really like the concept of critical clock handling Mike is working on=\n" - ", which=20\n" - "implements some sort of hand-off and keeps so marked clocks on until a =\n" - "real=20\n" + "I really like the concept of critical clock handling Mike is working on, which \n" + "implements some sort of hand-off and keeps so marked clocks on until a real \n" components picks them up. -ace5ee6ace2b4d9fdaac784777379667d5579fb0fc1adf0e633f998744f2d3e0 +6ee8303ef63e096f2a4948f387979be542b2700f4c9c8af3dc20e5e00c8d363e
diff --git a/a/1.txt b/N2/1.txt index 3f3fe50..2e6f67a 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,36 +1,27 @@ Am Montag, 14. September 2015, 15:19:21 schrieb Mark Rutland: -> On Sun, Sep 13, 2015 at 12:20:36PM +0100, Heiko St=FCbner wrote: +> On Sun, Sep 13, 2015 at 12:20:36PM +0100, Heiko St?bner wrote: > > Again a result of the gpio-clock-liberation the rk3368 needs the > > pclk_pd_pmu marked as critical, to boot successfully. -> >=20 +> > > > Reported-by: Mark Rutland <mark.rutland@arm.com> > > Signed-off-by: Heiko Stuebner <heiko@sntech.de> ->=20 +> > FWIW: Tested-by: Mark Rutland <mark.rutland@arm.com> ->=20 -> I'm surprised that we don't describe these as critical in the DT, giv= -en -> that this isn't really an internal property of the clock controller, = -but +> +> I'm surprised that we don't describe these as critical in the DT, given +> that this isn't really an internal property of the clock controller, but > rather what happens to be attached to it. That ship appears to have > sailed, however. -I wouldn't necessarily think so ... what is called critical only means = -"don't=20 +I wouldn't necessarily think so ... what is called critical only means "don't turn off when walking the clock-tree upwards". -The pclk_pd_pmu for example simply supplies some more clocks we don't h= -andle=20 -at all currently (pclk_pmu_noc, ...). That we currently choose to ignor= -e those=20 -[because we don't have any code nor dt-bindings to handle the component= -s=20 -supplied] sounds very much like an implementation-specific detail, not=20= - +The pclk_pd_pmu for example simply supplies some more clocks we don't handle +at all currently (pclk_pmu_noc, ...). That we currently choose to ignore those +[because we don't have any code nor dt-bindings to handle the components +supplied] sounds very much like an implementation-specific detail, not something about the hardware. -I really like the concept of critical clock handling Mike is working on= -, which=20 -implements some sort of hand-off and keeps so marked clocks on until a = -real=20 +I really like the concept of critical clock handling Mike is working on, which +implements some sort of hand-off and keeps so marked clocks on until a real components picks them up. diff --git a/a/content_digest b/N2/content_digest index 4fc3559..b6e4324 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,51 +1,37 @@ "ref\05267432.TORlj1Iv40@diego\0" "ref\020150914141920.GF7002@leverpostej\0" - "From\0Heiko St\303\274bner <heiko@sntech.de>\0" - "Subject\0Re: [PATCH] clk: rockchip: add critical clock for rk3368\0" + "From\0heiko@sntech.de (Heiko St\303\274bner)\0" + "Subject\0[PATCH] clk: rockchip: add critical clock for rk3368\0" "Date\0Mon, 14 Sep 2015 17:06:05 +0200\0" - "To\0Mark Rutland <mark.rutland@arm.com>\0" - "Cc\0mturquette@baylibre.com <mturquette@baylibre.com>" - sboyd@codeaurora.org <sboyd@codeaurora.org> - linux-clk@vger.kernel.org <linux-clk@vger.kernel.org> - linux-rockchip@lists.infradead.org <linux-rockchip@lists.infradead.org> - " linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "Am Montag, 14. September 2015, 15:19:21 schrieb Mark Rutland:\n" - "> On Sun, Sep 13, 2015 at 12:20:36PM +0100, Heiko St=FCbner wrote:\n" + "> On Sun, Sep 13, 2015 at 12:20:36PM +0100, Heiko St?bner wrote:\n" "> > Again a result of the gpio-clock-liberation the rk3368 needs the\n" "> > pclk_pd_pmu marked as critical, to boot successfully.\n" - "> >=20\n" + "> > \n" "> > Reported-by: Mark Rutland <mark.rutland@arm.com>\n" "> > Signed-off-by: Heiko Stuebner <heiko@sntech.de>\n" - ">=20\n" + "> \n" "> FWIW: Tested-by: Mark Rutland <mark.rutland@arm.com>\n" - ">=20\n" - "> I'm surprised that we don't describe these as critical in the DT, giv=\n" - "en\n" - "> that this isn't really an internal property of the clock controller, =\n" - "but\n" + "> \n" + "> I'm surprised that we don't describe these as critical in the DT, given\n" + "> that this isn't really an internal property of the clock controller, but\n" "> rather what happens to be attached to it. That ship appears to have\n" "> sailed, however.\n" "\n" - "I wouldn't necessarily think so ... what is called critical only means =\n" - "\"don't=20\n" + "I wouldn't necessarily think so ... what is called critical only means \"don't \n" "turn off when walking the clock-tree upwards\".\n" "\n" - "The pclk_pd_pmu for example simply supplies some more clocks we don't h=\n" - "andle=20\n" - "at all currently (pclk_pmu_noc, ...). That we currently choose to ignor=\n" - "e those=20\n" - "[because we don't have any code nor dt-bindings to handle the component=\n" - "s=20\n" - "supplied] sounds very much like an implementation-specific detail, not=20=\n" - "\n" + "The pclk_pd_pmu for example simply supplies some more clocks we don't handle \n" + "at all currently (pclk_pmu_noc, ...). That we currently choose to ignore those \n" + "[because we don't have any code nor dt-bindings to handle the components \n" + "supplied] sounds very much like an implementation-specific detail, not \n" "something about the hardware.\n" "\n" - "I really like the concept of critical clock handling Mike is working on=\n" - ", which=20\n" - "implements some sort of hand-off and keeps so marked clocks on until a =\n" - "real=20\n" + "I really like the concept of critical clock handling Mike is working on, which \n" + "implements some sort of hand-off and keeps so marked clocks on until a real \n" components picks them up. -ace5ee6ace2b4d9fdaac784777379667d5579fb0fc1adf0e633f998744f2d3e0 +2b7303747f24cc775b1a502db1cca6eae19acba85014c75faa1d21400aa7dca0
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.