On 21/03/16 18:16, Karol Herbst wrote:
this function just forces a reclock. This makes sense if some cstates get
(un)available and we have to adjust to that.
This can happen for various reasons:
* temperature changes
* user changes boost mode
Signed-off-by: Karol Herbst <nouv...@karolherbst.de>
You can also add one event:
* The load changes
In the end, the dyn. reclocking will generate a target pstate/cstate
which will be applied as well as possible. With this in mind, we could
rename this function nvkm_clk_update(<no param>). Reclock is a weird
name, but so is update.
Pick whatever you want!
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
