linux-kernel - Re: [PATCH v2 2/2] thermal/drivers/imx: Use the thermal framework for the trip point

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAOMZO5CdLXMtBbdH1j1RLFL=t5ZGXVgi5=Aw5pde1QNcCAVKxQ@mail.gmail.com>
Date:   Thu, 9 Mar 2023 07:45:14 -0300
From:   Fabio Estevam <festevam@...il.com>
To:     Daniel Lezcano <daniel.lezcano@...aro.org>
Cc:     rafael@...nel.org, linux-pm@...r.kernel.org,
        linux-kernel@...r.kernel.org, Amit Kucheria <amitk@...nel.org>,
        Zhang Rui <rui.zhang@...el.com>,
        Shawn Guo <shawnguo@...nel.org>,
        Sascha Hauer <s.hauer@...gutronix.de>,
        Pengutronix Kernel Team <kernel@...gutronix.de>,
        NXP Linux Team <linux-imx@....com>,
        "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2 2/2] thermal/drivers/imx: Use the thermal framework for
 the trip point

On Thu, Mar 9, 2023 at 6:28 AM Daniel Lezcano <daniel.lezcano@...aro.org> wrote:
>
> The thermal framework provides an API to get the trip related to a
> trip point id. We want to consolidate the generic trip points code,
> thus preventing the different drivers to deal with the trip points
> after they registered them.
>
> The set_trip_temp ops will be changed regarding the above changes but
> first we need to rework a bit the different implementation in the
> drivers.
>
> The goal is to prevent using the trip id but use a trip point passed
> as parameter which will contain all the needed information.
>
> As we don't have the trip point passed as parameter yet, we get the
> trip point using the generic trip thermal framewrok APIs and use it to
> take exactly the same decisions.
>
> The difference with this change and the previous code is from where we
> get the thermal trip point (which is the same).
>
> No functional change intended.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@...aro.org>
> ---
>   V2:
>     - Remove extra tab inserted in the previous version

Reviewed-by: Fabio Estevam <festevam@...il.com>