sys-clks logic is simple:
sys-clk sees user configured vals, sys-clk sees missmatching vals, sys-clk applies.
Every clock that differs from the designated profile must be changed, by design.
We considered logic for boost mode and came to the conclusion that it simply doesn't fit into sys-clks design concept.
The whole point is to give the user full authority over the clocks (within gpu limitations) at any given point in time.
This also applies to boost mode in its entirety, so it needs to be changed when the system applies it.
sys-clk sees user configured vals, sys-clk sees missmatching vals, sys-clk applies.
Every clock that differs from the designated profile must be changed, by design.
We considered logic for boost mode and came to the conclusion that it simply doesn't fit into sys-clks design concept.
The whole point is to give the user full authority over the clocks (within gpu limitations) at any given point in time.
This also applies to boost mode in its entirety, so it needs to be changed when the system applies it.
