From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: srinivas.pandruvada@linux.intel.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Add ACPI trip points parser helpers
Date: Wed, 14 Dec 2022 15:42:04 +0100 [thread overview]
Message-ID: <4507a68d-6d46-927a-ee74-7245764d4edf@linaro.org> (raw)
In-Reply-To: <CAJZ5v0h4RCnGv2C+x1m_Uvu5Hmy273wHDLNzYUuJxT_GFxS5qQ@mail.gmail.com>
On 14/12/2022 15:10, Rafael J. Wysocki wrote:
> On Mon, Dec 12, 2022 at 9:59 PM Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
>>
>> Regarding thermal, the ACPI code parsing the trip points is duplicated
>> inside different Intel drivers. The generic ACPI thermal driver also
>> duplicates this code.
>>
>> Those ACPI parsing actions are used to define trip points and these
>> ones are defined by, and specific to, the backend driver.
>>
>> The different get_trip_* ops, also very similar between each other,
>> are using the specific trip point structure to return the requested
>> trip point information.
>>
>> From there, there is nothing new, all this can be converted to the
>> generic trip point.
>>
>> The first patch provides the functions to parse trip point description
>> from the ACPI table but based on the generic trip point structure. The
>> other patches convert the different Intel driver to use the ACPI
>> functions along with a migration to the generic trip point.
>
> First off, please resend this series with CCs to linux-acpi.
>
> Second, what does it depend on? I think that it depends on the new
> material that hasn't been integrated yet, doesn't it?
Right, I assumed the generic trip points series was in the way to be
integrated
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2022-12-14 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 20:58 Daniel Lezcano
2022-12-12 20:58 ` [PATCH 1/5] thermal/acpi: Add ACPI trip point routines Daniel Lezcano
2022-12-12 20:58 ` [PATCH 2/5] thermal/drivers/intel: Use generic trip points for intel_pch Daniel Lezcano
2022-12-12 20:58 ` [PATCH 3/5] thermal/drivers/intel: Use generic trip points int340x Daniel Lezcano
2022-12-12 20:58 ` [PATCH 4/5] thermal/drivers/intel: Use generic trip points for quark_dts Daniel Lezcano
2022-12-12 20:58 ` [PATCH 5/5] thermal/drivers/intel: Use generic trip points for processor_thermal_device_pci Daniel Lezcano
2022-12-14 14:10 ` [PATCH 0/5] Add ACPI trip points parser helpers Rafael J. Wysocki
2022-12-14 14:42 ` Daniel Lezcano [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=4507a68d-6d46-927a-ee74-7245764d4edf@linaro.org \
--to=daniel.lezcano@linaro.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
all inboxes | Powered by JetHome®