Quoting Robert Marko (2020-06-08 02:47:15)
> From: Christian Lamparter <chunkeey@xxxxxxxxx>
>
> There's an interaction issue between the clk changes:"
> clk: qcom: ipq4019: Add the apss cpu pll divider clock node
> clk: qcom: ipq4019: remove fixed clocks and add pll clocks
> " and the cpufreq-dt.
>
> cpufreq-dt is now spamming the kernel-log with the following:
>
> [ 1099.190658] cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP
> for freq 761142857 (-34)
>
> This only happens on certain devices like the Compex WPJ428
> and AVM FritzBox!4040. However, other devices like the Asus
> RT-AC58U and Meraki MR33 work just fine.
>
> The issue stem from the fact that all higher CPU-Clocks
> are achieved by switching the clock-parent to the P_DDRPLLAPSS
> (ddrpllapss). Which is set by Qualcomm's proprietary bootcode
> as part of the DDR calibration.
>
> For example, the FB4040 uses 256 MiB Nanya NT5CC128M16IP clocked
> at round 533 MHz (ddrpllsdcc = 190285714 Hz).
>
> whereas the 128 MiB Nanya NT5CC64M16GP-DI in the ASUS RT-AC58U is
> clocked at a slightly higher 537 MHz ( ddrpllsdcc = 192000000 Hz).
>
> This patch attempts to fix the issue by modifying
> clk_cpu_div_round_rate(), clk_cpu_div_set_rate(), clk_cpu_div_recalc_rate()
> to use a new qcom_find_freq_close() function, which returns the closest
> matching frequency, instead of the next higher. This way, the SoC in
> the FB4040 (with its max clock speed of 710.4 MHz) will no longer
> try to overclock to 761 MHz.
Why are the OPP tables not properly indicating the frequencies that
should be chosen? The rounding policy should presumably be matching the
frequency exactly vs. relying on some sort of rounding policy to fix it.
>
> Fixes: d83dcacea18 ("clk: qcom: ipq4019: Add the apss cpu pll divider clock node")
> Signed-off-by: Christian Lamparter <chunkeey@xxxxxxxxx>
> Signed-off-by: John Crispin <john@xxxxxxxxxxx>
> Signed-off-by: Robert Marko <robert.marko@xxxxxxxxxx>
> Cc: Luka Perkov <luka.perkov@xxxxxxxxxx>
> ---
> Changes from v1 to v2:
Please update subject of the patch to indicate patch version (i.e.
PATCHv2 and next time PATCHv3, not just PATCH).
> * Resolve warnings discovered by the kbot
> * Return the return of regmap_update_bits instead of not using it at all
>
> drivers/clk/qcom/gcc-ipq4019.c | 36 ++++++++++++++++++++++++++++++----
> 1 file changed, 32 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/clk/qcom/gcc-ipq4019.c b/drivers/clk/qcom/gcc-ipq4019.c
> index ef5137fd50f3..62fa17a4291c 100644
> --- a/drivers/clk/qcom/gcc-ipq4019.c
> +++ b/drivers/clk/qcom/gcc-ipq4019.c
> @@ -1243,6 +1243,29 @@ static const struct clk_fepll_vco gcc_fepll_vco = {
> .reg = 0x2f020,
> };
>
> +
> +static const struct freq_tbl *qcom_find_freq_close(const struct freq_tbl *f,
Please call it qcom_find_freq_closest() instead.
> + unsigned long rate)
> +{
> + const struct freq_tbl *last = NULL;
> +
> + for ( ; f->freq; f++) {
> + if (rate == f->freq)
> + return f;
> +
> + if (f->freq > rate) {
> + if (!last ||
> + (f->freq - rate) < (rate - last->freq))
> + return f;
> + else
> + return last;
if (...)
return ...;
else
should be replaced with
if (...)
return ...;
...
but I also wonder if it would be clearer with some sort of 'break' and
then 'return f' type of logic.
> + }
> + last = f;
> + }
> +
> + return last;
> +}
Please relocate this to common.c in the qcom directory.
> +
> /*
> * Round rate function for APSS CPU PLL Clock divider.
> * It looks up the frequency table and returns the next higher frequency
