public inbox for linux-hwmon@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Zev Weiss <zev@bewilderbeest.net>
Cc: Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
	openbmc@lists.ozlabs.org
Subject: Re: [PATCH] hwmon: (pmbus) delta-ahe50dc-fan: work around hardware quirk
Date: Wed, 27 Apr 2022 04:53:33 -0700	[thread overview]
Message-ID: <20220427115333.GA2686708@roeck-us.net> (raw)
In-Reply-To: <20220427035109.3819-1-zev@bewilderbeest.net>

On Tue, Apr 26, 2022 at 08:51:09PM -0700, Zev Weiss wrote:
> CLEAR_FAULTS commands can apparently sometimes trigger catastrophic
> power output glitches on the ahe-50dc, so block them from being sent
> at all.
> 
> Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
> Cc: stable@vger.kernel.org

Applied.

Thanks,
Guenter

> ---
>  drivers/hwmon/pmbus/delta-ahe50dc-fan.c | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/drivers/hwmon/pmbus/delta-ahe50dc-fan.c b/drivers/hwmon/pmbus/delta-ahe50dc-fan.c
> index 40dffd9c4cbf..f546f0c12497 100644
> --- a/drivers/hwmon/pmbus/delta-ahe50dc-fan.c
> +++ b/drivers/hwmon/pmbus/delta-ahe50dc-fan.c
> @@ -14,6 +14,21 @@
>  
>  #define AHE50DC_PMBUS_READ_TEMP4 0xd0
>  
> +static int ahe50dc_fan_write_byte(struct i2c_client *client, int page, u8 value)
> +{
> +	/*
> +	 * The CLEAR_FAULTS operation seems to sometimes (unpredictably, perhaps
> +	 * 5% of the time or so) trigger a problematic phenomenon in which the
> +	 * fan speeds surge momentarily and at least some (perhaps all?) of the
> +	 * system's power outputs experience a glitch.
> +	 *
> +	 * However, according to Delta it should be OK to simply not send any
> +	 * CLEAR_FAULTS commands (the device doesn't seem to be capable of
> +	 * reporting any faults anyway), so just blackhole them unconditionally.
> +	 */
> +	return value == PMBUS_CLEAR_FAULTS ? -EOPNOTSUPP : -ENODATA;
> +}
> +
>  static int ahe50dc_fan_read_word_data(struct i2c_client *client, int page, int phase, int reg)
>  {
>  	/* temp1 in (virtual) page 1 is remapped to mfr-specific temp4 */
> @@ -68,6 +83,7 @@ static struct pmbus_driver_info ahe50dc_fan_info = {
>  		PMBUS_HAVE_VIN | PMBUS_HAVE_FAN12 | PMBUS_HAVE_FAN34 |
>  		PMBUS_HAVE_STATUS_FAN12 | PMBUS_HAVE_STATUS_FAN34 | PMBUS_PAGE_VIRTUAL,
>  	.func[1] = PMBUS_HAVE_TEMP | PMBUS_PAGE_VIRTUAL,
> +	.write_byte = ahe50dc_fan_write_byte,
>  	.read_word_data = ahe50dc_fan_read_word_data,
>  };
>  

      reply	other threads:[~2022-04-27 11:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27  3:51 [PATCH] hwmon: (pmbus) delta-ahe50dc-fan: work around hardware quirk Zev Weiss
2022-04-27 11:53 ` 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=20220427115333.GA2686708@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=zev@bewilderbeest.net \
    /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