From: Mikko Perttunen <mperttunen@nvidia.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Aaron Kling <luceoscutum@gmail.com>,
Sumit Gupta <sumitg@nvidia.com>,
webgeek1234@gmail.com
Cc: Thierry Reding <treding@nvidia.com>,
linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, Aaron Kling <webgeek1234@gmail.com>
Subject: Re: [PATCH v2 2/2] cpufreq: tegra186: Initialize all cores to max frequencies
Date: Fri, 29 Aug 2025 09:18:22 +0900 [thread overview]
Message-ID: <2606828.Sgy9Pd6rRy@senjougahara> (raw)
In-Reply-To: <20250828-tegra186-cpufreq-fixes-v2-2-fcffe4de1e15@gmail.com>
On Friday, August 29, 2025 1:57 AM Aaron Kling via B4 Relay wrote:
> From: Aaron Kling <webgeek1234@gmail.com>
>
> During initialization, the EDVD_COREx_VOLT_FREQ registers for some cores
> are still at reset values and not reflecting the actual frequency. This
> causes get calls to fail. Set all cores to their respective max
> frequency during probe to initialize the registers to working values.
>
> Suggested-by: Mikko Perttunen <mperttunen@nvidia.com>
> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> ---
> drivers/cpufreq/tegra186-cpufreq.c | 18 +++++++++++++++---
> 1 file changed, 15 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/cpufreq/tegra186-cpufreq.c
> b/drivers/cpufreq/tegra186-cpufreq.c index
> 6c394b429b6182faffabf222e5af501393dbbba9..3cd42db955c1c705f9774879e34b71ae1
> 24e86d2 100644 --- a/drivers/cpufreq/tegra186-cpufreq.c
> +++ b/drivers/cpufreq/tegra186-cpufreq.c
> @@ -138,7 +138,8 @@ static struct cpufreq_driver tegra186_cpufreq_driver = {
>
> static struct cpufreq_frequency_table *init_vhint_table(
> struct platform_device *pdev, struct tegra_bpmp *bpmp,
> - struct tegra186_cpufreq_cluster *cluster, unsigned int cluster_id)
> + struct tegra186_cpufreq_cluster *cluster, unsigned int cluster_id,
> + int *max_rate)
'max_rate' sounds like it's the rate itself and not the index. Perhaps have
init_vhint_table output num_rates and calculate in probe? We should also
handle the possibility of num_rates being 0. Otherwise looks good to me.
Thanks!
Mikko
> {
> struct cpufreq_frequency_table *table;
> struct mrq_cpu_vhint_request req;
> @@ -218,6 +219,7 @@ static struct cpufreq_frequency_table *init_vhint_table(
> }
>
> table[j].frequency = CPUFREQ_TABLE_END;
> + *max_rate = num_rates - 1;
>
> free:
> dma_free_coherent(bpmp->dev, sizeof(*data), virt, phys);
> @@ -229,7 +231,9 @@ static int tegra186_cpufreq_probe(struct platform_device
> *pdev) {
> struct tegra186_cpufreq_data *data;
> struct tegra_bpmp *bpmp;
> - unsigned int i = 0, err;
> + unsigned int i = 0, err, edvd_offset;
> + int max_rate = 0;
> + u32 edvd_val, cpu;
>
> data = devm_kzalloc(&pdev->dev,
> struct_size(data, clusters,
TEGRA186_NUM_CLUSTERS),
> @@ -252,11 +256,19 @@ static int tegra186_cpufreq_probe(struct
> platform_device *pdev) for (i = 0; i < TEGRA186_NUM_CLUSTERS; i++) {
> struct tegra186_cpufreq_cluster *cluster = &data-
>clusters[i];
>
> - cluster->table = init_vhint_table(pdev, bpmp, cluster, i);
> + cluster->table = init_vhint_table(pdev, bpmp, cluster, i,
&max_rate);
> if (IS_ERR(cluster->table)) {
> err = PTR_ERR(cluster->table);
> goto put_bpmp;
> }
> +
> + for (cpu = 0; cpu < ARRAY_SIZE(tegra186_cpus); cpu++) {
> + if (data->cpus[cpu].bpmp_cluster_id == i) {
> + edvd_val = cluster-
>table[max_rate].driver_data;
> + edvd_offset = data->cpus[cpu].edvd_offset;
> + writel(edvd_val, data->regs +
edvd_offset);
> + }
> + }
> }
>
> tegra186_cpufreq_driver.driver_data = data;
prev parent reply other threads:[~2025-08-29 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 16:57 [PATCH v2 0/2] cpufreq: tegra186: Fix initialization and scaling Aaron Kling via B4 Relay
2025-08-28 16:57 ` [PATCH v2 1/2] cpufreq: tegra186: Set target frequency for all cpus in policy Aaron Kling via B4 Relay
2025-08-28 16:57 ` [PATCH v2 2/2] cpufreq: tegra186: Initialize all cores to max frequencies Aaron Kling via B4 Relay
2025-08-29 0:18 ` Mikko Perttunen [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=2606828.Sgy9Pd6rRy@senjougahara \
--to=mperttunen@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=luceoscutum@gmail.com \
--cc=rafael@kernel.org \
--cc=sumitg@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.com \
--cc=viresh.kumar@linaro.org \
--cc=webgeek1234@gmail.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