From: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
To: Akashdeep Kaur <a-kaur@ti.com>,
praneeth@ti.com, nm@ti.com, vigneshr@ti.com, rafael@kernel.org,
viresh.kumar@linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: vishalm@ti.com, sebin.francis@ti.com, k-willis@ti.com,
zhongqiu.han@oss.qualcomm.com
Subject: Re: [PATCH v3 1/1] cpufreq: ti: Add EPROBE_DEFER for K3 SoCs
Date: Wed, 27 May 2026 15:59:20 +0800 [thread overview]
Message-ID: <c1214419-1f29-490e-a553-8662b08de2c1@oss.qualcomm.com> (raw)
In-Reply-To: <20260527062534.1808422-2-a-kaur@ti.com>
On 5/27/2026 2:25 PM, Akashdeep Kaur wrote:
> On K3 SoCs, ti-cpufreq relies on k3-socinfo to register the SoC
> device before soc_device_match() can return valid revision
> information. If ti-cpufreq probes before k3-socinfo,
> soc_device_match() returns NULL, leading to incorrect CPU frequency
> scaling behavior.
> Defer probe when k3-socinfo hasn't registered the SoC device yet.
>
> Signed-off-by: Akashdeep Kaur <a-kaur@ti.com>
> ---
> drivers/cpufreq/ti-cpufreq.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/cpufreq/ti-cpufreq.c b/drivers/cpufreq/ti-cpufreq.c
> index a01abc1622eb..72832898f3f5 100644
> --- a/drivers/cpufreq/ti-cpufreq.c
> +++ b/drivers/cpufreq/ti-cpufreq.c
> @@ -429,6 +429,7 @@ static int ti_cpufreq_get_efuse(struct ti_cpufreq_data *opp_data,
> static int ti_cpufreq_get_rev(struct ti_cpufreq_data *opp_data,
> u32 *revision_value)
> {
> + const struct of_device_id *match;
> struct device *dev = opp_data->cpu_dev;
> u32 revision;
> int ret;
> @@ -441,6 +442,15 @@ static int ti_cpufreq_get_rev(struct ti_cpufreq_data *opp_data,
> */
> *revision_value = 0x1;
> goto done;
> + } else {
> + /* Check if we're on a K3 SoC that needs k3-socinfo */
> + match = dev_get_platdata(dev);
Hi Akashdeep,
Just to double-check: here 'dev' is 'opp_data->cpu_dev'
(get_cpu_device(0)), not 'pdev->dev', right?
In that case, would the 'struct of_device_id' match data actually be
associated with the ti-cpufreq platform device rather than the CPU
device?
Do you think it would be reasonable to add a boolean
`needs_k3_socinfo` flag to `struct ti_cpufreq_soc_data` (similar to the
existing multi_regulator pattern), and check
`opp_data->soc_data->needs_k3_socinfo` instead?
> + if (match && !strncmp(match->compatible, "ti,am62", 7)) {
> + /* SoC info not ready yet, defer */
> + dev_dbg(opp_data->cpu_dev,
> + "Failed to get SoC info, deferring probe\n");
> + return -EPROBE_DEFER;
> + }
> }
>
> ret = regmap_read(opp_data->syscon, opp_data->soc_data->rev_offset,
--
Thx and BRs,
Zhongqiu Han
next prev parent reply other threads:[~2026-05-27 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 6:25 [PATCH v3 0/1] cpufreq: ti: Fix probe ordering with k3-socinfo Akashdeep Kaur
2026-05-27 6:25 ` [PATCH v3 1/1] cpufreq: ti: Add EPROBE_DEFER for K3 SoCs Akashdeep Kaur
2026-05-27 7:59 ` Zhongqiu Han [this message]
2026-05-28 13:26 ` Akashdeep Kaur
2026-06-01 3:31 ` Zhongqiu Han
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=c1214419-1f29-490e-a553-8662b08de2c1@oss.qualcomm.com \
--to=zhongqiu.han@oss.qualcomm.com \
--cc=a-kaur@ti.com \
--cc=k-willis@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=rafael@kernel.org \
--cc=sebin.francis@ti.com \
--cc=vigneshr@ti.com \
--cc=viresh.kumar@linaro.org \
--cc=vishalm@ti.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®