[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZQqpbSYsUdAZrcrT@shredder>
Date: Wed, 20 Sep 2023 11:12:29 +0300
From: Ido Schimmel <idosch@...dia.com>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Linux PM <linux-pm@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Zhang Rui <rui.zhang@...el.com>,
Daniel Lezcano <daniel.lezcano@...aro.org>
Subject: Re: [PATCH v1] thermal: core: Drop trips_disabled bitmask
On Tue, Sep 19, 2023 at 08:54:37PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
>
> After recent changes, thermal_zone_get_trip() cannot fail, as invoked
> from thermal_zone_device_register_with_trips(), so the only role of
> the trips_disabled bitmask is struct thermal_zone_device is to make
> handle_thermal_trip() skip trip points whose temperature was initially
> zero. However, since the unit of temperature in the thermal core is
> millicelsius, zero may very well be a valid temperature value at least
> in some usage scenarios and the trip temperature may as well change
> later. Thus there is no reason to permanently disable trip points
> with initial temperature equal to zero.
>
> Accordingly, drop the trips_disabled bitmask along with the code
> related to it.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
I guess I was copied because of commit f1b80a3878b2 ("thermal: core:
Restore behavior regarding invalid trip points"). Since then we stopped
relying on this behavior with commit 5601ef91fba8 ("mlxsw: core_thermal:
Use static trip points for transceiver modules").
Tested your patch and didn't see any regressions:
Tested-by: Ido Schimmel <idosch@...dia.com>
Thanks
Powered by blists - more mailing lists