diff for duplicates of <56BB82A8.8010701@nvidia.com> diff --git a/a/1.txt b/N1/1.txt index 243c0ad..5badf7a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,12 +1,12 @@ -On 2/9/2016 9:56 PM, Emilio L=F3pez wrote: +On 2/9/2016 9:56 PM, Emilio López wrote: > Hi, ->=20 -> El 09/02/16 a las 19:48, Rhyland Klein escribi=F3: +> +> El 09/02/16 a las 19:48, Rhyland Klein escribió: >> When clocks are registered, they could be enabled already in >> hardware. As of now, the enable count will start at 0. When this >> happens, it means a clock is enabled and the framework doesn't know >> that, so it will always report it as disabled. ->=20 +> > Keep in mind that during the boot process, towards the end, unused > clocks get disabled, so the state remains in sync. If suddenly the > enable_count on unused clocks is not 0, this will break and unused @@ -16,9 +16,9 @@ Hmm, I had misread the logic in clk_disable_unused_subtree(), namely I inverted the check on enable_count when I was looking at it. It does seem like it would take care of the clocks I was referring to. ->=20 +> > http://lxr.free-electrons.com/source/drivers/clk/clk.c#L244 ->=20 +> > What issue were you having that prompted you to write this patch? I ran into the situation where a peripheral clock was enabled before the @@ -37,5 +37,5 @@ Thanks. -rhyland ---=20 +-- nvpublic diff --git a/a/content_digest b/N1/content_digest index a586476..c5838c8 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -10,15 +10,15 @@ " <linux-kernel@vger.kernel.org>\0" "\00:1\0" "b\0" - "On 2/9/2016 9:56 PM, Emilio L=F3pez wrote:\n" + "On 2/9/2016 9:56 PM, Emilio L\303\263pez wrote:\n" "> Hi,\n" - ">=20\n" - "> El 09/02/16 a las 19:48, Rhyland Klein escribi=F3:\n" + "> \n" + "> El 09/02/16 a las 19:48, Rhyland Klein escribi\303\263:\n" ">> When clocks are registered, they could be enabled already in\n" ">> hardware. As of now, the enable count will start at 0. When this\n" ">> happens, it means a clock is enabled and the framework doesn't know\n" ">> that, so it will always report it as disabled.\n" - ">=20\n" + "> \n" "> Keep in mind that during the boot process, towards the end, unused\n" "> clocks get disabled, so the state remains in sync. If suddenly the\n" "> enable_count on unused clocks is not 0, this will break and unused\n" @@ -28,9 +28,9 @@ "inverted the check on enable_count when I was looking at it. It does\n" "seem like it would take care of the clocks I was referring to.\n" "\n" - ">=20\n" + "> \n" "> http://lxr.free-electrons.com/source/drivers/clk/clk.c#L244\n" - ">=20\n" + "> \n" "> What issue were you having that prompted you to write this patch?\n" "\n" "I ran into the situation where a peripheral clock was enabled before the\n" @@ -49,7 +49,7 @@ "-rhyland\n" "\n" "\n" - "--=20\n" + "-- \n" nvpublic -8f849acd51b6e18a7e6c0717248c8390b84ccbdfc3d881f29f08c1b8712d8f1b +9e485c3740a7af581b73e831847704fe9370a88321feda69ec4744f3e6457367
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.