diff for duplicates of <56BD03F6.1050907@nvidia.com> diff --git a/a/1.txt b/N1/1.txt index 6588579..cbede82 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,19 +1,19 @@ On 2/11/2016 4:32 PM, Michael Turquette wrote: > Quoting Rhyland Klein (2016-02-10 10:34:16) ->> On 2/9/2016 9:56 PM, Emilio L=C3=B3pez wrote: +>> On 2/9/2016 9:56 PM, Emilio López wrote: >>> Hi, >>> ->>> El 09/02/16 a las 19:48, Rhyland Klein escribi=C3=B3: +>>> 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 +> > clk_disable_unused() handles the case where spurious clocks were left > enabled by the bootloader and need to be gated. This sounds like the > only thing you were after. ->=20 +> > We also have a case where clocks are gated by clk_disable_unused() > because no driver has claimed them yet, but we really want those clocks > to be left enabled. For example, clocks supplying DDR & CPU shouldn't be @@ -21,16 +21,15 @@ On 2/11/2016 4:32 PM, Michael Turquette wrote: > but your display controller module hasn't loaded yet. Cutting the clock > isn't fatal but causes unnecessary screen flicker because the module has > not loaded up. ->=20 +> > To solve those sets of problems there is the critical clocks and handoff > clocks thread[0]. ->=20 -> [0] http://lkml.kernel.org/r/<1455225554-13267-1-git-send-email-mturquett= -e@baylibre.com> ->=20 +> +> [0] http://lkml.kernel.org/r/<1455225554-13267-1-git-send-email-mturquette@baylibre.com> +> > Best regards, > Mike ->=20 +> Thanks. I agree the clk_disable_unused should clear up the situation I was in. And the critical clocks and handoff logic should be useful. I am @@ -38,5 +37,5 @@ sure we can make use of it once its in for Tegra support. -rhyland ---=20 +-- nvpublic diff --git a/a/content_digest b/N1/content_digest index dc52aa9..9e091bd 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -14,20 +14,20 @@ "b\0" "On 2/11/2016 4:32 PM, Michael Turquette wrote:\n" "> Quoting Rhyland Klein (2016-02-10 10:34:16)\n" - ">> On 2/9/2016 9:56 PM, Emilio L=C3=B3pez wrote:\n" + ">> On 2/9/2016 9:56 PM, Emilio L\303\263pez wrote:\n" ">>> Hi,\n" ">>>\n" - ">>> El 09/02/16 a las 19:48, Rhyland Klein escribi=C3=B3:\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" "...\n" - ">=20\n" + "> \n" "> clk_disable_unused() handles the case where spurious clocks were left\n" "> enabled by the bootloader and need to be gated. This sounds like the\n" "> only thing you were after.\n" - ">=20\n" + "> \n" "> We also have a case where clocks are gated by clk_disable_unused()\n" "> because no driver has claimed them yet, but we really want those clocks\n" "> to be left enabled. For example, clocks supplying DDR & CPU shouldn't be\n" @@ -35,16 +35,15 @@ "> but your display controller module hasn't loaded yet. Cutting the clock\n" "> isn't fatal but causes unnecessary screen flicker because the module has\n" "> not loaded up.\n" - ">=20\n" + "> \n" "> To solve those sets of problems there is the critical clocks and handoff\n" "> clocks thread[0].\n" - ">=20\n" - "> [0] http://lkml.kernel.org/r/<1455225554-13267-1-git-send-email-mturquett=\n" - "e@baylibre.com>\n" - ">=20\n" + "> \n" + "> [0] http://lkml.kernel.org/r/<1455225554-13267-1-git-send-email-mturquette@baylibre.com>\n" + "> \n" "> Best regards,\n" "> Mike\n" - ">=20\n" + "> \n" "\n" "Thanks. I agree the clk_disable_unused should clear up the situation I\n" "was in. And the critical clocks and handoff logic should be useful. I am\n" @@ -52,7 +51,7 @@ "\n" "-rhyland\n" "\n" - "--=20\n" + "-- \n" nvpublic -51ac0985019415598d68573c9e5392ac538165534e91405fef61a28425527bb9 +bc10762bc5ce99d3f489c7e87be83c6d7292d9eacf08e4e30301712e89104b45
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.