From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Lukasz Luba <lukasz.luba@arm.com>,
Zhang Rui <rui.zhang@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>
Subject: [PATCH v2 0/6] thermal: Store trips table and ops in thermal_zone_device
Date: Wed, 14 Feb 2024 13:25:25 +0100 [thread overview]
Message-ID: <4551531.LvFx2qVVIh@kreacher> (raw)
Hi Everyone,
This is an update of
https://lore.kernel.org/linux-pm/2728491.mvXUDI8C0e@kreacher/
that has been rebased on top of
https://lore.kernel.org/linux-pm/6017196.lOV4Wx5bFT@kreacher/
and includes some bug fixes.
The original series description still applies:
"This series changes the PM core to copy the trips and zone ops directly
into struct thermal_zone_device so as to allow the callers of the zone
registration function to discard their own copies of those things after
zone registration and/or possibly allocate them as read-only.
The first patch makes the thermal core create a copy of the trips table which
is declared as a flex array to enable additional bounds checking on it. The
next two patches update the ACPI thermal driver and Intel thermal drivers to
take benefit of that change.
In a similar pattern, patch [4/6] makes the thermal core create an internal
copy of the zone ops supplied by the zone creator, so as to allow the
original ops structure to be discarded after zone registration or allocated
as read-only, and the next two patches update the ACPI thermal driver and Intel
thermal drivers to actually do that.
The other thermal drivers need not be changed, although in principle they may
be simplified a bit too in the future.
As usual, please refer to the individual patch changelogs for details."
However, the imx thermal driver is modified by patch [1/6], because it uses its
local trips table and expects it to contain the current passive trip temperature
value (as set via sysfs), and the thermal_of driver is modified by patch [4/6],
because it uses the ops pointer from the thermal zone device to free the ops.
Thanks!
next reply other threads:[~2024-02-14 12:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 12:25 Rafael J. Wysocki [this message]
2024-02-14 12:28 ` [PATCH v2 1/6] thermal: core: Store zone trips table in struct thermal_zone_device Rafael J. Wysocki
2024-02-22 10:27 ` Daniel Lezcano
2024-02-22 13:10 ` [PATCH v2.1 " Rafael J. Wysocki
2024-02-22 13:38 ` Daniel Lezcano
2024-02-22 13:45 ` Rafael J. Wysocki
2024-02-22 13:52 ` [PATCH v2.2 " Rafael J. Wysocki
2024-02-22 15:39 ` Daniel Lezcano
2024-02-14 12:30 ` [PATCH v2 2/6] thermal: ACPI: Discard trips table after zone registration Rafael J. Wysocki
2024-02-22 10:28 ` Daniel Lezcano
2024-02-14 12:42 ` [PATCH v2 3/6] thermal: intel: Discard trip tables " Rafael J. Wysocki
2024-02-22 10:34 ` Daniel Lezcano
2024-02-14 12:45 ` [PATCH v2 4/6] thermal: core: Store zone ops in struct thermal_zone_device Rafael J. Wysocki
2024-02-22 10:44 ` Daniel Lezcano
2024-02-22 10:47 ` Daniel Lezcano
2024-02-22 10:52 ` Rafael J. Wysocki
2024-02-22 10:58 ` Daniel Lezcano
2024-02-22 11:03 ` Rafael J. Wysocki
2024-02-22 14:05 ` Rafael J. Wysocki
2024-02-14 12:48 ` [PATCH v2 5/6] thermal: ACPI: Constify acpi_thermal_zone_ops Rafael J. Wysocki
2024-02-22 10:48 ` Daniel Lezcano
2024-02-14 12:49 ` [PATCH v2 6/6] thermal: intel: Adjust ops handling during thermal zone registration Rafael J. Wysocki
2024-02-22 11:06 ` Daniel Lezcano
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=4551531.LvFx2qVVIh@kreacher \
--to=rjw@rjwysocki.net \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel.lezcano@linaro.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rui.zhang@intel.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=stanislaw.gruszka@linux.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).