netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux PM <linux-pm@vger.kernel.org>,
	Miri Korenblit <miriam.rachel.korenblit@intel.com>,
	Lukasz Luba <lukasz.luba@arm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Zhang Rui <rui.zhang@intel.com>,
	netdev@vger.kernel.org, Ido Schimmel <idosch@nvidia.com>,
	Petr Machata <petrm@nvidia.com>,
	linux-wireless@vger.kernel.org, Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Manaf Meethalavalappu Pallikunhi <quic_manafm@quicinc.com>
Subject: Re: [PATCH v1 6/9] iwlwifi: mvm: Set THERMAL_TRIP_WRITABLE_TEMP directly
Date: Fri, 9 Feb 2024 15:49:51 +0100	[thread overview]
Message-ID: <ZcY7jyyFJq1yfOCj@linux.intel.com> (raw)
In-Reply-To: <3757041.MHq7AAxBmi@kreacher>

On Fri, Feb 09, 2024 at 03:10:24PM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> 
> It is now possible to flag trip points with THERMAL_TRIP_WRITABLE_TEMP
> to allow their temperature to be set from user space via sysfs instead
> of using a nonzero writable trips mask during thermal zone registration,
> so make the iwlwifi code do that.
> 
> No intentional functional impact.
> 
> Note that this change is requisite for dropping the mask argument from
> thermal_zone_device_register_with_trips() going forward.
> 
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> 
> This patch obviously depends on
> 
> https://patchwork.kernel.org/project/linux-pm/patch/8346768.T7Z3S40VBb@kreacher/
> 
> which has been queued up for 6.9 already.
> 
> ---
>  drivers/net/wireless/intel/iwlwifi/mvm/tt.c |    6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> Index: linux-pm/drivers/net/wireless/intel/iwlwifi/mvm/tt.c
> ===================================================================
> --- linux-pm.orig/drivers/net/wireless/intel/iwlwifi/mvm/tt.c
> +++ linux-pm/drivers/net/wireless/intel/iwlwifi/mvm/tt.c
> @@ -667,9 +667,6 @@ static  struct thermal_zone_device_ops t
>  	.set_trip_temp = iwl_mvm_tzone_set_trip_temp,
>  };
>  
> -/* make all trips writable */
> -#define IWL_WRITABLE_TRIPS_MSK (BIT(IWL_MAX_DTS_TRIPS) - 1)
> -
>  static void iwl_mvm_thermal_zone_register(struct iwl_mvm *mvm)
>  {
>  	int i, ret;
> @@ -692,11 +689,12 @@ static void iwl_mvm_thermal_zone_registe
>  	for (i = 0 ; i < IWL_MAX_DTS_TRIPS; i++) {
>  		mvm->tz_device.trips[i].temperature = THERMAL_TEMP_INVALID;
>  		mvm->tz_device.trips[i].type = THERMAL_TRIP_PASSIVE;
> +		mvm->tz_device.trips[i].type = THERMAL_TRIP_WRITABLE_TEMP;

		mvm->tz_device.trips[i].flags = THERMAL_TRIP_WRITABLE_TEMP;

Consider using diffrent prefix for constants to diffrenciate flags and types.

Regards
Stanislaw

>  	}
>  	mvm->tz_device.tzone = thermal_zone_device_register_with_trips(name,
>  							mvm->tz_device.trips,
>  							IWL_MAX_DTS_TRIPS,
> -							IWL_WRITABLE_TRIPS_MSK,
> +							0,
>  							mvm, &tzone_ops,
>  							NULL, 0, 0);
>  	if (IS_ERR(mvm->tz_device.tzone)) {
> 
> 
> 

  reply	other threads:[~2024-02-09 14:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 14:02 [PATCH v1 0/9] thermal: Writable trip points handling rework Rafael J. Wysocki
2024-02-09 14:05 ` [PATCH v1 1/9] thermal: Get rid of CONFIG_THERMAL_WRITABLE_TRIPS Rafael J. Wysocki
2024-02-09 14:06 ` [PATCH v1 2/9] thermal: core: Add flags to struct thermal_trip Rafael J. Wysocki
2024-02-09 14:06 ` [PATCH v1 3/9] thermal: core: Drop the .set_trip_hyst() thermal zone operation Rafael J. Wysocki
2024-02-09 14:07 ` [PATCH v1 4/9] thermal: intel: Set THERMAL_TRIP_WRITABLE_TEMP directly Rafael J. Wysocki
2024-02-09 14:08 ` [PATCH v1 5/9] mlxsw: core_thermal: " Rafael J. Wysocki
2024-02-11 15:16   ` Ido Schimmel
2024-02-09 14:10 ` [PATCH v1 6/9] iwlwifi: mvm: " Rafael J. Wysocki
2024-02-09 14:49   ` Stanislaw Gruszka [this message]
2024-02-09 16:15     ` Rafael J. Wysocki
2024-02-09 16:27       ` Stanislaw Gruszka
2024-02-12 10:31       ` Johannes Berg
2024-02-12 12:03         ` Rafael J. Wysocki
2024-02-12  7:30   ` Kalle Valo
2024-02-12 12:01     ` Rafael J. Wysocki
2024-02-09 14:11 ` [PATCH v1 7/9] thermal: imx: " Rafael J. Wysocki
2024-02-09 14:12 ` [PATCH v1 8/9] thermal: of: " Rafael J. Wysocki
2024-02-09 14:14 ` [PATCH v1 9/9] thermal: core: Eliminate writable trip points masks 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=ZcY7jyyFJq1yfOCj@linux.intel.com \
    --to=stanislaw.gruszka@linux.intel.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=idosch@nvidia.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=miriam.rachel.korenblit@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=petrm@nvidia.com \
    --cc=quic_manafm@quicinc.com \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=srinivas.pandruvada@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;
as well as URLs for NNTP newsgroup(s).