mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Mon, 1 Jun 2026 11:31:26 +0800	[thread overview]
Message-ID: <c669673c-ff3e-4d16-98b6-2efddf69458a@oss.qualcomm.com> (raw)
In-Reply-To: <9e5b46b8-cf04-4b9b-9e33-2cf27802690d@ti.com>

On 5/28/2026 9:26 PM, Akashdeep Kaur wrote:
> Hi Han,
> 
> On 27/05/26 13:29, Zhongqiu Han wrote:
>> 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
> ...
>>>       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?
> 
> Good catch!! I think the approach to use needs_k3_socinfo is good, i 
> have respinned the series with this approach, please take a look.


Thanks, Akashdeep.

I've shared my comments on v4.



>>
>>
>>
>>> +        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,
>>
>>
> 
> Thanks and Regards,
> Akashdeep Kaur


-- 
Thx and BRs,
Zhongqiu Han

      reply	other threads:[~2026-06-01  3:31 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
2026-05-28 13:26     ` Akashdeep Kaur
2026-06-01  3:31       ` Zhongqiu Han [this message]

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=c669673c-ff3e-4d16-98b6-2efddf69458a@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®