From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Lukasz Luba <lukasz.luba@arm.com>, Armin Wolf <w_armin@gmx.de>,
Jiajia Liu <liujiajia@kylinos.cn>, Marc Zyngier <maz@kernel.org>,
linux-hwmon@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>
Subject: [PATCH v2 0/3] thermal: hwmon: Rework of automatic hwmon device registration
Date: Tue, 05 May 2026 13:35:19 +0200 [thread overview]
Message-ID: <6017595.DvuYhMxLoT@rafael.j.wysocki> (raw)
Hi All,
This is an update of
https://lore.kernel.org/linux-pm/5100596.31r3eYUQgx@rafael.j.wysocki/
sent mosty to address feedback from sashiko.dev:
https://sashiko.dev/#/patchset/5100596.31r3eYUQgx%40rafael.j.wysocki
There is an extra patch in this revision (the first one) that addresses
a possible thermal hwmon removal issue pointed out by sashiko.dev.
The second patch in the series reworks the automatic registration of hwmon
devices for thermal zones so that one hwmon device is registered for each of
them. This is done to address a thermal zone removal deadlock related to the
sharing of a hwmon device with other thermal zones of the same type (see the
changelog of patch [2/3] for details).
The last patch simplifies the thermal hwmon code further by using the
canonical mechanism for registering extra sysfs attributes of hwmon devices
instead of manually adding files to sysfs.
The patches are targeted at 7.2.
Thanks!
next reply other threads:[~2026-05-05 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 11:35 Rafael J. Wysocki [this message]
2026-05-05 11:36 ` [PATCH v2 1/3] thermal: hwmon: Fix critical temperature attribute removal Rafael J. Wysocki
2026-05-05 11:44 ` [PATCH v2 2/3] thermal: hwmon: Register a hwmon device for each thermal zone Rafael J. Wysocki
2026-05-05 11:47 ` [PATCH v2 3/3] thermal: hwmon: Use extra_groups for adding temperature attributes 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=6017595.DvuYhMxLoT@rafael.j.wysocki \
--to=rafael@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=liujiajia@kylinos.cn \
--cc=lukasz.luba@arm.com \
--cc=maz@kernel.org \
--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