From: Jon Hunter <jonathanh@nvidia.com>
To: Aaron Kling <webgeek1234@gmail.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v4 3/5] memory: tegra186-emc: Support non-bpmp icc scaling
Date: Wed, 17 Dec 2025 18:59:38 +0000 [thread overview]
Message-ID: <45057c95-1dba-4302-94fa-f63941ee2b20@nvidia.com> (raw)
In-Reply-To: <CALHNRZ9mfO_DQR-RuH_QH=18R8zTt9VqbPaVCdnDKUWzx1pm3Q@mail.gmail.com>
On 17/12/2025 18:39, Aaron Kling wrote:
...
> To try to move a resolution along, let me try to enumerate the issues
> again. Again, please clarify should I have something incorrect or
> incomplete.
>
> 1) The primary issue is when an old dtb is used with this commit and
> the pcie driver is loaded. I can reproduce this issue on t186 and
> t194. If this becomes the sole remaining blocking issue, I would like
> for an exception to the normal rule be considered and this merged
> anyways. Since it does not cause a boot failure and distros package a
> new dt normally anyways. And to my knowledge, working around this
> would involve redoing part off the icc subsystem itself, a major task
> in comparison.
>
> 2) T194 is reported to have low clocks even with a new dt on the
> Nvidia regression bench. I cannot reproduce this, even with the pcie
> driver loaded. Can this be re-verified, please? And if it still
> happens, can logs from the failure be made available and/or more
> information provided as to the state of the unit? Like changes to the
> default defconfig, modules that get loaded, etc.
Can you list all the patches that need to be applied on top of the
current -next and I will run it through our testing to make sure I have
this correct.
> 3) Setting the max clock via debugfs fails when icc has pushed the
> current clock higher than the requested rate. This is a logic issue
> with all tegra emc drivers that implement dfs via icc. The suggested
> resolutions are to leave this as is to keep consistency with the
> existing drivers, perhaps updating all later, or to update the
> existing implementations in a separate series, then send a new
> revision here to match. I am personally unable to verify anything
> older than tegra124, however.
Thierry and I chatted about this last week and we feel that debugfs
should be able to override the current configuration. So this will need
to be addressed as well.
Jon
--
nvpublic
next prev parent reply other threads:[~2025-12-17 20:32 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 18:55 [PATCH v4 0/5] memory: tegra: Support EMC dfs on Tegra186/Tegra194 Aaron Kling via B4 Relay
2025-10-27 18:55 ` [PATCH v4 1/5] dt-bindings: memory: tegra186-mc: Add dummy client IDs for Tegra186 Aaron Kling via B4 Relay
2025-10-27 18:55 ` [PATCH v4 2/5] dt-bindings: memory: tegra194-mc: Add dummy client IDs for Tegra194 Aaron Kling via B4 Relay
2025-10-27 18:55 ` [PATCH v4 3/5] memory: tegra186-emc: Support non-bpmp icc scaling Aaron Kling via B4 Relay
2025-11-10 21:25 ` Jon Hunter
2025-11-10 21:55 ` Aaron Kling
2025-11-11 1:39 ` Aaron Kling
2025-11-11 11:13 ` Jon Hunter
2025-11-11 11:16 ` Krzysztof Kozlowski
2025-11-11 12:05 ` Jon Hunter
2025-11-11 14:35 ` Jon Hunter
2025-11-11 17:04 ` Aaron Kling
2025-11-11 21:29 ` Jon Hunter
2025-11-11 23:17 ` Aaron Kling
2025-11-12 6:18 ` Jon Hunter
2025-11-12 7:21 ` Aaron Kling
2025-11-12 7:31 ` Krzysztof Kozlowski
2025-11-21 11:21 ` Jon Hunter
2025-11-21 18:17 ` Aaron Kling
2025-12-10 4:08 ` Jon Hunter
2025-12-10 5:06 ` Aaron Kling
2025-12-10 15:03 ` Jon Hunter
2025-12-10 18:32 ` Aaron Kling
2025-12-10 21:24 ` Jon Hunter
2025-12-10 22:41 ` Aaron Kling
2025-12-11 7:46 ` Jon Hunter
2025-12-11 17:39 ` Aaron Kling
2025-12-17 18:39 ` Aaron Kling
2025-12-17 18:59 ` Jon Hunter [this message]
2025-12-17 20:29 ` Aaron Kling
2025-12-17 21:53 ` Jon Hunter
2025-12-17 22:44 ` Aaron Kling
2025-12-18 11:12 ` Jon Hunter
2025-12-18 19:25 ` Aaron Kling
2025-12-18 21:20 ` Aaron Kling
2025-12-19 11:05 ` Jon Hunter
2025-11-22 12:01 ` Krzysztof Kozlowski
2025-12-09 4:26 ` Aaron Kling
2025-12-09 5:53 ` Krzysztof Kozlowski
2025-12-10 4:08 ` Jon Hunter
2025-11-12 7:26 ` Krzysztof Kozlowski
2025-11-12 10:59 ` Jon Hunter
2025-11-12 11:42 ` Krzysztof Kozlowski
2025-11-12 12:29 ` Jon Hunter
2025-11-12 7:26 ` Krzysztof Kozlowski
2025-10-27 18:55 ` [PATCH v4 4/5] memory: tegra186: Support " Aaron Kling via B4 Relay
2025-10-27 18:55 ` [PATCH v4 5/5] memory: tegra194: " Aaron Kling via B4 Relay
2025-10-31 13:21 ` [PATCH v4 0/5] memory: tegra: Support EMC dfs on Tegra186/Tegra194 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=45057c95-1dba-4302-94fa-f63941ee2b20@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--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