Received-SPF: pass (google.com: domain of linux-kernel+bounces-94469-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
 Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
 Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>,
 Daniel Lezcano <daniel.lezcano@linaro.org>,
 Lukasz Luba <lukasz.luba@arm.com>,
 AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Subject: [PATCH v1 0/2] thermal: More separation between the core and drivers
Date: Wed, 06 Mar 2024 20:14:15 +0100
Message-ID: <4558384.LvFx2qVVIh@kreacher>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="UTF-8"

Hi Everyone,

This series is for the next kernel development cycle and I'm sending it
mostly due to the discussion regarding the ordering of trip crossing
notifications:

https://lore.kernel.org/linux-pm/20240306085428.88011-1-daniel.lezcano@linaro.org/

because the solution of the ordering problem I have in the works is
based on it.

Still, please review it and/or test it if you can and let me know if you
discover any problems related to it (I'm not seeing any issues with it now).

Patch [1/2] is based on the observation that the threshold field in struct
thermal_trip really should be core-internal and to make that happen it
introduces a wrapper structure around struct thermal_trip for internal
use in the core.

Patch [2/2] moves the definition of the new structure and the struct
thermal_zone_device one to a local header file in the core to enforce
more separation between the core and drivers.

The patches are not expected to introduce any observable differences in
behavior, so please let me know if you see any of that.

They are based on the thermal material currently in linux-next and I'm
going to create a separate test git branch with them.

Thanks!