diff options
author | Maxime Ripard <maxime@cerno.tech> | 2022-03-25 17:11:43 +0100 |
---|---|---|
committer | Stephen Boyd <sboyd@kernel.org> | 2022-03-25 16:51:16 -0700 |
commit | 481f541ced8fcf9af87bedf6f87c2023de22bf6e (patch) | |
tree | ac0388ce09a5489b480f1aa4e06bbf5524d3f0f7 /include | |
parent | 5f7e2af00807f2117650e711a58b7f0e986ce1df (diff) | |
download | linux-stable-481f541ced8fcf9af87bedf6f87c2023de22bf6e.tar.gz linux-stable-481f541ced8fcf9af87bedf6f87c2023de22bf6e.tar.bz2 linux-stable-481f541ced8fcf9af87bedf6f87c2023de22bf6e.zip |
clk: test: Test clk_set_rate_range on orphan mux
A bug recently affected the Tegra30 where calling clk_set_rate_range()
on a clock would make it change its rate to the minimum.
This was due to the clock in question being a mux that was orphan at
registration, which lead to the clk_core req_rate being 0, and the
clk_set_rate_range() function then calling clk_set_rate() with req_rate,
effectively making that clock running at the minimum rate allowed, even
though the initial rate was within that range.
Make a test suite to create a mux initially orphan, and then make sure
that if our clock rate was initially within a given range, then
enforcing that range won't affect it.
Signed-off-by: Maxime Ripard <maxime@cerno.tech>
Link: https://lore.kernel.org/r/20220325161144.1901695-3-maxime@cerno.tech
Signed-off-by: Stephen Boyd <sboyd@kernel.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions