Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Zhang Rui <rui.zhang@intel.com>
Cc: jdelvare@suse.com, fenghua.yu@intel.com,
	linux-hwmon@vger.kernel.org, srinivas.pandruvada@linux.intel.com
Subject: Re: [PATCH 1/3] hwmon (coretemp): Remove obsolete temp_data->valid
Date: Fri, 11 Nov 2022 13:14:32 -0800	[thread overview]
Message-ID: <20221111211432.GA1059403@roeck-us.net> (raw)
In-Reply-To: <20221108075051.5139-2-rui.zhang@intel.com>

On Tue, Nov 08, 2022 at 03:50:49PM +0800, Zhang Rui wrote:
> Checking for the valid bit of IA32_THERM_STATUS is removed in commit
> bf6ea084ebb5 ("hwmon: (coretemp) Do not return -EAGAIN for low
> temperatures"), and temp_data->valid is set and never cleared when the
> temperature has been read once.
> 
> Remove the obsolete temp_data->valid field.
> 
> Signed-off-by: Zhang Rui <rui.zhang@intel.com>

Applied to hwmon-next.

Thanks,
Guenter

> ---
>  drivers/hwmon/coretemp.c | 5 +----
>  1 file changed, 1 insertion(+), 4 deletions(-)
> 
> diff --git a/drivers/hwmon/coretemp.c b/drivers/hwmon/coretemp.c
> index 8bf32c6c85d9..ec35ada68455 100644
> --- a/drivers/hwmon/coretemp.c
> +++ b/drivers/hwmon/coretemp.c
> @@ -64,7 +64,6 @@ MODULE_PARM_DESC(tjmax, "TjMax value in degrees Celsius");
>   * @attr_size:  Total number of pre-core attrs displayed in the sysfs.
>   * @is_pkg_data: If this is 1, the temp_data holds pkgtemp data.
>   *		Otherwise, temp_data holds coretemp data.
> - * @valid: If this is 1, the current temperature is valid.
>   */
>  struct temp_data {
>  	int temp;
> @@ -76,7 +75,6 @@ struct temp_data {
>  	u32 status_reg;
>  	int attr_size;
>  	bool is_pkg_data;
> -	bool valid;
>  	struct sensor_device_attribute sd_attrs[TOTAL_ATTRS];
>  	char attr_name[TOTAL_ATTRS][CORETEMP_NAME_LENGTH];
>  	struct attribute *attrs[TOTAL_ATTRS + 1];
> @@ -157,7 +155,7 @@ static ssize_t show_temp(struct device *dev,
>  	mutex_lock(&tdata->update_lock);
>  
>  	/* Check whether the time interval has elapsed */
> -	if (!tdata->valid || time_after(jiffies, tdata->last_updated + HZ)) {
> +	if (time_after(jiffies, tdata->last_updated + HZ)) {
>  		rdmsr_on_cpu(tdata->cpu, tdata->status_reg, &eax, &edx);
>  		/*
>  		 * Ignore the valid bit. In all observed cases the register
> @@ -166,7 +164,6 @@ static ssize_t show_temp(struct device *dev,
>  		 * really help at all.
>  		 */
>  		tdata->temp = tdata->tjmax - ((eax >> 16) & 0x7f) * 1000;
> -		tdata->valid = true;
>  		tdata->last_updated = jiffies;
>  	}
>  

  reply	other threads:[~2022-11-11 21:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08  7:50 [PATCH 0/3] hwmon (coretemp): Add support for dynamic tjmax/ttarget Zhang Rui
2022-11-08  7:50 ` [PATCH 1/3] hwmon (coretemp): Remove obsolete temp_data->valid Zhang Rui
2022-11-11 21:14   ` Guenter Roeck [this message]
2022-11-08  7:50 ` [PATCH 2/3] hwmon (coretemp): Add support for dynamic tjmax Zhang Rui
2022-11-11 21:26   ` Guenter Roeck
2022-11-08  7:50 ` [PATCH 3/3] hwmon (coretemp): Add support for dynamic ttarget Zhang Rui
2022-11-11 21:34   ` Guenter Roeck
2022-11-12  8:37     ` Zhang Rui
2022-11-12 15:10       ` Guenter Roeck

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=20221111211432.GA1059403@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=fenghua.yu@intel.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    --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