From: "Zhang, Rui" <rui.zhang@intel.com>
To: "rafael@kernel.org" <rafael@kernel.org>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>
Cc: "srinivas.pandruvada@linux.intel.com"
<srinivas.pandruvada@linux.intel.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"christophe.jaillet@wanadoo.fr" <christophe.jaillet@wanadoo.fr>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v4 0/3] Thermal ACPI APIs for generic trip points
Date: Wed, 11 Jan 2023 14:49:47 +0000 [thread overview]
Message-ID: <d51432466ed6b1a8eef0e966bf1b2c2bb2e1e37f.camel@intel.com> (raw)
In-Reply-To: <b070cfab-b8ab-f795-0c98-fc874f05f16b@linaro.org>
On Wed, 2023-01-11 at 12:52 +0100, Daniel Lezcano wrote:
> Can I consider these changes ok for thermal/bleeding-edge ?
>
>
Hi, Daniel,
In general, the patch looks good to me.
But can you give me more time so that I can test them on my test box by
this week?
thanks,
rui
> On 10/01/2023 16:17, Daniel Lezcano wrote:
> > Recently sent as a RFC, the thermal ACPI for generic trip points is
> > a set of
> > functions to fill the generic trip points structure which will
> > become the
> > standard structure for the thermal framework and its users.
> >
> > Different Intel drivers and the ACPI thermal driver are using the
> > ACPI tables to
> > get the thermal zone information. As those are getting the same
> > information,
> > providing this set of ACPI function with the generic trip points
> > will
> > consolidate the code.
> >
> > Also, the Intel PCH and the Intel 34xx drivers are converted to use
> > the generic
> > trip points relying on the ACPI generic trip point parsing
> > functions.
> >
> > These changes have been tested on a Thinkpad Lenovo x280 with the
> > PCH and
> > INT34xx drivers. No regression have been observed, the trip points
> > remain the
> > same for what is described on this system.
> >
> > Changelog:
> > - V4:
> > - Fixed Kconfig option dependency, select THERMAL_ACPI if ACPI
> > is set
> > only for the PCH driver
> >
> > - V3:
> > - Took into account Rafael's comments
> > - Used a silence option THERMAL_ACPI in order to stay
> > consistent
> > with THERMAL_OF. It is up to the API user to select the
> > option.
> >
> > - V2:
> > - Fix the thermal ACPI patch where the thermal_acpi.c was not
> > included in
> > the series
> > - Provide a couple of users of this API which could have been
> > tested on a
> > real system
> >
> > Daniel Lezcano (3):
> > thermal/acpi: Add ACPI trip point routines
> > thermal/drivers/intel: Use generic trip points for intel_pch
> > thermal/drivers/intel: Use generic trip points int340x
> >
> > drivers/thermal/Kconfig | 4 +
> > drivers/thermal/Makefile | 1 +
> > drivers/thermal/intel/Kconfig | 1 +
> > drivers/thermal/intel/int340x_thermal/Kconfig | 1 +
> > .../int340x_thermal/int340x_thermal_zone.c | 177 ++++---------
> > --
> > .../int340x_thermal/int340x_thermal_zone.h | 10 +-
> > drivers/thermal/intel/intel_pch_thermal.c | 88 ++------
> > drivers/thermal/thermal_acpi.c | 211
> > ++++++++++++++++++
> > include/linux/thermal.h | 8 +
> > 9 files changed, 287 insertions(+), 214 deletions(-)
> > create mode 100644 drivers/thermal/thermal_acpi.c
> >
next prev parent reply other threads:[~2023-01-11 14:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 15:17 [PATCH v4 0/3] Thermal ACPI APIs for generic trip points Daniel Lezcano
2023-01-10 15:17 ` [PATCH 1/3] thermal/acpi: Add ACPI trip point routines Daniel Lezcano
2023-01-10 15:17 ` [PATCH 2/3] thermal/drivers/intel: Use generic trip points for intel_pch Daniel Lezcano
2023-01-10 15:17 ` [PATCH 3/3] thermal/drivers/intel: Use generic trip points int340x Daniel Lezcano
2023-01-13 11:41 ` Zhang, Rui
2023-01-13 12:12 ` Daniel Lezcano
2023-01-13 15:48 ` srinivas pandruvada
2023-01-13 17:21 ` Daniel Lezcano
2023-01-13 17:34 ` srinivas pandruvada
2023-01-13 15:44 ` srinivas pandruvada
2023-01-11 11:52 ` [PATCH v4 0/3] Thermal ACPI APIs for generic trip points Daniel Lezcano
2023-01-11 14:49 ` Zhang, Rui [this message]
2023-01-11 15:01 ` Daniel Lezcano
2023-01-12 2:13 ` Zhang, Rui
2023-01-13 11:46 ` Zhang, Rui
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=d51432466ed6b1a8eef0e966bf1b2c2bb2e1e37f.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=daniel.lezcano@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@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).