linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
	rafael@kernel.org, dan.carpenter@oracle.com,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH 2/4] thermal/of: Return -ENODEV instead of -EINVAL if registration fails
Date: Mon, 08 Aug 2022 21:05:46 +0200	[thread overview]
Message-ID: <d676c6533e11ac357a8aaca4ba216b6d@walle.cc> (raw)
In-Reply-To: <f8008f05-4e4d-e21f-2e40-e234930ee86e@roeck-us.net>

Am 2022-08-08 20:35, schrieb Guenter Roeck:
> On 8/8/22 11:09, Daniel Lezcano wrote:
>> The previous version of the OF code was returning -ENODEV if no
>> thermal zones description was found or if the lookup of the sensor in
>> the thermal zones was not found.
>> 
>> The backend drivers are expecting this return value as an information
>> about skipping the sensor initialization and considered as normal.
>> 
>> Fix the return value by replacing -EINVAL by -ENODEV
>> 
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>> ---
>>   drivers/thermal/thermal_of.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>> 
>> diff --git a/drivers/thermal/thermal_of.c 
>> b/drivers/thermal/thermal_of.c
>> index 368eb58e97cf..4210c18ef7b2 100644
>> --- a/drivers/thermal/thermal_of.c
>> +++ b/drivers/thermal/thermal_of.c
>> @@ -329,7 +329,7 @@ static struct device_node 
>> *of_thermal_zone_find(struct device_node *sensor, int
>>   	np = of_find_node_by_name(NULL, "thermal-zones");
>>   	if (!np) {
>>   		pr_err("Unable to find thermal zones description\n");
> 
> I really don't like that error message: People will see it (and 
> complain)
> whenever a sensor registers and there is no thermal zone, even though 
> that
> is perfectly normal (see description above).

I can second that, and there actually two error messages:

[    6.156983] thermal_sys: Unable to find thermal zones description
[    6.163125] thermal_sys: Failed to find thermal zone for hwmon id=0

On the sl28 board with the qoriq_thermal driver:
[    1.917940] thermal_sys: Failed to find thermal zone for tmu id=2
[    1.929231] thermal_sys: Failed to find thermal zone for tmu id=3
[    1.940519] thermal_sys: Failed to find thermal zone for tmu id=4
[    1.951814] thermal_sys: Failed to find thermal zone for tmu id=5
[    1.963109] thermal_sys: Failed to find thermal zone for tmu id=6
[    1.974399] thermal_sys: Failed to find thermal zone for tmu id=7
[    1.985690] thermal_sys: Failed to find thermal zone for tmu id=8
[    1.996980] thermal_sys: Failed to find thermal zone for tmu id=9
[    2.008274] thermal_sys: Failed to find thermal zone for tmu id=10
[    2.019656] thermal_sys: Failed to find thermal zone for tmu id=11
[    2.031037] thermal_sys: Failed to find thermal zone for tmu id=12
[    2.048942] thermal_sys: Failed to find thermal zone for tmu id=13
[    2.060320] thermal_sys: Failed to find thermal zone for tmu id=14
[    2.071700] thermal_sys: Failed to find thermal zone for tmu id=15

Btw. the driver seems to always register 16 sensors regardless how
many the actual hardware has (or rather: are described in the DT).

-michael

  reply	other threads:[~2022-08-08 19:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 18:09 [PATCH 1/4] thermal/of: Fix error code in of_thermal_zone_find() Daniel Lezcano
2022-08-08 18:09 ` [PATCH 2/4] thermal/of: Return -ENODEV instead of -EINVAL if registration fails Daniel Lezcano
2022-08-08 18:35   ` Guenter Roeck
2022-08-08 19:05     ` Michael Walle [this message]
2022-08-08 21:17       ` Daniel Lezcano
2022-08-08 20:31     ` Daniel Lezcano
2022-08-08 21:33       ` Guenter Roeck
2022-08-08 19:03   ` Michael Walle
2022-08-08 18:09 ` [PATCH 3/4] dt-bindings: thermal: Fix missing required property Daniel Lezcano
2022-08-08 18:09 ` [PATCH 4/4] thermal/of: Fix free after use in thermal_of_unregister() Daniel Lezcano
2022-08-08 18:44   ` Michael Walle

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=d676c6533e11ac357a8aaca4ba216b6d@walle.cc \
    --to=michael@walle.cc \
    --cc=amitk@kernel.org \
    --cc=dan.carpenter@oracle.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).