Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Vadim Pasternak <vadimp@nvidia.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH hwmon 1/1] hwmon: (mlxreg-fan) Return zero speed for broken fan
Date: Sun, 12 Feb 2023 07:22:07 -0800	[thread overview]
Message-ID: <b13231fb-a0e9-b8f6-ebee-40ba9cc40cb4@roeck-us.net> (raw)
In-Reply-To: <20230212145730.24247-1-vadimp@nvidia.com>

On 2/12/23 06:57, Vadim Pasternak wrote:
> Currently for broken fan driver returns value calculated based on error
> code (0xFF) in related fan speed register.
> Thus, for such fan user gets fan{n}_fault to 1 and fan{n}_input with
> misleading value.
> 
> Add check for fan fault prior return speed value and return zero if
> fault is detected.
> 
> Fixes: 65afb4c8e7e4 ("hwmon: (mlxreg-fan) Add support for Mellanox FAN driver")
> Signed-off-by: Vadim Pasternak <vadimp@nvidia.com>

Applied.

Thanks,
Guenter

> ---
>   drivers/hwmon/mlxreg-fan.c | 6 ++++++
>   1 file changed, 6 insertions(+)
> 
> diff --git a/drivers/hwmon/mlxreg-fan.c b/drivers/hwmon/mlxreg-fan.c
> index b48bd7c961d6..96017cc8da7e 100644
> --- a/drivers/hwmon/mlxreg-fan.c
> +++ b/drivers/hwmon/mlxreg-fan.c
> @@ -155,6 +155,12 @@ mlxreg_fan_read(struct device *dev, enum hwmon_sensor_types type, u32 attr,
>   			if (err)
>   				return err;
>   
> +			if (MLXREG_FAN_GET_FAULT(regval, tacho->mask)) {
> +				/* FAN is broken - return zero for FAN speed. */
> +				*val = 0;
> +				return 0;
> +			}
> +
>   			*val = MLXREG_FAN_GET_RPM(regval, fan->divider,
>   						  fan->samples);
>   			break;


      reply	other threads:[~2023-02-12 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-12 14:57 [PATCH hwmon 1/1] hwmon: (mlxreg-fan) Return zero speed for broken fan Vadim Pasternak
2023-02-12 15:22 ` 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=b13231fb-a0e9-b8f6-ebee-40ba9cc40cb4@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=vadimp@nvidia.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