Linux Power Management development
 help / color / mirror / Atom feed
From: "Zhang, Rui" <rui.zhang@intel.com>
To: "ricardo.neri-calderon@linux.intel.com"
	<ricardo.neri-calderon@linux.intel.com>,
	"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>
Cc: "srinivas.pandruvada@linux.intel.com"
	<srinivas.pandruvada@linux.intel.com>,
	"Brown, Len" <len.brown@intel.com>,
	"stanislaw.gruszka@linux.intel.com"
	<stanislaw.gruszka@linux.intel.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Neri, Ricardo" <ricardo.neri@intel.com>
Subject: Re: [PATCH v2 3/4] thermal: intel: hfi: Rename HFI_MAX_THERM_NOTIFY_COUNT
Date: Wed, 8 May 2024 04:46:49 +0000	[thread overview]
Message-ID: <971f68f994de1842fff0569a49e87356e835e03b.camel@intel.com> (raw)
In-Reply-To: <20240508034352.18414-4-ricardo.neri-calderon@linux.intel.com>

On Tue, 2024-05-07 at 20:43 -0700, Ricardo Neri wrote:
> When processing a hardware update, HFI generates as many thermal
> netlink
> events as needed to relay all the updated CPU capabilities to user
> space.
> The constant HFI_MAX_THERM_NOTIFY_COUNT is the number of CPU
> capabilities
> updated per each of those events.
> 
> Give this constant a more descriptive name.
> 
> Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>

Acked-by: Zhang Rui <rui.zhang@intel.com>

-rui
> ---
> Cc: Len Brown <len.brown@intel.com>
> Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> Cc: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
> Cc: Zhang Rui <rui.zhang@intel.com>
> Cc: linux-pm@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> ---
> Changes since v1:
>  * None
> ---
>  drivers/thermal/intel/intel_hfi.c | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/thermal/intel/intel_hfi.c
> b/drivers/thermal/intel/intel_hfi.c
> index d82b8788b0f8..c6658f8c5cca 100644
> --- a/drivers/thermal/intel/intel_hfi.c
> +++ b/drivers/thermal/intel/intel_hfi.c
> @@ -167,7 +167,7 @@ static DEFINE_MUTEX(hfi_instance_lock);
>  
>  static struct workqueue_struct *hfi_updates_wq;
>  #define HFI_UPDATE_DELAY_MS            100
> -#define HFI_MAX_THERM_NOTIFY_COUNT     16
> +#define HFI_THERMNL_CAPS_PER_EVENT     16
>  
>  static void get_hfi_caps(struct hfi_instance *hfi_instance,
>                          struct thermal_genl_cpu_caps *cpu_caps)
> @@ -218,14 +218,14 @@ static void update_capabilities(struct
> hfi_instance *hfi_instance)
>  
>         get_hfi_caps(hfi_instance, cpu_caps);
>  
> -       if (cpu_count < HFI_MAX_THERM_NOTIFY_COUNT)
> +       if (cpu_count < HFI_THERMNL_CAPS_PER_EVENT)
>                 goto last_cmd;
>  
> -       /* Process complete chunks of HFI_MAX_THERM_NOTIFY_COUNT
> capabilities. */
> +       /* Process complete chunks of HFI_THERMNL_CAPS_PER_EVENT
> capabilities. */
>         for (i = 0;
> -            (i + HFI_MAX_THERM_NOTIFY_COUNT) <= cpu_count;
> -            i += HFI_MAX_THERM_NOTIFY_COUNT)
> -
>                thermal_genl_cpu_capability_event(HFI_MAX_THERM_NOTIFY_
> COUNT,
> +            (i + HFI_THERMNL_CAPS_PER_EVENT) <= cpu_count;
> +            i += HFI_THERMNL_CAPS_PER_EVENT)
> +               thermal_genl_cpu_capability_event(HFI_THERMNL_CAPS_PE
> R_EVENT,
>                                                   &cpu_caps[i]);
>  
>         cpu_count = cpu_count - i;


  reply	other threads:[~2024-05-08  4:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08  3:43 [PATCH v2 0/4] thermal: intel: hfi: Update thermal netlink parameters Ricardo Neri
2024-05-08  3:43 ` [PATCH v2 1/4] thermal: intel: hfi: Rename HFI_UPDATE_INTERVAL Ricardo Neri
2024-05-08  3:43 ` [PATCH v2 2/4] thermal: intel: hfi: Shorten the thermal netlink event delay to 100ms Ricardo Neri
2024-05-08  4:45   ` Zhang, Rui
2024-05-08  3:43 ` [PATCH v2 3/4] thermal: intel: hfi: Rename HFI_MAX_THERM_NOTIFY_COUNT Ricardo Neri
2024-05-08  4:46   ` Zhang, Rui [this message]
2024-05-08  3:43 ` [PATCH v2 4/4] thermal: intel: hfi: Increase the number of CPU capabilities per netlink event Ricardo Neri
2024-05-08  4:47   ` Zhang, Rui
2024-05-08 13:48 ` [PATCH v2 0/4] thermal: intel: hfi: Update thermal netlink parameters 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=971f68f994de1842fff0569a49e87356e835e03b.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=ricardo.neri-calderon@linux.intel.com \
    --cc=ricardo.neri@intel.com \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=stanislaw.gruszka@linux.intel.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