From: Thierry Reding <thierry.reding@gmail.com>
To: Mikko Perttunen <cyndis@kapsi.fi>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
Mikko Perttunen <mperttunen@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] thermal: tegra-bpmp: Check if BPMP supports trip points
Date: Thu, 26 Jan 2023 15:52:28 +0100 [thread overview]
Message-ID: <Y9KTrO+WqJJwuEDf@orome> (raw)
In-Reply-To: <20221129153914.2699041-1-cyndis@kapsi.fi>
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
On Tue, Nov 29, 2022 at 05:39:14PM +0200, Mikko Perttunen wrote:
> From: Mikko Perttunen <mperttunen@nvidia.com>
>
> Check if BPMP supports thermal trip points, and if not,
> do not expose the .set_trips callback to the thermal core
> framework. This can happen in virtualized environments
> where asynchronous communication with VM BPMP drivers is not
> available.
>
> Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
> ---
> drivers/thermal/tegra/tegra-bpmp-thermal.c | 52 +++++++++++++++++++++-
> 1 file changed, 51 insertions(+), 1 deletion(-)
Applied, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-26 14:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 15:39 [PATCH] thermal: tegra-bpmp: Check if BPMP supports trip points Mikko Perttunen
2023-01-26 14:52 ` Thierry Reding [this message]
2023-01-26 15:08 ` Daniel Lezcano
2023-01-26 15:42 ` Thierry Reding
2023-01-26 16:07 ` Daniel Lezcano
2023-04-03 10:22 ` Jon Hunter
2023-04-03 10:26 ` Daniel Lezcano
2023-08-21 10:08 ` Mikko Perttunen
2023-08-23 7:50 ` Daniel Lezcano
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=Y9KTrO+WqJJwuEDf@orome \
--to=thierry.reding@gmail.com \
--cc=amitk@kernel.org \
--cc=cyndis@kapsi.fi \
--cc=daniel.lezcano@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.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.