From: Mikko Perttunen <mperttunen@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Svyatoslav Ryhel <clamor95@gmail.com>,
Svyatoslav Ryhel <clamor95@gmail.com>
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v1 1/3] drivers: cpufreq: add Tegra 4 support
Date: Fri, 22 Aug 2025 11:58:21 +0900 [thread overview]
Message-ID: <1914341.atdPhlSkOF@senjougahara> (raw)
In-Reply-To: <20250321095556.91425-2-clamor95@gmail.com>
On Friday, March 21, 2025 6:55 PM Svyatoslav Ryhel wrote:
> Tegra 4 is fully compatible with existing Tegra K1 cpufreq driver.
>
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> ---
> drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
> drivers/cpufreq/tegra124-cpufreq.c | 5 +++--
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c
> b/drivers/cpufreq/cpufreq-dt-platdev.c index 18942bfe9c95..7d15a1224d37
> 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -140,6 +140,7 @@ static const struct of_device_id blocklist[] __initconst
> = {
>
> { .compatible = "nvidia,tegra20", },
> { .compatible = "nvidia,tegra30", },
> + { .compatible = "nvidia,tegra114", },
> { .compatible = "nvidia,tegra124", },
> { .compatible = "nvidia,tegra210", },
> { .compatible = "nvidia,tegra234", },
> diff --git a/drivers/cpufreq/tegra124-cpufreq.c
> b/drivers/cpufreq/tegra124-cpufreq.c index 514146d98bca..6ff2ccc08e5e
> 100644
> --- a/drivers/cpufreq/tegra124-cpufreq.c
> +++ b/drivers/cpufreq/tegra124-cpufreq.c
> @@ -189,8 +189,9 @@ static int __init tegra_cpufreq_init(void)
> int ret;
> struct platform_device *pdev;
>
> - if (!(of_machine_is_compatible("nvidia,tegra124") ||
> - of_machine_is_compatible("nvidia,tegra210")))
> + if (!(of_machine_is_compatible("nvidia,tegra114") ||
> + of_machine_is_compatible("nvidia,tegra124") ||
> + of_machine_is_compatible("nvidia,tegra210")))
> return -ENODEV;
>
> /*
I also prefer using Tegra114 and Tegra124 in the commit message, perhaps with
the marketing names in parentheses, as the chip IDs are more consistent and
(IMO) easier to decipher than the product names.
Reviewed-by: Mikko Perttunen <mperttunen@nvidia.com>
next prev parent reply other threads:[~2025-08-22 2:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 9:55 [PATCH v1 0/3] clk: tegra: add DFLL support for Tegra 4 Svyatoslav Ryhel
2025-03-21 9:55 ` [PATCH v1 1/3] drivers: cpufreq: add Tegra 4 support Svyatoslav Ryhel
2025-06-10 11:09 ` Thierry Reding
2025-08-11 8:08 ` Svyatoslav Ryhel
2025-08-22 2:58 ` Mikko Perttunen [this message]
2025-08-22 5:21 ` Svyatoslav Ryhel
2025-08-25 3:56 ` Mikko Perttunen
2025-03-21 9:55 ` [PATCH v1 2/3] drivers: clk: tegra: add DFLL support for Tegra 4 Svyatoslav Ryhel
2025-03-21 20:50 ` Krzysztof Kozlowski
2025-05-03 8:54 ` Svyatoslav Ryhel
2025-05-04 16:23 ` Krzysztof Kozlowski
2025-05-04 16:25 ` Svyatoslav Ryhel
2025-05-04 17:11 ` Krzysztof Kozlowski
2025-05-04 17:30 ` Svyatoslav Ryhel
2025-05-04 17:33 ` Krzysztof Kozlowski
2025-06-10 11:07 ` Thierry Reding
2025-06-18 9:13 ` Krzysztof Kozlowski
2025-07-09 15:10 ` Thierry Reding
2025-03-25 18:56 ` Stephen Boyd
2025-03-25 19:00 ` Svyatoslav Ryhel
2025-08-22 2:53 ` Mikko Perttunen
2025-03-21 9:55 ` [PATCH v1 3/3] ARM: tegra: Add DFLL clock support on " Svyatoslav Ryhel
2025-08-22 3:05 ` Mikko Perttunen
2025-08-22 5:19 ` Svyatoslav Ryhel
2025-08-25 4:20 ` Mikko Perttunen
2025-08-25 4:26 ` Svyatoslav
2025-08-26 1:42 ` Mikko Perttunen
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=1914341.atdPhlSkOF@senjougahara \
--to=mperttunen@nvidia.com \
--cc=clamor95@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=viresh.kumar@linaro.org \
/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