From: Eddie James <eajames@linux.ibm.com>
To: linux-hwmon@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
devicetree@vger.kernel.org, linux@roeck-us.net, andrew@aj.id.au,
joel@jms.id.au, mark.rutland@arm.com, robh+dt@kernel.org,
jdelvare@suse.com, Eddie James <eajames@linux.ibm.com>
Subject: [PATCH 0/3] pmbus: ibm-cffps: Add support for version 2 of PSU
Date: Fri, 30 Aug 2019 11:09:42 -0500 [thread overview]
Message-ID: <1567181385-22129-1-git-send-email-eajames@linux.ibm.com> (raw)
Version 2 of this PSU supports a second page of data and changes the
format of the FW version command. Use the devicetree binding (or the I2C
device ID) to determine which version the driver should use. Therefore add
the new compatible string to the devicetree documentation and change the
Swift system devicetree to use version 2.
Eddie James (3):
dt-bindings: hwmon: Document ibm,cffps2 compatible string
ARM: dts: aspeed: swift: Change power supplies to version 2
pmbus: ibm-cffps: Add support for version 2 of the PSU
.../devicetree/bindings/hwmon/ibm,cffps1.txt | 8 +-
arch/arm/boot/dts/aspeed-bmc-opp-swift.dts | 4 +-
drivers/hwmon/pmbus/ibm-cffps.c | 109 ++++++++++++++++-----
3 files changed, 94 insertions(+), 27 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-08-30 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 16:09 Eddie James [this message]
2019-08-30 16:09 ` [PATCH 1/3] dt-bindings: hwmon: Document ibm,cffps2 compatible string Eddie James
2019-08-30 16:09 ` [PATCH 2/3] ARM: dts: aspeed: swift: Change power supplies to version 2 Eddie James
2019-08-30 16:09 ` [PATCH 3/3] pmbus: ibm-cffps: Add support for version 2 of the PSU Eddie James
2019-08-30 17:36 ` Guenter Roeck
2019-08-30 18:19 ` Eddie James
2019-09-02 7:49 ` kbuild test robot
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=1567181385-22129-1-git-send-email-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--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).