All of
 help / color / mirror / Atom feed
From: Cao Van Dong <>
To: Marc Zyngier <>,,,
	Eduardo Valentin <>,
	Guenter Roeck <>,
	Enric Balletbo i Serra <>
Subject: Re: [PATCH v2] thermal_hwmon: Fix the 'No sensors found' error after replacing the parameter NULL by the actual device
Date: Thu, 4 Oct 2018 10:29:19 +0900	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 2990 bytes --]

Dear Marc-san,

Thanks for your comment!

>> Formerly, when registering the hwmon device, we pass NULL as the 
>> device. It's not a problem.
>> Recently, the developer has replaced the parameter NULL as the device 
>> by the actual device.
>> This causes the "No sensors found" error. Therefore, instead of using 
>> the device we will use pass
> What does report this error? Is it a userspace application?

Below are the comments of Guente-san:
  " The "No sensors found" message is from the "sensors" application.
    The device type associated with the passed device is unknown to
    libsensors (it is parsed from the parent device subsystem name -
    what is that, anyway ?). This could be addressed in libsensors,
    or the thermal subsystem could attach itself to a known subsystem,
    or the thermal subsystem must pass a pointer the parent device. "

I think the problem is the thermal subsystem must pass a pointer the 
parent device.

>> the parent of that device as parameter. This will sync with the 
>> processor on the hwmon core.
>> This patch is to fix this error.
>> This patch is based on the v4.19-rc3 tag.
>> ---
> This patch has no SoB.

I will add SoB later.

>>   drivers/thermal/thermal_hwmon.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>> diff --git a/drivers/thermal/thermal_hwmon.c 
>> b/drivers/thermal/thermal_hwmon.c
>> index 40c69a5..a918ba9 100644
>> --- a/drivers/thermal/thermal_hwmon.c
>> +++ b/drivers/thermal/thermal_hwmon.c
>> @@ -143,7 +143,7 @@ int thermal_add_hwmon_sysfs(struct 
>> thermal_zone_device *tz)
>>       INIT_LIST_HEAD(&hwmon->tz_list);
>>       strlcpy(hwmon->type, tz->type, THERMAL_NAME_LENGTH);
>>       strreplace(hwmon->type, '-', '_');
>> -    hwmon->device = hwmon_device_register_with_info(&tz->device, 
>> hwmon->type,
>> +    hwmon->device = 
>> hwmon_device_register_with_info(tz->device.parent, hwmon->type,
>>                               hwmon, NULL, NULL);
>>       if (IS_ERR(hwmon->device)) {
>>           result = PTR_ERR(hwmon->device);
> It is not clear to me that this is any better. What is the parent 
> device in this case? Can you give an example of what breaks in the 
> hierarchy?
> Given how close we are to to 4.19, I'd rather we revert 
> f6b6b52ef7a54160 if there are userspace visible regressions.

Initially, I considered your patch to be correct and went to look at the 
processor in the hwmon core. Then I created the v1 patch.
After patch v1, I noticed that it is necessary to check for cases where 
the device has parent and if there is no parent.
However, when looking at function hwmon_device_register_with_info() and 
its header, I see that the device parameter passed in
must be the parent device ("* @dev: the parent device"). Therefore, I 
think it's best to pass a parent device parameter to this function.
So, I decided to create this v2 patch.


[-- Attachment #2: Type: text/html, Size: 6006 bytes --]

  reply	other threads:[~2018-10-04  1:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03  7:25 [PATCH v2] thermal_hwmon: Fix the 'No sensors found' error after replacing the parameter NULL by the actual device Cao Van Dong
2018-10-03  7:35 ` Geert Uytterhoeven
2018-10-03  8:07 ` Marc Zyngier
2018-10-04  1:29   ` Cao Van Dong [this message]
2018-10-04 16:56     ` Guenter Roeck

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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.