[PATCH v1 0/1] devfreq: tegra30-devfreq: add support for Tegra114

[PATCH v1 0/1] devfreq: tegra30-devfreq: add support for Tegra114

[Svyatoslav Ryhel]

Lets add Tegra114 support to activity monitor device as a preparation to
upcoming EMC controller support.

Part of previous patchset: https://lore.kernel.org/lkml/20251125120559.158860-1-clamor95@gmail.com/

Svyatoslav Ryhel (1):
  devfreq: tegra30-devfreq: add support for Tegra114

 drivers/devfreq/tegra30-devfreq.c | 17 ++++++++++++-----
 1 file changed, 12 insertions(+), 5 deletions(-)

-- 
2.51.0

[PATCH v1 1/1] devfreq: tegra30-devfreq: add support for Tegra114

[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, },
 	{ },
 };
-- 
2.51.0

Re: [PATCH v1 0/1] devfreq: tegra30-devfreq: add support for Tegra114

[Svyatoslav Ryhel]

пн, 26 січ. 2026 р. о 20:54 Svyatoslav Ryhel <clamor95@gmail.com> пише:
>
> Lets add Tegra114 support to activity monitor device as a preparation to
> upcoming EMC controller support.
>
> Part of previous patchset: https://lore.kernel.org/lkml/20251125120559.158860-1-clamor95@gmail.com/
>
> Svyatoslav Ryhel (1):
>   devfreq: tegra30-devfreq: add support for Tegra114
>
>  drivers/devfreq/tegra30-devfreq.c | 17 ++++++++++++-----
>  1 file changed, 12 insertions(+), 5 deletions(-)
>

Hello there!

May this patch be picked if everyone is fine with it?

Best regards,
Svyatoslav R.

> --
> 2.51.0
>

Re: [PATCH v1 1/1] devfreq: tegra30-devfreq: add support for Tegra114

[Dmitry Osipenko]

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>

Re: [PATCH v1 1/1] devfreq: tegra30-devfreq: add support for Tegra114

[MyungJoo Ham]

2026년 3월 3일 (화) AM 8:24, Dmitry Osipenko <digetx@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>

Acked-by: MyungJoo Ham <myungjoo.ham@gmail.com>

-- 
MyungJoo Ham, Ph.D.
Samsung Electronics

Re: [PATCH v1 1/1] devfreq: tegra30-devfreq: add support for Tegra114

[Chanwoo Choi]

Hi,

I'm sorry for late reply.

Applied it. Thanks.

On Sun, Mar 8, 2026 at 5:02 PM MyungJoo Ham <myungjoo.ham@samsung.com> wrote:
>
> 2026년 3월 3일 (화) AM 8:24, Dmitry Osipenko <digetx@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>
>
> Acked-by: MyungJoo Ham <myungjoo.ham@gmail.com>
>
> --
> MyungJoo Ham, Ph.D.
> Samsung Electronics
>


-- 
Best Regards,
Chanwoo Choi
Samsung Electronics