Linux Power Management development
 help / color / mirror / Atom feed
From: Mikko Perttunen <cyndis@kapsi.fi>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>
Cc: Mikko Perttunen <mperttunen@nvidia.com>,
	linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] thermal: tegra-bpmp: Handle offline zones
Date: Thu, 30 Mar 2023 13:06:06 +0300	[thread overview]
Message-ID: <204e0435-c544-8727-e892-9fc69b8d691d@kapsi.fi> (raw)
In-Reply-To: <a09d8edf-9db1-0037-15a4-7ce329b82bf2@linaro.org>

On 3/30/23 13:03, Daniel Lezcano wrote:
> On 30/03/2023 11:49, Mikko Perttunen wrote:
>> From: Mikko Perttunen <mperttunen@nvidia.com>
>>
>> Thermal zones located in power domains may not be accessible when
>> the domain is powergated. In this situation, reading the temperature
>> will return -BPMP_EFAULT. When evaluating trips, BPMP will internally
>> use -256C as the temperature for offline zones.
> 
>> For smooth operation, for offline zones, return -EAGAIN when reading
>> the temperature and allow registration of zones even if they are
>> offline during probe.
> 
> I think it makes more sense to check if the power domain associated with 
> the device is powered up and if not return -EPROBE_DEFER.

The power domains in question are related to computer vision engines 
that only get powered on when in use, possibly never if the user doesn't 
run a computer vision workload on the system. We still want other 
thermal zones to be available.

Mikko

> 
> 
>> Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
>> ---
>> v2:
>> * Adjusted commit message.
>> * Patch 2/2 dropped for now since it is more controversial,
>>    and this patch is more critical.
>>
>>   drivers/thermal/tegra/tegra-bpmp-thermal.c | 9 ++++++++-
>>   1 file changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/thermal/tegra/tegra-bpmp-thermal.c 
>> b/drivers/thermal/tegra/tegra-bpmp-thermal.c
>> index f5fd4018f72f..4ffc3bb3bf35 100644
>> --- a/drivers/thermal/tegra/tegra-bpmp-thermal.c
>> +++ b/drivers/thermal/tegra/tegra-bpmp-thermal.c
>> @@ -52,6 +52,8 @@ static int __tegra_bpmp_thermal_get_temp(struct 
>> tegra_bpmp_thermal_zone *zone,
>>       err = tegra_bpmp_transfer(zone->tegra->bpmp, &msg);
>>       if (err)
>>           return err;
>> +    if (msg.rx.ret == -BPMP_EFAULT)
>> +        return -EAGAIN;
>>       if (msg.rx.ret)
>>           return -EINVAL;
>> @@ -259,7 +261,12 @@ static int tegra_bpmp_thermal_probe(struct 
>> platform_device *pdev)
>>           zone->tegra = tegra;
>>           err = __tegra_bpmp_thermal_get_temp(zone, &temp);
>> -        if (err < 0) {
>> +
>> +        /*
>> +         * Sensors in powergated domains may temporarily fail to be read
>> +         * (-EAGAIN), but will become accessible when the domain is 
>> powered on.
>> +         */
>> +        if (err < 0 && err != -EAGAIN) {
>>               devm_kfree(&pdev->dev, zone);
>>               continue;
>>           }
> 


  reply	other threads:[~2023-03-30 10:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30  9:49 [PATCH v2] thermal: tegra-bpmp: Handle offline zones Mikko Perttunen
2023-03-30 10:03 ` Daniel Lezcano
2023-03-30 10:06   ` Mikko Perttunen [this message]
2023-03-30 12:36     ` Daniel Lezcano
2023-03-30 13:11       ` Mikko Perttunen
2023-03-30 16:29 ` Thierry Reding
2023-03-30 21:14 ` Daniel Lezcano
2023-03-31  7:12   ` Mikko Perttunen

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=204e0435-c544-8727-e892-9fc69b8d691d@kapsi.fi \
    --to=cyndis@kapsi.fi \
    --cc=amitk@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 \
    --cc=thierry.reding@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