From: Dmitry Osipenko <digetx@gmail.com>
To: Svyatoslav Ryhel <clamor95@gmail.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mikko Perttunen <mperttunen@nvidia.com>
Cc: linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] devfreq: tegra30-devfreq: add support for Tegra114
Date: Tue, 3 Mar 2026 02:23:49 +0300 [thread overview]
Message-ID: <4b98421a-9e64-48cb-9726-ff34a5b9cc76@gmail.com> (raw)
In-Reply-To: <20260126185423.77786-2-clamor95@gmail.com>
26.01.2026 21:54, Svyatoslav Ryhel пишет:
> Lets add Tegra114 support to activity monitor device as a preparation to
> upcoming EMC controller support.
>
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> Reviewed-by: Mikko Perttunen <mperttunen@nvidia.com>
> ---
> drivers/devfreq/tegra30-devfreq.c | 17 ++++++++++++-----
> 1 file changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/devfreq/tegra30-devfreq.c b/drivers/devfreq/tegra30-devfreq.c
> index 8ea5b482bfb3..fa83480a923f 100644
> --- a/drivers/devfreq/tegra30-devfreq.c
> +++ b/drivers/devfreq/tegra30-devfreq.c
> @@ -963,16 +963,22 @@ static int tegra_devfreq_probe(struct platform_device *pdev)
> return 0;
> }
>
> +/*
> + * The activity counter is incremented every 256 memory transactions. However,
> + * the number of clock cycles required for each transaction varies across
> + * different SoC generations. For instance, a single transaction takes 2 EMC
> + * clocks on Tegra30, 1 EMC clock on Tegra114, and 4 EMC clocks on Tegra124.
> + */
> static const struct tegra_devfreq_soc_data tegra124_soc = {
> .configs = tegra124_device_configs,
> -
> - /*
> - * Activity counter is incremented every 256 memory transactions,
> - * and each transaction takes 4 EMC clocks.
> - */
> .count_weight = 4 * 256,
> };
>
> +static const struct tegra_devfreq_soc_data tegra114_soc = {
> + .configs = tegra124_device_configs,
> + .count_weight = 256,
> +};
> +
> static const struct tegra_devfreq_soc_data tegra30_soc = {
> .configs = tegra30_device_configs,
> .count_weight = 2 * 256,
> @@ -980,6 +986,7 @@ static const struct tegra_devfreq_soc_data tegra30_soc = {
>
> static const struct of_device_id tegra_devfreq_of_match[] = {
> { .compatible = "nvidia,tegra30-actmon", .data = &tegra30_soc, },
> + { .compatible = "nvidia,tegra114-actmon", .data = &tegra114_soc, },
> { .compatible = "nvidia,tegra124-actmon", .data = &tegra124_soc, },
> { },
> };
Acked-by: Dmitry Osipenko <digetx@gmail.com>
next prev parent reply other threads:[~2026-03-02 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 18:54 [PATCH v1 0/1] devfreq: tegra30-devfreq: add support for Tegra114 Svyatoslav Ryhel
2026-01-26 18:54 ` [PATCH v1 1/1] " Svyatoslav Ryhel
2026-03-02 23:23 ` Dmitry Osipenko [this message]
2026-03-08 8:01 ` MyungJoo Ham
2026-03-21 7:10 ` Chanwoo Choi
2026-03-02 7:48 ` [PATCH v1 0/1] " Svyatoslav Ryhel
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=4b98421a-9e64-48cb-9726-ff34a5b9cc76@gmail.com \
--to=digetx@gmail.com \
--cc=clamor95@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=jonathanh@nvidia.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=myungjoo.ham@samsung.com \
--cc=thierry.reding@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