From: Andrew Jeffery <andrew@aj.id.au>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org, 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: [v4,4/6] pmbus: max31785: Add fan control
Date: Fri, 10 Nov 2017 13:40:16 +1030 [thread overview]
Message-ID: <1510283416.4287.43.camel@aj.id.au> (raw)
In-Reply-To: <20171105150441.GA26191@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 4090 bytes --]
On Sun, 2017-11-05 at 07:04 -0800, Guenter Roeck wrote:
> On Fri, Nov 03, 2017 at 03:53:04PM +1100, Andrew Jeffery wrote:
> > The implementation makes use of the new fan control virtual registers
> > exposed by the pmbus core. It mixes use of the default implementations
> > with some overrides via the read/write handlers to handle FAN_COMMAND_1
> > on the MAX31785, whose definition breaks the value range into various
> > control bands dependent on RPM or PWM mode.
> >
> > Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
> > ---
> > Documentation/hwmon/max31785 | 4 ++
> > drivers/hwmon/pmbus/max31785.c | 104 ++++++++++++++++++++++++++++++++++++++++-
> > 2 files changed, 107 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/hwmon/max31785 b/Documentation/hwmon/max31785
> > index 45fb6093dec2..e9edbf11948f 100644
> > --- a/Documentation/hwmon/max31785
> > +++ b/Documentation/hwmon/max31785
> > @@ -32,6 +32,7 @@ Sysfs attributes
> > fan[1-4]_alarm Fan alarm.
> > fan[1-4]_fault Fan fault.
> > fan[1-4]_input Fan RPM.
> > +fan[1-4]_target Fan input target
> >
> > in[1-6]_crit Critical maximum output voltage
> > in[1-6]_crit_alarm Output voltage critical high alarm
> > @@ -44,6 +45,9 @@ in[1-6]_max_alarm Output voltage high alarm
> > in[1-6]_min Minimum output voltage
> > in[1-6]_min_alarm Output voltage low alarm
> >
> > +pwm[1-4] Fan target duty cycle (0..255)
> > +pwm[1-4]_enable 0: full-speed, 1: manual control, 2: automatic
> > +
> > temp[1-11]_crit Critical high temperature
> > temp[1-11]_crit_alarm Chip temperature critical high alarm
> > temp[1-11]_input Measured temperature
> > diff --git a/drivers/hwmon/pmbus/max31785.c b/drivers/hwmon/pmbus/max31785.c
> > index 9313849d5160..0d97ddf67079 100644
> > --- a/drivers/hwmon/pmbus/max31785.c
> > +++ b/drivers/hwmon/pmbus/max31785.c
> > @@ -20,8 +20,102 @@ enum max31785_regs {
> >
> > #define MAX31785_NR_PAGES 23
> >
> > +static int max31785_get_pwm(struct i2c_client *client, int page)
> > +{
> > + int config;
> > + int command;
> > +
> > + config = pmbus_read_byte_data(client, page, PMBUS_FAN_CONFIG_12);
> > + if (config < 0)
> > + return config;
> > +
> > + command = pmbus_read_word_data(client, page, PMBUS_FAN_COMMAND_1);
> > + if (command < 0)
> > + return command;
> > +
> > + if (!(config & PB_FAN_1_RPM)) {
> > + if (command >= 0x8000)
> > + return 0;
> > + else if (command >= 0x2711)
> > + return 0x2710;
> > +
> > + return command;
> > + }
> > +
> > + return 0;
> > +}
> > +
> > +static int max31785_get_pwm_mode(struct i2c_client *client, int page)
> > +{
> > + int config;
> > + int command;
> > +
> > + config = pmbus_read_byte_data(client, page, PMBUS_FAN_CONFIG_12);
> > + if (config < 0)
> > + return config;
> > +
> > + command = pmbus_read_word_data(client, page, PMBUS_FAN_COMMAND_1);
> > + if (command < 0)
> > + return command;
> > +
> > + if (!(config & PB_FAN_1_RPM)) {
> > + if (command >= 0x8000)
> > + return 2;
> > + else if (command >= 0x2711)
> > + return 0;
> > +
> > + return 1;
> > + }
> > +
> > + return (command >= 0x8000) ? 2 : 1;
> > +}
> > +
> > +static int max31785_read_word_data(struct i2c_client *client, int page,
> > + int reg)
> > +{
> > + int rv;
> > +
> > + switch (reg) {
> > + case PMBUS_VIRT_PWM_1:
> > + rv = max31785_get_pwm(client, page);
> > + if (rv < 0)
> > + return rv;
> > +
> > + rv *= 255;
> > + rv /= 100;
> > + break;
> > + case PMBUS_VIRT_PWM_ENABLE_1:
> > + rv = max31785_get_pwm_mode(client, page);
> > + break;
>
> I do wonder ... does it even make sense to specify generic code
> for the new virtual attributes in the pmbus core code, or would
> it be better to have it all in this driver, at least for now ?
I think I'll pull the generic implementations out in light of my
response on 3/6. At best the generic implementation for the PWM virtual
regs is a guess. We can always put it back if others come to need it.
Cheers,
Andrew
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-11-10 3:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 4:53 [PATCH v4 0/6] pmbus: Expand fan support and add MAX31785 driver Andrew Jeffery
2017-11-03 4:53 ` [PATCH v4 1/6] dt-bindings: pmbus: Add Maxim MAX31785 documentation Andrew Jeffery
2017-11-06 21:52 ` Rob Herring
2017-11-07 1:27 ` [v4,1/6] " Guenter Roeck
2017-11-03 4:53 ` [PATCH v4 2/6] pmbus: Add driver for Maxim MAX31785 Intelligent Fan Controller Andrew Jeffery
2017-11-05 14:08 ` [v4, " Guenter Roeck
2017-11-03 4:53 ` [PATCH v4 3/6] pmbus: core: Add fan control support Andrew Jeffery
2017-11-05 14:39 ` [v4,3/6] " Guenter Roeck
2017-11-10 3:03 ` Andrew Jeffery
2017-11-10 8:24 ` Guenter Roeck
2017-11-03 4:53 ` [PATCH v4 4/6] pmbus: max31785: Add fan control Andrew Jeffery
2017-11-05 15:04 ` [v4,4/6] " Guenter Roeck
2017-11-10 3:10 ` Andrew Jeffery [this message]
2017-11-10 8:07 ` Guenter Roeck
2017-11-03 4:53 ` [PATCH v4 5/6] pmbus: core: Add virtual page config bit Andrew Jeffery
2017-11-03 4:53 ` [PATCH v4 6/6] pmbus: max31785: Add dual tachometer support Andrew Jeffery
[not found] ` <20171103045306.26448-7-andrew-zrmu5oMJ5Fs@public.gmane.org>
2017-11-05 14:58 ` [v4,6/6] " Guenter Roeck
[not found] ` <20171105145833.GA25880-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2017-11-10 3:12 ` 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=1510283416.4287.43.camel@aj.id.au \
--to=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=linux@roeck-us.net \
--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).