From: Zhang Rui <rui.zhang@intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>, rafael@kernel.org
Cc: quic_manafm@quicinc.com, amitk@kernel.org, lukasz.luba@arm.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/4] thermal/core: Build ascending ordered indexes for the trip points
Date: Tue, 19 Jul 2022 09:07:01 +0800 [thread overview]
Message-ID: <b83d6630bb133b2c02b4a4e5e7777ad27f8fe159.camel@intel.com> (raw)
In-Reply-To: <387c126a-0106-2227-4b4a-db284965b6ca@linaro.org>
On Mon, 2022-07-18 at 16:32 +0200, Daniel Lezcano wrote:
> On 18/07/2022 07:28, Zhang Rui wrote:
> > On Fri, 2022-07-15 at 23:09 +0200, Daniel Lezcano 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
> > > 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.
> > >
> > > Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>
> [ ... ]
>
> > > +static void sort_trips_indexes(struct thermal_zone_device *tz)
> > > +{
> > > + int i, j;
> > > +
> > > + for (i = 0; i < tz->trips; i++)
> > > + tz->trips_indexes[i] = i;
> > > +
> > > + for (i = 0; i < tz->trips; i++) {
> > > + for (j = i + 1; j < tz->trips; j++) {
> > > + int t1, t2;
> > > +
> > > + tz->ops->get_trip_temp(tz, tz-
> > > > trips_indexes[i], &t1);
> >
> > This line can be moved to the upper loop.
> >
> > > + tz->ops->get_trip_temp(tz, tz-
> > > > trips_indexes[j], &t2);
>
>
> Actually, we can not move the line up because of the swap below
Oh, right.
But I still think that we should check the disabled trips as well as
the .get_trip_temp() return value here, or else, we may comparing some
random trip_temp value here.
thanks,
rui
>
> > > + if (t1 > t2)
> > > + swap(tz->trips_indexes[i], tz-
> > > > trips_indexes[j]);
> > > + }
> > > + }
> > > +}
>
>
>
>
next prev parent reply other threads:[~2022-07-19 1:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 21:09 [PATCH v3 1/4] thermal/core: Encapsulate the trip point crossed function Daniel Lezcano
2022-07-15 21:09 ` [PATCH v3 2/4] thermal/core: Avoid calling ->get_trip_temp() unnecessarily Daniel Lezcano
2022-07-18 4:59 ` Zhang Rui
2022-07-18 14:04 ` Daniel Lezcano
2022-07-19 1:01 ` Zhang Rui
2022-07-15 21:09 ` [PATCH v3 3/4] thermal/core: Build ascending ordered indexes for the trip points Daniel Lezcano
2022-07-18 5:28 ` Zhang Rui
2022-07-18 13:21 ` Daniel Lezcano
2022-07-19 1:14 ` Zhang Rui
2022-07-19 1:35 ` Zhang Rui
2022-07-19 7:22 ` Daniel Lezcano
2022-07-19 14:17 ` Zhang Rui
2022-07-21 9:34 ` Daniel Lezcano
2022-07-22 7:15 ` Zhang, Rui
2022-07-22 16:49 ` Rafael J. Wysocki
2022-07-18 14:32 ` Daniel Lezcano
2022-07-19 1:07 ` Zhang Rui [this message]
2022-07-15 21:09 ` [PATCH v3 4/4] thermal/core: Fix thermal trip cross point Daniel Lezcano
2022-07-18 5:30 ` Zhang Rui
2022-07-24 13:26 ` [thermal/core] 3c3e786e2b: BUG:KASAN:slab-out-of-bounds_in_handle_thermal_trip kernel test robot
2023-10-26 18:37 ` [PATCH v3 4/4] thermal/core: Fix thermal trip cross point Rafael J. Wysocki
2022-07-18 4:58 ` [PATCH v3 1/4] thermal/core: Encapsulate the trip point crossed function 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=b83d6630bb133b2c02b4a4e5e7777ad27f8fe159.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.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 \
/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).