From: Armin Wolf <W_Armin@gmx.de>
To: "Rafael J. Wysocki (Intel)" <rafael@kernel.org>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Hans de Goede <hansg@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Lukasz Luba <lukasz.luba@arm.com>
Subject: Re: [PATCH v1 00/10] ACPI: thermal: Register thermal class cooling devices under parents
Date: Tue, 15 Sep 2026 21:20:43 +0200 [thread overview]
Message-ID: <77b1542a-5f3d-4d8f-bf97-67e2c2805927@gmx.de> (raw)
In-Reply-To: <CAJZ5v0gLWT4x44Vbruaf0cKWp0jPTkLuh0pLQ29_O5vfNC4q_A@mail.gmail.com>
Am 12.09.26 um 15:34 schrieb Rafael J. Wysocki (Intel):
> On Fri, Sep 11, 2026 at 11:35 PM Armin Wolf <W_Armin@gmx.de> wrote:
>> Am 11.09.26 um 15:00 schrieb Rafael J. Wysocki:
>>
>>> Hi All,
>>>
>>> This series generally changes the way in which thermal class cooling devices
>>> are used by ACPI device drivers registering them (ACPI processor, ACPI fan,
>>> and ACPI video) and by the ACPI thermal zone device driver.
>>>
>>> First, it causes the thermal class cooling devices to be registered under
>>> parents in specific locations within the device hierarchy which allows
>>> their relationships with other devices to be recognized more easily. It
>>> also drops custom sysfs attributes registered by the users of the thermal
>>> class cooling devices because they are not particularly useful any more
>>> when those devices get proper parents.
>>>
>>> Second, it modifies the ACPI thermal zone device driver to use thermal class
>>> cooling device parent information for binding cooling devices to trip points
>>> in thermal zones, which was previously done with the help of the devdata
>>> pointers of the cooling devices and effectively prevented drivers from using
>>> the devdata pointers for their own purposes as originally intended.
>>>
>>> Finally, it updates the ACPI processor and ACPI fan drivers to use the
>>> devdata pointers of thermal class cooling devices in a bit more efficient
>>> way.
>>>
>>> The first two patches in the series are preliminary fixes preventing
>>> Sashiko from reporting "pre-existing issues" in the subsequent patches.
>>>
>>> The third patch is a thermal core update allowing thermal class cooling
>>> devices to be registered under proper parents.
>>>
>>> The other patches update the ACPI processor, ACPI video, and ACPI fan
>>> drivers as per the above.
>>>
>>> The details are covered by individual patch changelogs.
>>>
>>> Thanks!
>> Nice patch series, it looks mostly good to me.
> Thanks!
>
>> Do you plan something similar for thermal zones?
> I do overall, but that is a bit harder due to the hwmon involvement.
I understand, maybe we can discuss this on the LPC.
Thanks,
Armin Wolf
prev parent reply other threads:[~2026-09-15 19:20 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 13:00 Rafael J. Wysocki
2026-09-11 13:00 ` [PATCH v1 01/10] ACPI: fan: Fix memory leak due to leftover devm_kcalloc() argument Rafael J. Wysocki
2026-09-11 16:29 ` Andy Shevchenko
2026-09-12 13:48 ` Rafael J. Wysocki (Intel)
2026-09-11 21:01 ` Armin Wolf
2026-09-11 13:01 ` [PATCH v1 02/10] ACPI: video: Fix backlight unregistration ordering Rafael J. Wysocki
2026-09-11 16:27 ` Andy Shevchenko
2026-09-11 16:35 ` Rafael J. Wysocki (Intel)
2026-09-11 21:02 ` Armin Wolf
2026-09-11 13:02 ` [PATCH v1 03/10] thermal: core: Introduce thermal_cooling_device_create() Rafael J. Wysocki
2026-09-11 21:04 ` Armin Wolf
2026-09-14 10:18 ` Rafael J. Wysocki (Intel)
2026-09-15 19:25 ` Armin Wolf
2026-09-11 13:02 ` [PATCH v1 04/10] ACPI: processor: thermal: Use thermal_cooling_device_create() Rafael J. Wysocki
2026-09-11 16:32 ` Andy Shevchenko
2026-09-11 16:36 ` Rafael J. Wysocki (Intel)
2026-09-11 16:46 ` Andy Shevchenko
2026-09-11 17:01 ` Rafael J. Wysocki (Intel)
2026-09-11 18:06 ` Andy Shevchenko
2026-09-11 21:14 ` Armin Wolf
2026-09-13 8:15 ` Andy Shevchenko
2026-09-13 10:28 ` Rafael J. Wysocki (Intel)
2026-09-14 4:35 ` Andy Shevchenko
2026-09-11 21:11 ` Armin Wolf
2026-09-11 13:03 ` [PATCH v1 05/10] ACPI: video: " Rafael J. Wysocki
2026-09-11 21:16 ` Armin Wolf
2026-09-11 13:04 ` [PATCH v1 06/10] ACPI: fan: " Rafael J. Wysocki
2026-09-11 21:17 ` Armin Wolf
2026-09-11 13:05 ` [PATCH v1 07/10] ACPI: thermal: Use cooling device parent for thermal zone binding Rafael J. Wysocki
2026-09-11 16:36 ` Andy Shevchenko
2026-09-11 16:41 ` Rafael J. Wysocki (Intel)
2026-09-11 21:20 ` Armin Wolf
2026-09-11 13:05 ` [PATCH v1 08/10] ACPI: processor: thermal: Use more suitable cooling device data Rafael J. Wysocki
2026-09-11 21:22 ` Armin Wolf
2026-09-11 13:06 ` [PATCH v1 09/10] ACPI: fan: Store ACPI device pointer in struct acpi_fan Rafael J. Wysocki
2026-09-11 21:25 ` Armin Wolf
2026-09-11 13:07 ` [PATCH v1 10/10] ACPI: fan: Use more suitable cooling device data Rafael J. Wysocki
2026-09-11 21:26 ` Armin Wolf
2026-09-11 21:35 ` [PATCH v1 00/10] ACPI: thermal: Register thermal class cooling devices under parents Armin Wolf
2026-09-12 13:34 ` Rafael J. Wysocki (Intel)
2026-09-15 19:20 ` Armin Wolf [this message]
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=77b1542a-5f3d-4d8f-bf97-67e2c2805927@gmx.de \
--to=w_armin@gmx.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel.lezcano@kernel.org \
--cc=hansg@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
/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
all inboxes | Powered by JetHome®