From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sumit Gupta <sumitg@nvidia.com>,
treding@nvidia.com, jonathanh@nvidia.com,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: bbasu@nvidia.com
Subject: Re: [Patch v2 2/2] memory: tegra: set BPMP msg flags to reset IPC channels
Date: Thu, 12 Oct 2023 15:28:53 +0200 [thread overview]
Message-ID: <edef23cb-c88f-4b98-afa8-a29c122f0a6c@linaro.org> (raw)
In-Reply-To: <20231009100557.18224-3-sumitg@nvidia.com>
On 09/10/2023 12:05, Sumit Gupta wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Set the 'TEGRA_BPMP_MESSAGE_RESET' bit in newly added 'flags' field
> of 'struct tegra_bpmp_message' to request for the reset of BPMP IPC
> channels. This is used along with the 'suspended' check in BPMP driver
> for handling early bandwidth requests due to the hotplug of CPU's
> during system resume before the driver gets resumed.
>
> Fixes: f41e1442ac5b ("cpufreq: tegra194: add OPP support and set bandwidth")
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> Co-developed-by: Sumit Gupta <sumitg@nvidia.com>
> Signed-off-by: Sumit Gupta <sumitg@nvidia.com>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-10-12 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 10:05 [Patch v2 0/2] Fix hang due to CPU BW request as BPMP suspended 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 [this message]
2023-10-13 12:25 ` (subset) [Patch v2 0/2] Fix hang due to CPU BW request as BPMP suspended Thierry Reding
2023-10-13 12:36 ` 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=edef23cb-c88f-4b98-afa8-a29c122f0a6c@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=bbasu@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=sumitg@nvidia.com \
--cc=treding@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®