public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Eddie James <eajames@linux.ibm.com>
Cc: jdelvare@suse.com, linux-hwmon@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (occ) Fix P10 VRM temp sensors
Date: Sat, 2 Oct 2021 04:36:02 -0700	[thread overview]
Message-ID: <20211002113602.GA894333@roeck-us.net> (raw)
In-Reply-To: <20210929153604.14968-1-eajames@linux.ibm.com>

On Wed, Sep 29, 2021 at 10:36:04AM -0500, Eddie James wrote:
> The P10 (temp sensor version 0x10) doesn't do the same VRM status
> reporting that was used on P9. It just reports the temperature, so
> drop the check for VRM fru type in the sysfs show function, and don't
> set the name to "alarm".
> 
> Fixes: db4919ec86 ("hwmon: (occ) Add new temperature sensor type")
> Signed-off-by: Eddie James <eajames@linux.ibm.com>

Applied.

Thanks,
Guenter

> ---
>  drivers/hwmon/occ/common.c | 17 +++++------------
>  1 file changed, 5 insertions(+), 12 deletions(-)
> 
> diff --git a/drivers/hwmon/occ/common.c b/drivers/hwmon/occ/common.c
> index 0d68a78be980..ae664613289c 100644
> --- a/drivers/hwmon/occ/common.c
> +++ b/drivers/hwmon/occ/common.c
> @@ -340,18 +340,11 @@ static ssize_t occ_show_temp_10(struct device *dev,
>  		if (val == OCC_TEMP_SENSOR_FAULT)
>  			return -EREMOTEIO;
>  
> -		/*
> -		 * VRM doesn't return temperature, only alarm bit. This
> -		 * attribute maps to tempX_alarm instead of tempX_input for
> -		 * VRM
> -		 */
> -		if (temp->fru_type != OCC_FRU_TYPE_VRM) {
> -			/* sensor not ready */
> -			if (val == 0)
> -				return -EAGAIN;
> +		/* sensor not ready */
> +		if (val == 0)
> +			return -EAGAIN;
>  
> -			val *= 1000;
> -		}
> +		val *= 1000;
>  		break;
>  	case 2:
>  		val = temp->fru_type;
> @@ -886,7 +879,7 @@ static int occ_setup_sensor_attrs(struct occ *occ)
>  					     0, i);
>  		attr++;
>  
> -		if (sensors->temp.version > 1 &&
> +		if (sensors->temp.version == 2 &&
>  		    temp->fru_type == OCC_FRU_TYPE_VRM) {
>  			snprintf(attr->name, sizeof(attr->name),
>  				 "temp%d_alarm", s);

      reply	other threads:[~2021-10-02 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29 15:36 [PATCH] hwmon: (occ) Fix P10 VRM temp sensors Eddie James
2021-10-02 11:36 ` Guenter Roeck [this message]

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=20211002113602.GA894333@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=eajames@linux.ibm.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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