From: Guenter Roeck <linux@roeck-us.net>
To: Matthew Barth <msbarth@linux.ibm.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
jdelvare@suse.com
Cc: joel@jms.id.au, andrew@aj.id.au
Subject: Re: [PATCH] pmbus:max31785: Support revision "B"
Date: Mon, 1 Feb 2021 11:43:15 -0800 [thread overview]
Message-ID: <96fd0466-13be-dea1-985c-19cccbd3d321@roeck-us.net> (raw)
In-Reply-To: <20210201165043.36751-1-msbarth@linux.ibm.com>
On 2/1/21 8:50 AM, Matthew Barth wrote:
> There was an issue in how the tach feedbacks of dual rotor fans were
> reported during any change in fan speeds with revision "A" of the
> MAX31785. When the fan speeds would transition to a new target speed,
> the rotor not wired to the TACH input when TACHSEL = 0 would report a
> speed of 0 until the new target was reached. This has been fixed,
> resulting in a revision "B" update where the MFR_REVISION of "B" is
> 0x3061.
>
Is that published somewhere ?
> Signed-off-by: Matthew Barth <msbarth@linux.ibm.com>
> ---
> drivers/hwmon/pmbus/max31785.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/hwmon/pmbus/max31785.c b/drivers/hwmon/pmbus/max31785.c
> index e5a9f4019cd5..e636a65061df 100644
> --- a/drivers/hwmon/pmbus/max31785.c
> +++ b/drivers/hwmon/pmbus/max31785.c
> @@ -17,6 +17,7 @@ enum max31785_regs {
>
> #define MAX31785 0x3030
> #define MAX31785A 0x3040
> +#define MAX31785B 0x3061
>
> #define MFR_FAN_CONFIG_DUAL_TACH BIT(12)
>
> @@ -350,12 +351,13 @@ static int max31785_probe(struct i2c_client *client)
> if (ret < 0)
> return ret;
>
> - if (ret == MAX31785A) {
> + if (ret == MAX31785A || ret == MAX31785B) {
> dual_tach = true;
> } else if (ret == MAX31785) {
> if (!strcmp("max31785a", client->name))
Probably also wants to check for max31785b,
> dev_warn(dev, "Expected max3175a, found max31785: cannot provide secondary tachometer readings\n");
and say something like "Expected max3175a/b, ..."
Thanks,
Guenter
> } else {
> + dev_err(dev, "Unrecognized MAX31785 revision: %x\n", ret);
> return -ENODEV;
> }
>
> @@ -371,6 +373,7 @@ static int max31785_probe(struct i2c_client *client)
> static const struct i2c_device_id max31785_id[] = {
> { "max31785", 0 },
> { "max31785a", 0 },
> + { "max31785b", 0 },
> { },
> };
>
> @@ -379,6 +382,7 @@ MODULE_DEVICE_TABLE(i2c, max31785_id);
> static const struct of_device_id max31785_of_match[] = {
> { .compatible = "maxim,max31785" },
> { .compatible = "maxim,max31785a" },
> + { .compatible = "maxim,max31785b" },
> { },
> };
>
>
next prev parent reply other threads:[~2021-02-01 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 16:50 Matthew Barth
2021-02-01 19:43 ` Guenter Roeck [this message]
2021-02-01 20:02 ` Matthew Barth
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=96fd0466-13be-dea1-985c-19cccbd3d321@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andrew@aj.id.au \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msbarth@linux.ibm.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
all inboxes | Powered by JetHome®