aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/brcm2708
diff options
context:
space:
mode:
authorAnsuel Smith <ansuelsmth@gmail.com>2019-12-15 02:25:04 +0100
committerPetr Štetiar <ynezz@true.cz>2020-02-23 08:27:32 +0100
commitbc0ca20ca90e4d58090392c96b6d8d6405444268 (patch)
tree8da60dbb9ab3ffbc0b2db3fc9bf90535d0f94db5 /target/linux/brcm2708
parent191822b59f0e18fbe2e05a81be2586e33b040eb3 (diff)
downloadupstream-bc0ca20ca90e4d58090392c96b6d8d6405444268.tar.gz
upstream-bc0ca20ca90e4d58090392c96b6d8d6405444268.tar.bz2
upstream-bc0ca20ca90e4d58090392c96b6d8d6405444268.zip
ipq806x: fix bug in L2 cache scaling
It has been notice a buf in L2 cache scaling where the scaling is not done proprely if the frequency is set to the initial state before the new frequency. From: https://patchwork.kernel.org/patch/10565443/ * The clocks are set to aux clock rate first to make sure the * secondary mux is not sourcing off of QSB. The rate is then set to * two different rates to force a HFPLL reinit under all * circumstances. In the initial stage of boot to force a new frequency to apply, is needed to first set the frequency back to the lowest one (aux_rate) and then to the target one. This force and make sure the controller actually switch the frequency to the right one. Apply the same mechanism to L2 frequency scaling. Before scaling to the target frequency, first set the frequency to the aux_rate to force the transition, then scale it to the target frequency. Doing the wrong way can produce unexpected results and could lock the scaling mechanism until a full reboot is done (Causing a full reset by the krait-cc driver) From: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=77612720a2362230af726baa4149c40ec7a7fb05 When the Hfplls are reprogrammed during the rate change, the primary muxes which are sourced from the same hfpll for higher frequencies, needs to be switched to the 'safe secondary mux' as the parent for that small window. This is done by registering a clk notifier for the muxes and switching to the safe parent in the PRE_RATE_CHANGE notifier and back to the original parent in the POST_RATE_CHANGE notifier. This should apply also to L2 scaling... as we can't relly use the notifier, we manually do this on L2 scaling. Tested-By: Marc Benoit <marcb62185@gmail.com> [19.07: R7800] Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com> (cherry picked from commit 5ab9c0b388e9cf2537ef23d6e9baaf5730a14a1c)
Diffstat (limited to 'target/linux/brcm2708')
0 files changed, 0 insertions, 0 deletions