Hi,
This series has a couple of fixes for the Qcom CPUFreq clock provider.
Patch 1 fixes an issue where incorrect rate might be reported if LMh IRQ is not
available for a platform (issue identified based on code inspection). Patch 2
fixes a regression reported for v6.13-rc1 [1]. The regression was triggered by
commit 25f1c96a0e84 ("clk: Fix invalid execution of clk_set_rate"), which fixed
the behavior of the clk_set_rate() API. Even though the commit got reverted now,
patch 2 fixes the issue in the clock provider code.
This series is tested on Qcom RB5 development board.
[1] https://lore.kernel.org/all/20241202100621.29209-1-johan+linaro@xxxxxxxxxx
Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@xxxxxxxxxx>
---
Manivannan Sadhasivam (2):
cpufreq: qcom: Fix qcom_cpufreq_hw_recalc_rate() to query LUT if LMh IRQ is not available
cpufreq: qcom: Implement clk_ops::determine_rate() for qcom_cpufreq* clocks
drivers/cpufreq/qcom-cpufreq-hw.c | 34 ++++++++++++++++++++++++----------
1 file changed, 24 insertions(+), 10 deletions(-)
---
base-commit: 40384c840ea1944d7c5a392e8975ed088ecf0b37
change-id: 20241205-qcom-cpufreq-clk-fix-a60fbfdd7b84
Best regards,
--
Manivannan Sadhasivam <manivannan.sadhasivam@xxxxxxxxxx>
