public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Mikko Perttunen <mperttunen@nvidia.com>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Svyatoslav Ryhel <clamor95@gmail.com>,
	Svyatoslav Ryhel <clamor95@gmail.com>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 3/5] ARM: tegra: Add EMC OPP and ICC properties to Tegra114 EMC and ACTMON device-tree nodes
Date: Fri, 06 Feb 2026 12:40:46 +0900	[thread overview]
Message-ID: <6698837.lOV4Wx5bFT@senjougahara> (raw)
In-Reply-To: <20260126191536.78829-4-clamor95@gmail.com>

On Tuesday, January 27, 2026 4:15 AM Svyatoslav Ryhel wrote:
> Add EMC OPP tables and interconnect paths that will be used for dynamic
> memory bandwidth scaling based on memory utilization statistics.
> 
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> ---
>  .../dts/nvidia/tegra114-peripherals-opp.dtsi  | 164 ++++++++++++++++++
>  arch/arm/boot/dts/nvidia/tegra114.dtsi        |   9 +
>  2 files changed, 173 insertions(+)
>  create mode 100644 arch/arm/boot/dts/nvidia/tegra114-peripherals-opp.dtsi
> 
> diff --git a/arch/arm/boot/dts/nvidia/tegra114-peripherals-opp.dtsi b/arch/arm/boot/dts/nvidia/tegra114-peripherals-opp.dtsi
> new file mode 100644
> index 000000000000..b40a1c24abab
> --- /dev/null
> +++ b/arch/arm/boot/dts/nvidia/tegra114-peripherals-opp.dtsi
> @@ -0,0 +1,164 @@
> +// SPDX-License-Identifier: GPL-2.0
> +
> +/ {
> +	emc_icc_dvfs_opp_table: opp-table-emc {
> +		compatible = "operating-points-v2";
> +
> +		opp-12750000-900 {
> +			opp-microvolt = <900000 900000 1390000>;
> +			opp-hz = /bits/ 64 <12750000>;
> +			opp-supported-hw = <0x000F>;
> +		};
> +
> +		opp-20400000-900 {
> +			opp-microvolt = <900000 900000 1390000>;
> +			opp-hz = /bits/ 64 <20400000>;
> +			opp-supported-hw = <0x000F>;
> +		};
> +
> +		opp-40800000-900 {
> +			opp-microvolt = <900000 900000 1390000>;
> +			opp-hz = /bits/ 64 <40800000>;
> +			opp-supported-hw = <0x000F>;
> +		};
> +
> +		opp-68000000-900 {
> +			opp-microvolt = <900000 900000 1390000>;
> +			opp-hz = /bits/ 64 <68000000>;
> +			opp-supported-hw = <0x000F>;
> +		};
> +
> +		opp-102000000-900 {
> +			opp-microvolt = <900000 900000 1390000>;
> +			opp-hz = /bits/ 64 <102000000>;
> +			opp-supported-hw = <0x000F>;
> +		};
> +
> +		opp-204000000-900 {
> +			opp-microvolt = <900000 900000 1390000>;
> +			opp-hz = /bits/ 64 <204000000>;
> +			opp-supported-hw = <0x000F>;
> +			opp-suspend;
> +		};
> +
> +		opp-312000000-1000 {
> +			opp-microvolt = <1000000 1000000 1390000>;
> +			opp-hz = /bits/ 64 <312000000>;
> +			opp-supported-hw = <0x000F>;
> +		};
> +
> +		opp-408000000-1000 {
> +			opp-microvolt = <1000000 1000000 1390000>;
> +			opp-hz = /bits/ 64 <408000000>;
> +			opp-supported-hw = <0x000F>;
> +		};
> +
> +		/*
> +		 * T40X can work with 1050mV for 528MHz but T40T which is
> +		 * in the same group as T40X requires 1100mV. If there will
> +		 * be enough data that T40T can work reliably with 1050mV
> +		 * for 528MHz then voltage for 528MHz opp can be lowered.
> +		 * T40S should remain with 1100mV for 528MHz opp.
> +		 */
> +		opp-528000000-1100 {
> +			opp-microvolt = <1100000 1100000 1390000>;
> +			opp-hz = /bits/ 64 <528000000>;
> +			opp-supported-hw = <0x000F>;
> +		};
> +
> +		opp-624000000-1100 {
> +			opp-microvolt = <1100000 1100000 1390000>;
> +			opp-hz = /bits/ 64 <624000000>;
> +			opp-supported-hw = <0x000F>;
> +		};
> +
> +		opp-792000000-1100 {
> +			opp-microvolt = <1100000 1100000 1390000>;
> +			opp-hz = /bits/ 64 <792000000>;
> +			opp-supported-hw = <0x000F>;
> +		};
> +
> +		opp-900000000-1200 {
> +			opp-microvolt = <1200000 1200000 1390000>;
> +			opp-hz = /bits/ 64 <900000000>;
> +			opp-supported-hw = <0x000E>;
> +		};
> +	};
> +
> +	emc_bw_dfs_opp_table: opp-table-actmon {
> +		compatible = "operating-points-v2";
> +
> +		opp-12750000 {
> +			opp-hz = /bits/ 64 <12750000>;
> +			opp-supported-hw = <0x000F>;
> +			opp-peak-kBps = <204000>;
> +		};
> +
> +		opp-20400000 {
> +			opp-hz = /bits/ 64 <20400000>;
> +			opp-supported-hw = <0x000F>;
> +			opp-peak-kBps = <326400>;
> +		};
> +
> +		opp-40800000 {
> +			opp-hz = /bits/ 64 <40800000>;
> +			opp-supported-hw = <0x000F>;
> +			opp-peak-kBps = <652800>;
> +		};
> +
> +		opp-68000000 {
> +			opp-hz = /bits/ 64 <68000000>;
> +			opp-supported-hw = <0x000F>;
> +			opp-peak-kBps = <1088000>;
> +		};
> +
> +		opp-102000000 {
> +			opp-hz = /bits/ 64 <102000000>;
> +			opp-supported-hw = <0x000F>;
> +			opp-peak-kBps = <1632000>;
> +		};
> +
> +		opp-204000000 {
> +			opp-hz = /bits/ 64 <204000000>;
> +			opp-supported-hw = <0x000F>;
> +			opp-peak-kBps = <3264000>;
> +			opp-suspend;
> +		};
> +
> +		opp-312000000 {
> +			opp-hz = /bits/ 64 <312000000>;
> +			opp-supported-hw = <0x000F>;
> +			opp-peak-kBps = <4992000>;
> +		};
> +
> +		opp-408000000 {
> +			opp-hz = /bits/ 64 <408000000>;
> +			opp-supported-hw = <0x000F>;
> +			opp-peak-kBps = <6528000>;
> +		};
> +
> +		opp-528000000 {
> +			opp-hz = /bits/ 64 <528000000>;
> +			opp-supported-hw = <0x000F>;
> +			opp-peak-kBps = <8448000>;
> +		};
> +
> +		opp-624000000 {
> +			opp-hz = /bits/ 64 <624000000>;
> +			opp-supported-hw = <0x000F>;
> +			opp-peak-kBps = <9984000>;
> +		};
> +
> +		opp-792000000 {
> +			opp-hz = /bits/ 64 <792000000>;
> +			opp-supported-hw = <0x000F>;
> +			opp-peak-kBps = <12672000>;
> +		};
> +
> +		opp-900000000 {
> +			opp-hz = /bits/ 64 <900000000>;
> +			opp-supported-hw = <0x000E>;
> +			opp-peak-kBps = <14400000>;
> +		};
> +	};
> +};
> diff --git a/arch/arm/boot/dts/nvidia/tegra114.dtsi b/arch/arm/boot/dts/nvidia/tegra114.dtsi
> index 77ab17f397f6..9acba15fba25 100644
> --- a/arch/arm/boot/dts/nvidia/tegra114.dtsi
> +++ b/arch/arm/boot/dts/nvidia/tegra114.dtsi
> @@ -8,6 +8,8 @@
>  #include <dt-bindings/soc/tegra-pmc.h>
>  #include <dt-bindings/thermal/tegra114-soctherm.h>
>  
> +#include "tegra114-peripherals-opp.dtsi"
> +
>  / {
>  	compatible = "nvidia,tegra114";
>  	interrupt-parent = <&lic>;
> @@ -323,6 +325,9 @@ actmon: actmon@6000c800 {
>  		clock-names = "actmon", "emc";
>  		resets = <&tegra_car TEGRA114_CLK_ACTMON>;
>  		reset-names = "actmon";
> +		operating-points-v2 = <&emc_bw_dfs_opp_table>;
> +		interconnects = <&mc TEGRA114_MC_MPCORER &emc>;
> +		interconnect-names = "cpu-read";
>  		#cooling-cells = <2>;
>  	};
>  
> @@ -655,6 +660,7 @@ mc: memory-controller@70019000 {
>  
>  		#reset-cells = <1>;
>  		#iommu-cells = <1>;
> +		#interconnect-cells = <1>;
>  	};
>  
>  	emc: external-memory-controller@7001b000 {
> @@ -665,6 +671,9 @@ emc: external-memory-controller@7001b000 {
>  		clock-names = "emc";
>  
>  		nvidia,memory-controller = <&mc>;
> +		operating-points-v2 = <&emc_icc_dvfs_opp_table>;
> +
> +		#interconnect-cells = <0>;
>  	};
>  
>  	hda@70030000 {
> 

Reviewed-by: Mikko Perttunen <mperttunen@nvidia.com>




  reply	other threads:[~2026-02-06  3:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26 19:15 [PATCH v1 0/5] ARM: tegra: configure EMC and PMC Svyatoslav Ryhel
2026-01-26 19:15 ` [PATCH v1 1/5] ARM: tegra: Add ACTMON node to Tegra114 device tree Svyatoslav Ryhel
2026-01-26 19:15 ` [PATCH v1 2/5] ARM: tegra: Add External Memory Controller node on Tegra114 Svyatoslav Ryhel
2026-01-26 19:15 ` [PATCH v1 3/5] ARM: tegra: Add EMC OPP and ICC properties to Tegra114 EMC and ACTMON device-tree nodes Svyatoslav Ryhel
2026-02-06  3:40   ` Mikko Perttunen [this message]
2026-01-26 19:15 ` [PATCH v1 4/5] ARM: tegra: add DC interconnections for Tegra114 Svyatoslav Ryhel
2026-01-26 19:15 ` [PATCH v1 5/5] ARM: tegra: configure Tegra114 power domains Svyatoslav Ryhel
2026-02-13  3:44   ` Mikko Perttunen
2026-02-13  8:10     ` Svyatoslav Ryhel
2026-03-27 23:48 ` [PATCH v1 0/5] ARM: tegra: configure EMC and PMC Thierry Reding

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=6698837.lOV4Wx5bFT@senjougahara \
    --to=mperttunen@nvidia.com \
    --cc=clamor95@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --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