LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net> To: Chris Packham <chris.packham@alliedtelesis.co.nz> Cc: jdelvare@suse.com, linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 2/2] hwmon: (pmbus/bpa-rs600) Add workaround for incorrect Pin max Date: Wed, 11 Aug 2021 21:41:24 -0700 [thread overview] Message-ID: <20210812044124.GA1116027@roeck-us.net> (raw) In-Reply-To: <20210812014000.26293-3-chris.packham@alliedtelesis.co.nz> On Thu, Aug 12, 2021 at 01:40:00PM +1200, Chris Packham wrote: > BPD-RS600 modules running firmware v5.70 misreport the MFR_PIN_MAX. > The indicate a maximum of 1640W instead of 700W. Detect the invalid > reading and return a sensible value instead. > > Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz> Applied. Thanks, Guenter > --- > > Notes: > Changes in v2: > - Add comments for magic values > > drivers/hwmon/pmbus/bpa-rs600.c | 23 +++++++++++++++++++++++ > 1 file changed, 23 insertions(+) > > diff --git a/drivers/hwmon/pmbus/bpa-rs600.c b/drivers/hwmon/pmbus/bpa-rs600.c > index 84dee86399cb..f2d4e378a775 100644 > --- a/drivers/hwmon/pmbus/bpa-rs600.c > +++ b/drivers/hwmon/pmbus/bpa-rs600.c > @@ -65,6 +65,26 @@ static int bpa_rs600_read_vin(struct i2c_client *client) > return ret; > } > > +/* > + * Firmware V5.70 incorrectly reports 1640W for MFR_PIN_MAX. > + * Deal with this by returning a sensible value. > + */ > +static int bpa_rs600_read_pin_max(struct i2c_client *client) > +{ > + int ret; > + > + ret = pmbus_read_word_data(client, 0, 0xff, PMBUS_MFR_PIN_MAX); > + if (ret < 0) > + return ret; > + > + /* Detect invalid 1640W (linear encoding) */ > + if (ret == 0x0b34) > + /* Report 700W (linear encoding) */ > + return 0x095e; > + > + return ret; > +} > + > static int bpa_rs600_read_word_data(struct i2c_client *client, int page, int phase, int reg) > { > int ret; > @@ -91,6 +111,9 @@ static int bpa_rs600_read_word_data(struct i2c_client *client, int page, int pha > case PMBUS_READ_VIN: > ret = bpa_rs600_read_vin(client); > break; > + case PMBUS_MFR_PIN_MAX: > + ret = bpa_rs600_read_pin_max(client); > + break; > default: > if (reg >= PMBUS_VIRT_BASE) > ret = -ENXIO;
prev parent reply other threads:[~2021-08-12 4:41 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-12 1:39 [PATCH v2 0/2] hwmon: (pmbus/bpa-rs600) cleanup and workaround Chris Packham 2021-08-12 1:39 ` [PATCH v2 1/2] hwmon: (pmbus/bpa-rs600) Don't use rated limits as warn limits Chris Packham 2021-08-12 4:40 ` Guenter Roeck 2021-08-12 1:40 ` [PATCH v2 2/2] hwmon: (pmbus/bpa-rs600) Add workaround for incorrect Pin max Chris Packham 2021-08-12 4:41 ` 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=20210812044124.GA1116027@roeck-us.net \ --to=linux@roeck-us.net \ --cc=chris.packham@alliedtelesis.co.nz \ --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: linkBe 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; as well as URLs for NNTP newsgroup(s).