From: Guenter Roeck <linux@roeck-us.net>
To: Andrew Jeffery <andrew@aj.id.au>, linux-hwmon@vger.kernel.org
Cc: robh+dt@kernel.org, mark.rutland@arm.com, jdelvare@suse.com,
corbet@lwn.net, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
joel@jms.id.au, openbmc@lists.ozlabs.org
Subject: Re: [PATCH v5 3/4] pmbus (core): Add virtual page config bit
Date: Sun, 19 Nov 2017 08:49:19 -0800 [thread overview]
Message-ID: <3e84eca8-7a10-abd3-b8df-babb5f4ac8a0@roeck-us.net> (raw)
In-Reply-To: <c5ccfeab881181dfbfdbdfb26051bb4cd332f6e6.1510974230.git-series.andrew@aj.id.au>
On 11/17/2017 07:26 PM, Andrew Jeffery wrote:
> Some circumstances call for virtual pages, to expose multiple values
> packed into an extended PMBus register in a manner non-compliant with
> the PMBus standard. An example of this is the Maxim MAX31785 controller, which
> extends the READ_FAN_SPEED_1 PMBus register from two to four bytes to support
> tach readings for both rotors of a dual rotor fan. This extended register
> contains two word-sized values, one reporting the rate of the fastest rotor,
> the other the rate of the slowest. The concept of virtual pages aids this
> situation by mapping the page number onto the value to be selected from the
> vectored result.
>
> We should not try to set virtual pages on the device as such a page explicitly
> doesn't exist; add a flag so we can avoid doing so.
>
> Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
> ---
> drivers/hwmon/pmbus/pmbus.h | 2 ++
> drivers/hwmon/pmbus/pmbus_core.c | 10 +++++++---
> 2 files changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/hwmon/pmbus/pmbus.h b/drivers/hwmon/pmbus/pmbus.h
> index b54d7604d3ef..d39d506aa63e 100644
> --- a/drivers/hwmon/pmbus/pmbus.h
> +++ b/drivers/hwmon/pmbus/pmbus.h
> @@ -372,6 +372,8 @@ enum pmbus_sensor_classes {
> #define PMBUS_HAVE_PWM12 BIT(20)
> #define PMBUS_HAVE_PWM34 BIT(21)
>
> +#define PMBUS_PAGE_VIRTUAL BIT(31)
> +
> enum pmbus_data_format { linear = 0, direct, vid };
> enum vrm_version { vr11 = 0, vr12, vr13 };
>
> diff --git a/drivers/hwmon/pmbus/pmbus_core.c b/drivers/hwmon/pmbus/pmbus_core.c
> index 631db88526b6..ba97230fcde7 100644
> --- a/drivers/hwmon/pmbus/pmbus_core.c
> +++ b/drivers/hwmon/pmbus/pmbus_core.c
> @@ -164,14 +164,18 @@ int pmbus_set_page(struct i2c_client *client, int page)
> int rv = 0;
> int newpage;
>
> - if (page >= 0 && page != data->currpage) {
> + if (page < 0 || page == data->currpage)
> + return 0;
> +
> + if (!(data->info->func[page] & PMBUS_PAGE_VIRTUAL)) {
> rv = i2c_smbus_write_byte_data(client, PMBUS_PAGE, page);
> newpage = i2c_smbus_read_byte_data(client, PMBUS_PAGE);
> if (newpage != page)
> rv = -EIO;
This should probably be something like
rv = i2c_smbus_write_byte_data(client, PMBUS_PAGE, page);
if (rv < 0)
return rv;
newpage = i2c_smbus_read_byte_data(client, PMBUS_PAGE);
if (newpage < 0)
return newpage;
if (newpage != page)
return -EIO;
We can actually drop 'newpage' and just use 'rv'.
> - else
> - data->currpage = page;
> }
> +
> + data->currpage = page;
> +
... otherwise currpage is set even on error.
> return rv;
this can then be
return 0;
> }
> EXPORT_SYMBOL_GPL(pmbus_set_page);
>
next prev parent reply other threads:[~2017-11-19 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 3:26 [PATCH v5 0/4] pmbus: Expand fan support and add MAX31785 driver Andrew Jeffery
2017-11-18 3:26 ` [PATCH v5 1/4] pmbus (core): Add fan control support Andrew Jeffery
2017-11-18 3:26 ` [PATCH v5 2/4] pmbus (max31785): Add fan control Andrew Jeffery
2017-11-18 3:26 ` [PATCH v5 3/4] pmbus (core): Add virtual page config bit Andrew Jeffery
2017-11-19 16:49 ` Guenter Roeck [this message]
2017-11-20 0:40 ` Andrew Jeffery
2017-11-18 3:26 ` [PATCH v5 4/4] pmbus (max31785): Add dual tachometer support Andrew Jeffery
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=3e84eca8-7a10-abd3-b8df-babb5f4ac8a0@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andrew@aj.id.au \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).