From: Vadim Pasternak <vadimp@mellanox.com>
To: linux@roeck-us.net, robh+dt@kernel.org, vijaykhemka@fb.com
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
Vadim Pasternak <vadimp@mellanox.com>
Subject: [RFC PATCH hwmon-next v1 3/5] hwmon: (pmbus/tps53679) Allow support for Intel IMVP9 specification
Date: Sun, 5 Jan 2020 10:58:31 +0000 [thread overview]
Message-ID: <20200105105833.30196-4-vadimp@mellanox.com> (raw)
In-Reply-To: <20200105105833.30196-1-vadimp@mellanox.com>
Allow driver to Intel IMVP9 specification.
Signed-off-by: Vadim Pasternak <vadimp@mellanox.com>
---
drivers/hwmon/pmbus/tps53679.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/hwmon/pmbus/tps53679.c b/drivers/hwmon/pmbus/tps53679.c
index 163e8c6aaa8e..7ce2fca4acde 100644
--- a/drivers/hwmon/pmbus/tps53679.c
+++ b/drivers/hwmon/pmbus/tps53679.c
@@ -15,6 +15,7 @@
#define TPS53679_PROT_VR12_5MV 0x01 /* VR12.0 mode, 5-mV DAC */
#define TPS53679_PROT_VR12_5_10MV 0x02 /* VR12.5 mode, 10-mV DAC */
+#define TPS53679_PROT_IMVP9_10MV 0x03 /* IMVP9 mode, 10-mV DAC */
#define TPS53679_PROT_VR13_10MV 0x04 /* VR13.0 mode, 10-mV DAC */
#define TPS53679_PROT_IMVP8_5MV 0x05 /* IMVP8 mode, 5-mV DAC */
#define TPS53679_PROT_VR13_5MV 0x07 /* VR13.0 mode, 5-mV DAC */
@@ -44,6 +45,9 @@ static int tps53679_identify(struct i2c_client *client,
case TPS53679_PROT_IMVP8_5MV:
info->vrm_version[i] = vr12;
break;
+ case TPS53679_PROT_IMVP9_10MV:
+ info->vrm_version[i] = imvp9;
+ break;
default:
return -EINVAL;
}
--
2.11.0
next prev parent reply other threads:[~2020-01-05 10:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 10:58 [RFC PATCH hwmon-next v1 0/5] hwmon: (pmbus) Add support for vid mode calculation per page bases Vadim Pasternak
2020-01-05 10:58 ` [RFC PATCH hwmon-next v1 1/5] hwmon: (pmbus/core) Add support for vid mode detection " Vadim Pasternak
2020-01-05 10:58 ` [RFC PATCH hwmon-next v1 2/5] hwmon: (pmbus/core) Add support for Intel IMVP9 specification Vadim Pasternak
2020-01-05 16:26 ` Guenter Roeck
2020-01-05 17:15 ` Vadim Pasternak
2020-01-06 12:14 ` Vadim Pasternak
2020-01-05 10:58 ` Vadim Pasternak [this message]
2020-01-05 10:58 ` [RFC PATCH hwmon-next v1 4/5] dt-bindings: Add TI and Infineon VR Controllers as trivial devices Vadim Pasternak
2020-01-05 10:58 ` [RFC PATCH hwmon-next v1 5/5] hwmon: (pmbus/tps53679) Extend device list supported by driver Vadim Pasternak
2020-01-05 16:03 ` Guenter Roeck
2020-01-05 16:44 ` Vadim Pasternak
2020-01-05 18:34 ` Guenter Roeck
2020-01-06 12:16 ` Vadim Pasternak
2020-01-06 14:52 ` Guenter Roeck
2020-01-06 16:57 ` Vadim Pasternak
2020-01-06 21:01 ` Guenter Roeck
2020-01-06 22:29 ` Vadim Pasternak
2020-01-07 1:28 ` Guenter Roeck
2020-01-07 6:06 ` Vadim Pasternak
2020-01-07 12:14 ` Guenter Roeck
2020-01-08 14:10 ` Vadim Pasternak
2020-01-08 16:47 ` Guenter Roeck
2020-01-13 12:25 ` Vadim Pasternak
2020-01-13 20:56 ` Guenter Roeck
2020-01-14 6:54 ` Vadim Pasternak
2020-01-14 14:19 ` Guenter Roeck
2020-01-16 19:54 ` Vadim Pasternak
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=20200105105833.30196-4-vadimp@mellanox.com \
--to=vadimp@mellanox.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=vijaykhemka@fb.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;
as well as URLs for NNTP newsgroup(s).