linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: rafael@kernel.org
Cc: linux-pm@vger.kernel.org, thierry.reding@gmail.com
Subject: Re: [PATCH 0/8] Finish thermal zone structure encapsulation
Date: Tue, 13 Jun 2023 16:12:50 +0200	[thread overview]
Message-ID: <e9d2e286-df54-1b6f-484b-afadaf594e82@linaro.org> (raw)
In-Reply-To: <20230525140135.3589917-1-daniel.lezcano@linaro.org>


Hi Rafael,

On 25/05/2023 16:01, Daniel Lezcano wrote:
> The series are the last changes to self-encapsulate the thermal zone device
> structure in order to protect wild accesses to the thermal zone device
> internals, especially the trip points and the locks.
> 
> Meanwhile the latest changes, a new driver has come via the network tree which
> directly accesses the thermal zone device structure information and uses the
> old thermal_zone_device_register function. The first patch does the change to
> use the accessor and the new registering function. It is expected to have the
> changes to go through the thermal tree along with the other patches.
> 
> The second patch adds a macro to warn at compilation time if the
> thermal_core.h is included in a file not belonging to the thermal core
> code. One warning will happen with the nvidia drivers but this is in
> the way to be solved.
> 
> The third patch reorders the headers inclusion in the core code.
> 
> The fourth patch provides an API to update the thermal trips of a
> thermal zone. This function takes care of the locking and the thermal
> zone update.
> 
> The next patches makes the int340x drivers to use the thermal trip
> update above and the different accessors for thermal zone structure.
> 
> Finally the last patch moves the thermal zone device structure from
> the exported thermal.h header to the thermal core private header.

I think we are all pretty busy for this cycle and that series did not 
raised any comments (yet?).

I would like to go forward with the generic trip points changes and 
finish the conversion so we can fix the trip points monitoring once and 
for all. This series consolidate the self-encapsulation of the thermal 
zone device to prevent changing the trip points directly in the thermal 
zone device structure.

Most of the patches of this series don't have functional changes.

If nobody has concern with it, I propose to pick them up in the next days.

> Daniel Lezcano (8):
>    net/mlx5: Update the driver with the recent thermal changes
>    thermal/core: Hardening the self-encapsulation
>    thermal/core: Reorder the headers inclusion
>    thermal/core: Update the generic trip points
>    thermal/drivers/int3400: Use thermal zone device wrappers
>    thermal/drivers/int340x: Do not check the thermal zone state
>    thermal/drivers/int340x: Use thermal zone device trip update
>    thermal/core: Move the thermal zone structure to the private core
>      header
> 
>   .../net/ethernet/mellanox/mlx5/core/thermal.c | 15 ++--
>   drivers/thermal/gov_bang_bang.c               |  1 +
>   drivers/thermal/gov_fair_share.c              |  1 +
>   drivers/thermal/gov_power_allocator.c         |  7 +-
>   drivers/thermal/gov_step_wise.c               |  1 +
>   drivers/thermal/gov_user_space.c              |  1 +
>   .../intel/int340x_thermal/int3400_thermal.c   | 44 +++++-----
>   .../int340x_thermal/int340x_thermal_zone.c    | 17 ++--
>   drivers/thermal/thermal_acpi.c                |  1 +
>   drivers/thermal/thermal_core.c                | 47 +++++------
>   drivers/thermal/thermal_core.h                | 82 +++++++++++++++++++
>   drivers/thermal/thermal_helpers.c             |  1 +
>   drivers/thermal/thermal_hwmon.c               |  1 +
>   drivers/thermal/thermal_netlink.c             |  1 +
>   drivers/thermal/thermal_of.c                  |  1 +
>   drivers/thermal/thermal_sysfs.c               |  1 +
>   drivers/thermal/thermal_trip.c                | 79 ++++++++++++++++++
>   include/linux/thermal.h                       | 79 +-----------------
>   18 files changed, 241 insertions(+), 139 deletions(-)
> 

-- 
<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


  parent reply	other threads:[~2023-06-13 14:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25 14:01 [PATCH 0/8] Finish thermal zone structure encapsulation Daniel Lezcano
2023-05-25 14:01 ` [PATCH 1/8] net/mlx5: Update the driver with the recent thermal changes Daniel Lezcano
2023-05-26  9:20   ` Simon Horman
2023-05-31 22:10   ` Saeed Mahameed
2023-06-07 13:17     ` Daniel Lezcano
2023-05-25 14:01 ` [PATCH 2/8] thermal/core: Hardening the self-encapsulation Daniel Lezcano
2023-05-25 14:01 ` [PATCH 3/8] thermal/core: Reorder the headers inclusion Daniel Lezcano
2023-05-25 14:01 ` [PATCH 4/8] thermal/core: Update the generic trip points Daniel Lezcano
2023-06-20 11:28   ` Rafael J. Wysocki
2023-06-20 18:35     ` Daniel Lezcano
2023-06-23 17:59       ` Rafael J. Wysocki
2023-06-25 20:29   ` Rafael J. Wysocki
2023-05-25 14:01 ` [PATCH 5/8] thermal/drivers/int3400: Use thermal zone device wrappers Daniel Lezcano
2023-07-03 10:49   ` Daniel Lezcano
2023-07-03 16:15     ` srinivas pandruvada
2023-07-05 10:41       ` Daniel Lezcano
2023-07-05 11:35         ` srinivas pandruvada
2023-07-05 11:49           ` Daniel Lezcano
2023-05-25 14:01 ` [PATCH 6/8] thermal/drivers/int340x: Do not check the thermal zone state Daniel Lezcano
2023-05-25 14:01 ` [PATCH 7/8] thermal/drivers/int340x: Use thermal zone device trip update Daniel Lezcano
2023-05-25 14:01 ` [PATCH 8/8] thermal/core: Move the thermal zone structure to the private core header Daniel Lezcano
2023-06-13 14:12 ` Daniel Lezcano [this message]
2023-06-20 10:54   ` [PATCH 0/8] Finish thermal zone structure encapsulation Rafael J. Wysocki

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=e9d2e286-df54-1b6f-484b-afadaf594e82@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).