From: Guenter Roeck <linux@roeck-us.net>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Jiajia Liu <liujiajia@kylinos.cn>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Armin Wolf <w_armin@gmx.de>,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH RESEND v1] thermal: core: fix blocking in unregistering zone
Date: Sat, 4 Apr 2026 07:02:14 -0700 [thread overview]
Message-ID: <ec16fc75-c5fa-4ff9-bc6b-91464e9c26cc@roeck-us.net> (raw)
In-Reply-To: <CAJZ5v0jZPXC5g3KY+trwmV=nXJu74y=0LaQTHaQ_MnqcfPVAGQ@mail.gmail.com>
On 4/4/26 05:58, Rafael J. Wysocki wrote:
> On Fri, Apr 3, 2026 at 4:20 PM Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> On 4/3/26 05:52, Rafael J. Wysocki wrote:
>> .[ ... ]
>>> It appears to work for me, but I'm not sure if having multiple hwmon class
>>> devices with the same value in the name attribute is fine.
>>
>> Like this ?
>>
>> $ cd /sys/class/hwmon
>> $ grep . */name
>> hwmon0/name:r8169_0_c00:00
>> hwmon1/name:nvme
>> hwmon2/name:nvme
>> hwmon3/name:nct6687
>> hwmon4/name:k10temp
>> hwmon5/name:spd5118
>> hwmon6/name:spd5118
>> hwmon7/name:spd5118
>> hwmon8/name:spd5118
>> hwmon9/name:mt7921_phy0
>
> Yes.
>
>> Names such as "r8169_0_c00:00" and "mt7921_phy0" are actually overkill
>> since the "sensors" command makes it
>>
>> r8169_0_c00:00-mdio-0
>> Adapter: MDIO adapter
>> temp1: +36.0°C (high = +120.0°C)
>>
>> mt7921_phy0-pci-0d00
>> Adapter: PCI adapter
>> temp1: +30.0°C
>>
>> essentially duplicating the device index.
>
> Well, with the patch posted by me, the output of sensors from a test
> system looks like this:
>
> acpitz-acpi-0
> Adapter: ACPI interface
> temp1: +16.8°C
>
> pch_cannonlake-virtual-0
> Adapter: Virtual device
> temp1: +33.0°C
>
> acpitz-acpi-0
> Adapter: ACPI interface
> temp1: +27.8°C
>
> (some further data excluded), which is kind of confusing (note the
> duplicate acpitz-acpi-0 entries with different values of temp1).
>
Yes, agreed, that is confusing. I would have expected the second one
to be identified as "acpitz-acpi-1". Do they both have the same parent ?
> That could be disambiguated by concatenating the thermal zone ID
> (possibly after a '_') to the name. Or the "temp*" things for thermal
> zones of the same type could carry different numbers.
>
> A less attractive alternative would be to register a special virtual
> device serving as a parent for all hwmon interfaces registered
> automatically for thermal zones.
If they all have the same parent, technically it should be a single
hwmon device with multiple sensors, as in:
acpitz-acpi-0
Adapter: ACPI interface
temp1: +16.8°C
temp2: +27.8°C
Guenter
next prev parent reply other threads:[~2026-04-04 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 2:27 [PATCH RESEND v1] thermal: core: fix blocking in unregistering zone Jiajia Liu
2026-04-03 12:52 ` Rafael J. Wysocki
2026-04-03 14:20 ` Guenter Roeck
2026-04-04 12:58 ` Rafael J. Wysocki
2026-04-04 14:02 ` Guenter Roeck [this message]
2026-04-04 17:38 ` Rafael J. Wysocki
2026-04-05 3:34 ` Guenter Roeck
2026-04-08 15:05 ` Rafael J. Wysocki
2026-04-08 15:32 ` Guenter Roeck
2026-04-08 15:57 ` Rafael J. Wysocki
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=ec16fc75-c5fa-4ff9-bc6b-91464e9c26cc@roeck-us.net \
--to=linux@roeck-us.net \
--cc=daniel.lezcano@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=liujiajia@kylinos.cn \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=w_armin@gmx.de \
/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