From: Thierry Reding <thierry.reding@gmail.com>
To: jonathanh@nvidia.com, krzysztof.kozlowski@linaro.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
Sumit Gupta <sumitg@nvidia.com>
Cc: bbasu@nvidia.com
Subject: Re: (subset) [Patch v2 0/2] Fix hang due to CPU BW request as BPMP suspended
Date: Fri, 13 Oct 2023 14:25:12 +0200 [thread overview]
Message-ID: <169719989291.3880029.32092032379655248.b4-ty@nvidia.com> (raw)
In-Reply-To: <20231009100557.18224-1-sumitg@nvidia.com>
From: Thierry Reding <treding@nvidia.com>
On Mon, 09 Oct 2023 15:35:55 +0530, Sumit Gupta wrote:
> This patch set fixes hang during system resume which started coming
> after adding Memory Interconnect and OPP support to the Tegra194 CPUFREQ
> in below change:
> f41e1442ac5b ("cpufreq: tegra194: add OPP support and set bandwidth").
>
> Tegra194 CPUFREQ driver uses 'CPUFREQ_NEED_INITIAL_FREQ_CHECK' flag
> which causes a CPU frequency set request from the 'cpuhp_cpufreq_online'
> hotplug notifier during resume. The CPU frequency set call also triggers
> a DRAM bandwidth set request but the BPMP driver hasn't resumed yet
> which results in hang during resume.
>
> [...]
Applied, thanks!
[2/2] memory: tegra: set BPMP msg flags to reset IPC channels
(no commit info)
Best regards,
--
Thierry Reding <treding@nvidia.com>
next prev parent reply other threads:[~2023-10-13 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 10:05 Sumit Gupta
2023-10-09 10:05 ` [Patch v2 1/2] firmware: tegra: add suspend hook and reset BPMP IPC early on resume Sumit Gupta
2023-10-12 11:01 ` Thierry Reding
2023-10-09 10:05 ` [Patch v2 2/2] memory: tegra: set BPMP msg flags to reset IPC channels Sumit Gupta
2023-10-12 11:00 ` Thierry Reding
2023-10-12 13:32 ` Krzysztof Kozlowski
2023-10-12 13:28 ` Krzysztof Kozlowski
2023-10-13 12:25 ` Thierry Reding [this message]
2023-10-13 12:36 ` (subset) [Patch v2 0/2] Fix hang due to CPU BW request as BPMP suspended 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=169719989291.3880029.32092032379655248.b4-ty@nvidia.com \
--to=thierry.reding@gmail.com \
--cc=bbasu@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=sumitg@nvidia.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®