From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Manaf Meethalavalappu Pallikunhi <quic_manafm@quicinc.com>,
"Zhang, Rui" <rui.zhang@intel.com>,
Amit Kucheria <amitk@kernel.org>,
Lukasz Luba <lukasz.luba@arm.com>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 3/4] thermal/core: Build ascending ordered indexes for the trip points
Date: Thu, 21 Jul 2022 12:59:01 +0200 [thread overview]
Message-ID: <117c778a-4496-4d49-e73d-06fa3efa4d09@linaro.org> (raw)
In-Reply-To: <CAJZ5v0hj0kMRNBqO_0SqsAAY8Rb8h2NrWOYogDLgGZnCtiTEwg@mail.gmail.com>
On 19/07/2022 20:56, Rafael J. Wysocki wrote:
> On Mon, Jul 18, 2022 at 4:50 PM Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
>>
>> By convention the trips points are declared in the ascending
>> temperature order. However, no specification for the device tree, ACPI
>> or documentation tells the trip points must be ordered this way.
>>
>> In the other hand, we need those to be ordered to browse them at the
>
> s/In/On/
>
>> thermal events.
>
> What if they are all inspected every time?
My bad, my sentence is confusing. The trip point are browsed every time
and we need to have them ordered to detect correctly the thermal events.
>> But if we assume they are ordered and change the code
>> based on this assumption, any platform with shuffled trip points
>> description will be broken (if they exist).
>>
>> Instead of taking the risk of breaking the existing platforms, use an
>> array of temperature ordered trip identifiers and make it available
>> for the code needing to browse the trip points in an ordered way.
>
> Well, having ops->get_trip_temp() suggests that the trip temperatures
> can be dynamic. Is the ordering guaranteed to be preserved in that
> case?
The number of trips can not be changed. It is fixed when the thermal
zone is created AFAICT. The get_trip_temp() is just a way to let the
different driver declare their own trip structure which is actually
something I'm trying to fix by moving the structure thermal_trip inside
the thermal zone. But that is a longer and separate work.
> Anyway, if they need to be sorted, why don't we just sort them
> properly instead of adding this extra array?
We can not because ATM the trip points array is private to the different
sensors.
[ ... ]
--
<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
next prev parent reply other threads:[~2022-07-21 10:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 14:50 [PATCH v4 1/4] thermal/core: Encapsulate the trip point crossed function Daniel Lezcano
2022-07-18 14:50 ` [PATCH v4 2/4] thermal/core: Avoid calling ->get_trip_temp() unnecessarily Daniel Lezcano
2022-07-25 16:30 ` Daniel Lezcano
2022-07-18 14:50 ` [PATCH v4 3/4] thermal/core: Build ascending ordered indexes for the trip points Daniel Lezcano
2022-07-19 18:56 ` Rafael J. Wysocki
2022-07-21 10:59 ` Daniel Lezcano [this message]
2022-07-21 11:25 ` Rafael J. Wysocki
2022-07-21 21:15 ` Daniel Lezcano
2022-07-22 17:40 ` Rafael J. Wysocki
2022-07-25 16:29 ` Daniel Lezcano
2022-07-25 16:35 ` Daniel Lezcano
2022-07-18 14:50 ` [PATCH v4 4/4] thermal/core: Fix thermal trip cross point 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=117c778a-4496-4d49-e73d-06fa3efa4d09@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=amitk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=quic_manafm@quicinc.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@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®