From: Stephen Boyd <sboyd@kernel.org>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev,
Johan Hovold <johan+linaro@kernel.org>,
Aishwarya TCV <aishwarya.tcv@arm.com>,
Chuan Liu <chuan.liu@amlogic.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: [PATCH] Revert "clk: Fix invalid execution of clk_set_rate"
Date: Mon, 02 Dec 2024 17:20:06 -0800 [thread overview]
Message-ID: <3fd004add188460bf2bdd1a718387c7f.sboyd@kernel.org> (raw)
In-Reply-To: <20241202100621.29209-1-johan+linaro@kernel.org>
Quoting Johan Hovold (2024-12-02 02:06:21)
> This reverts commit 25f1c96a0e841013647d788d4598e364e5c2ebb7.
>
> The offending commit results in errors like
>
> cpu cpu0: _opp_config_clk_single: failed to set clock rate: -22
>
> spamming the logs on the Lenovo ThinkPad X13s and other Qualcomm
> machines when cpufreq tries to update the CPUFreq HW Engine clocks.
>
> As mentioned in commit 4370232c727b ("cpufreq: qcom-hw: Add CPU clock
> provider support"):
>
> [T]he frequency supplied by the driver is the actual frequency
> that comes out of the EPSS/OSM block after the DCVS operation.
> This frequency is not same as what the CPUFreq framework has set
> but it is the one that gets supplied to the CPUs after
> throttling by LMh.
>
> which seems to suggest that the driver relies on the previous behaviour
> of clk_set_rate().
I don't understand why a clk provider is needed there. Is anyone looking
into the real problem?
>
> Since this affects many Qualcomm machines, let's revert for now.
>
> Fixes: 25f1c96a0e84 ("clk: Fix invalid execution of clk_set_rate")
> Reported-by: Aishwarya TCV <aishwarya.tcv@arm.com>
> Link: https://lore.kernel.org/all/e2d83e57-ad07-411b-99f6-a4fc3c4534fa@arm.com/
> Cc: Chuan Liu <chuan.liu@amlogic.com>
> Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
> ---
Applied to clk-fixes
next prev parent reply other threads:[~2024-12-03 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 10:06 [PATCH] Revert "clk: Fix invalid execution of clk_set_rate" Johan Hovold
2024-12-03 1:20 ` Stephen Boyd [this message]
2024-12-03 8:25 ` Johan Hovold
2024-12-03 9:21 ` Manivannan Sadhasivam
2024-12-03 19:30 ` Stephen Boyd
2024-12-05 16:52 ` Manivannan Sadhasivam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3fd004add188460bf2bdd1a718387c7f.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=aishwarya.tcv@arm.com \
--cc=chuan.liu@amlogic.com \
--cc=johan+linaro@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mturquette@baylibre.com \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.