From: Sumit Gupta <sumitg@nvidia.com>
To: webgeek1234@gmail.com, Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
bbasu@nvidia.com, sumitg@nvidia.com
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 0/8] Support dynamic EMC frequency scaling on Tegra186/Tegra194
Date: Thu, 4 Sep 2025 17:17:40 +0530 [thread overview]
Message-ID: <cfffcabd-c33b-46f9-9b16-b6063ceee4c1@nvidia.com> (raw)
In-Reply-To: <20250831-tegra186-icc-v1-0-607ddc53b507@gmail.com>
On 01/09/25 09:03, Aaron Kling via B4 Relay wrote:
> External email: Use caution opening links or attachments
>
>
> This series borrows the concept used on Tegra234 to scale EMC based on
> CPU frequency and applies it to Tegra186 and Tegra194. Except that the
> bpmp on those archs does not support bandwidth manager, so the scaling
> iteself is handled similar to how Tegra124 currently works.
>
> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> ---
Tegra186/194 had multiple drivers for BWMGR, ISOMGR and LA+PTSA configs
on the CPU side. I am not sure how effective this patch series will be
in absence
of those components. In Tegra234, those were moved to BPMP-FW. So, Kernel
forwards the BW request to BPMP (R5) who takes care of setting the final
freq.
Thank you,
Sumit Gupta
> Aaron Kling (8):
> dt-bindings: tegra: Add ICC IDs for dummy memory clients for Tegra186
> dt-bindings: tegra: Add ICC IDs for dummy memory clients for Tegra194
> cpufreq: tegra186: add OPP support and set bandwidth
> memory: tegra186-emc: Support non-bpmp icc scaling
> memory: tegra186: Support icc scaling
> memory: tegra194: Support icc scaling
> arm64: tegra: Add CPU OPP tables for Tegra186
> arm64: tegra: Add CPU OPP tables for Tegra194
>
> arch/arm64/boot/dts/nvidia/tegra186.dtsi | 317 +++++++++++++++
> arch/arm64/boot/dts/nvidia/tegra194.dtsi | 636 +++++++++++++++++++++++++++++++
> drivers/cpufreq/tegra186-cpufreq.c | 152 +++++++-
> drivers/memory/tegra/tegra186-emc.c | 132 ++++++-
> drivers/memory/tegra/tegra186.c | 48 +++
> drivers/memory/tegra/tegra194.c | 59 ++-
> include/dt-bindings/memory/tegra186-mc.h | 4 +
> include/dt-bindings/memory/tegra194-mc.h | 6 +
> 8 files changed, 1344 insertions(+), 10 deletions(-)
> ---
> base-commit: 1b237f190eb3d36f52dffe07a40b5eb210280e00
> change-id: 20250823-tegra186-icc-7299110cd774
> prerequisite-change-id: 20250826-tegra186-cpufreq-fixes-7fbff81c68a2:v3
> prerequisite-patch-id: 74a2633b412b641f9808306cff9b0a697851d6c8
> prerequisite-patch-id: 9c52827317f7abfb93885febb1894b40967bd64c
>
> Best regards,
> --
> Aaron Kling <webgeek1234@gmail.com>
>
>
>
next prev parent reply other threads:[~2025-09-04 11:47 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 3:33 [PATCH 0/8] Support dynamic EMC frequency scaling on Tegra186/Tegra194 Aaron Kling
2025-09-01 3:33 ` Aaron Kling via B4 Relay
2025-09-01 3:33 ` [PATCH 1/8] dt-bindings: tegra: Add ICC IDs for dummy memory clients for Tegra186 Aaron Kling
2025-09-01 3:33 ` Aaron Kling via B4 Relay
2025-09-01 3:33 ` [PATCH 2/8] dt-bindings: tegra: Add ICC IDs for dummy memory clients for Tegra194 Aaron Kling
2025-09-01 3:33 ` Aaron Kling via B4 Relay
2025-09-02 8:25 ` Krzysztof Kozlowski
2025-09-02 16:57 ` Aaron Kling
2025-09-01 3:33 ` [PATCH 3/8] cpufreq: tegra186: add OPP support and set bandwidth Aaron Kling
2025-09-01 3:33 ` Aaron Kling via B4 Relay
2025-09-01 5:53 ` Viresh Kumar
2025-09-02 17:21 ` Aaron Kling
2025-09-03 5:01 ` Viresh Kumar
2025-09-04 11:19 ` Sumit Gupta
2025-09-09 5:43 ` Aaron Kling
2025-09-01 3:33 ` [PATCH 4/8] memory: tegra186-emc: Support non-bpmp icc scaling Aaron Kling
2025-09-01 3:33 ` Aaron Kling via B4 Relay
2025-09-01 3:33 ` [PATCH 5/8] memory: tegra186: Support " Aaron Kling
2025-09-01 3:33 ` Aaron Kling via B4 Relay
2025-09-01 3:33 ` [PATCH 6/8] memory: tegra194: " Aaron Kling
2025-09-01 3:33 ` Aaron Kling via B4 Relay
2025-09-01 3:33 ` [PATCH 7/8] arm64: tegra: Add CPU OPP tables for Tegra186 Aaron Kling
2025-09-01 3:33 ` Aaron Kling via B4 Relay
2025-09-01 3:33 ` [PATCH 8/8] arm64: tegra: Add CPU OPP tables for Tegra194 Aaron Kling
2025-09-01 3:33 ` Aaron Kling via B4 Relay
2025-09-02 8:23 ` [PATCH 0/8] Support dynamic EMC frequency scaling on Tegra186/Tegra194 Krzysztof Kozlowski
2025-09-02 16:51 ` Aaron Kling
2025-09-03 6:18 ` Krzysztof Kozlowski
2025-09-03 6:20 ` Krzysztof Kozlowski
2025-09-03 6:37 ` Aaron Kling
2025-09-04 8:19 ` Krzysztof Kozlowski
2025-09-04 17:49 ` Aaron Kling
2025-09-05 6:55 ` Krzysztof Kozlowski
2025-09-04 11:47 ` Sumit Gupta [this message]
2025-09-04 16:47 ` Aaron Kling
2025-09-05 13:37 ` Sumit Gupta
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=cfffcabd-c33b-46f9-9b16-b6063ceee4c1@nvidia.com \
--to=sumitg@nvidia.com \
--cc=bbasu@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.