From: Krzysztof Kozlowski <krzk@kernel.org>
To: webgeek1234@gmail.com, 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>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 0/8] Support dynamic EMC frequency scaling on Tegra186/Tegra194
Date: Thu, 9 Oct 2025 09:05:34 +0900 [thread overview]
Message-ID: <5d7491b1-8f9a-4040-b854-ff0b94bfd24e@kernel.org> (raw)
In-Reply-To: <20250909-tegra186-icc-v2-0-09413724e781@gmail.com>
On 09/09/2025 15:21, Aaron Kling via B4 Relay wrote:
> 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.
>
Nothing improved:
https://lore.kernel.org/all/20250902-glittering-toucan-of-feminism-95fd9f@kuoka/
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-09 0:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 6:21 Aaron Kling via B4 Relay
2025-09-09 6:21 ` [PATCH v2 1/8] cpufreq: tegra186: add OPP support and set bandwidth Aaron Kling via B4 Relay
2025-09-30 10:30 ` Viresh Kumar
2025-10-13 2:32 ` Aaron Kling
2025-10-13 5:08 ` Viresh Kumar
2025-10-21 17:58 ` Aaron Kling
2025-09-09 6:21 ` [PATCH v2 2/8] dt-bindings: memory: tegra186-mc: Add dummy client IDs for Tegra186 Aaron Kling via B4 Relay
2025-09-09 6:21 ` [PATCH v2 3/8] dt-bindings: memory: tegra194-mc: Add dummy client IDs for Tegra194 Aaron Kling via B4 Relay
2025-09-09 6:21 ` [PATCH v2 4/8] memory: tegra186-emc: Support non-bpmp icc scaling Aaron Kling via B4 Relay
2025-09-09 6:21 ` [PATCH v2 5/8] memory: tegra186: Support " Aaron Kling via B4 Relay
2025-09-09 6:21 ` [PATCH v2 6/8] memory: tegra194: " Aaron Kling via B4 Relay
2025-09-09 6:21 ` [PATCH v2 7/8] arm64: tegra: Add CPU OPP tables for Tegra186 Aaron Kling via B4 Relay
2025-09-09 6:21 ` [PATCH v2 8/8] arm64: tegra: Add CPU OPP tables for Tegra194 Aaron Kling via B4 Relay
2025-10-09 0:05 ` Krzysztof Kozlowski [this message]
2025-10-13 2:18 ` [PATCH v2 0/8] Support dynamic EMC frequency scaling on Tegra186/Tegra194 Aaron Kling
2025-10-13 2:25 ` Krzysztof Kozlowski
2025-10-13 2:31 ` Aaron Kling
2025-10-20 20:14 ` Aaron Kling
2025-10-20 20:37 ` Krzysztof Kozlowski
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=5d7491b1-8f9a-4040-b854-ff0b94bfd24e@kernel.org \
--to=krzk@kernel.org \
--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-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®