From: Eddie James <eajames@linux.vnet.ibm.com>
To: Guenter Roeck <linux@roeck-us.net>, linux-kernel@vger.kernel.org
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
jdelvare@suse.com, mark.rutland@arm.com, robh+dt@kernel.org,
gregkh@linuxfoundation.org, cbostic@linux.vnet.ibm.com,
jk@ozlabs.org, joel@jms.id.au, andrew@aj.id.au,
"Edward A. James" <eajames@us.ibm.com>
Subject: Re: [PATCH 0/7] drivers/hwmon: Add On-Chip Controller (OCC) hwmon driver
Date: Fri, 23 Jun 2017 08:38:50 -0500 [thread overview]
Message-ID: <4d77d0b7-d7eb-d62f-a10e-63dde83bd407@linux.vnet.ibm.com> (raw)
In-Reply-To: <7806f15f-a594-2cfb-777a-29f1e8a3fd97@roeck-us.net>
On 06/22/2017 11:52 PM, Guenter Roeck wrote:
> On 06/22/2017 03:48 PM, Eddie James wrote:
>> From: "Edward A. James" <eajames@us.ibm.com>
>>
>> This series adds a hwmon driver to support the OCC on POWER8 and POWER9
>> processors. The OCC is an embedded processor that provides realtime
>> power and
>> thermal monitoring and management.
>>
>> This driver has two different platform drivers as a "base" for the
>> hwmon stuff, as the means of communicating with the OCC on P8 and P9 is
>> completely different. For P8, the driver is an I2C client driver. For
>> P9 the
>> driver is an FSI-based OCC client driver, and uses the OCC driver
>> in-kernel
>> API.
>>
>> There was a previous version of this driver that wasn't written with the
>> differences in communication methods between the two versions in
>> mind. This
>> driver has been considerably simplified.
>>
>
> I thought I did see this before.
>
> It is customary to use "v2" in such situations, and add a change log.
> You expect me to go into the two versions and compare them to figure
> out what changed to evaluate if it makes sense. Do you really believe
> that
> I have enough time to do that, and that I would be willing to spend that
> time in the first place ?
>
> Presumably you know what changed. Why not just tell me ?
Hi,
This driver does not build upon the previous patch set at all, so I
didn't mark it as a v2. It is completely rewritten from scratch. I sent
a note saying that the previous patch set was abandoned. There may be
some similarities with the previous one, simply because the drivers do
the same thing, but I don't think there is any need to compare it with
the old driver I mailed out.
Thanks for your time,
Eddie
>
> Guenter
>
>> Edward A. James (7):
>> drivers/hwmon: Add On-Chip Controller (OCC) hwmon driver
>> drivers/hwmon/occ: Add command transport method for P8 and P9
>> drivers/hwmon/occ: Parse OCC poll response
>> drivers/hwmon/occ: Add sensor types and versions
>> drivers/hwmon/occ: Add sensor attributes and register hwmon device
>> drivers/hwmon/occ: Add non-hwmon attributes
>> drivers/hwmon/occ: Add error handling
>>
>> Documentation/ABI/testing/sysfs-driver-occ-hwmon | 77 ++
>> .../devicetree/bindings/fsi/ibm,p9-occ-hwmon.txt | 18 +
>> .../devicetree/bindings/i2c/ibm,p8-occ-hwmon.txt | 25 +
>> Documentation/hwmon/occ | 84 ++
>> drivers/hwmon/Kconfig | 2 +
>> drivers/hwmon/Makefile | 1 +
>> drivers/hwmon/occ/Kconfig | 28 +
>> drivers/hwmon/occ/Makefile | 11 +
>> drivers/hwmon/occ/common.c | 1242
>> ++++++++++++++++++++
>> drivers/hwmon/occ/common.h | 151 +++
>> drivers/hwmon/occ/p8_i2c.c | 250 ++++
>> drivers/hwmon/occ/p9_sbe.c | 144 +++
>> 12 files changed, 2033 insertions(+)
>> create mode 100644 Documentation/ABI/testing/sysfs-driver-occ-hwmon
>> create mode 100644
>> Documentation/devicetree/bindings/fsi/ibm,p9-occ-hwmon.txt
>> create mode 100644
>> Documentation/devicetree/bindings/i2c/ibm,p8-occ-hwmon.txt
>> create mode 100644 Documentation/hwmon/occ
>> create mode 100644 drivers/hwmon/occ/Kconfig
>> create mode 100644 drivers/hwmon/occ/Makefile
>> create mode 100644 drivers/hwmon/occ/common.c
>> create mode 100644 drivers/hwmon/occ/common.h
>> create mode 100644 drivers/hwmon/occ/p8_i2c.c
>> create mode 100644 drivers/hwmon/occ/p9_sbe.c
>>
>
prev parent reply other threads:[~2017-06-23 13:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 22:48 [PATCH 0/7] drivers/hwmon: Add On-Chip Controller (OCC) hwmon driver Eddie James
2017-06-22 22:48 ` [PATCH 1/7] " Eddie James
2017-06-24 14:15 ` Guenter Roeck
2017-06-26 15:06 ` Eddie James
2017-06-26 16:38 ` Guenter Roeck
2017-06-26 19:01 ` Rob Herring
2017-06-22 22:48 ` [PATCH 2/7] drivers/hwmon/occ: Add command transport method for P8 and P9 Eddie James
2017-06-24 14:49 ` Guenter Roeck
2017-06-26 15:30 ` Eddie James
2017-06-26 16:55 ` Guenter Roeck
2017-06-22 22:48 ` [PATCH 3/7] drivers/hwmon/occ: Parse OCC poll response Eddie James
2017-06-22 22:48 ` [PATCH 4/7] drivers/hwmon/occ: Add sensor types and versions Eddie James
2017-06-22 22:48 ` [PATCH 5/7] drivers/hwmon/occ: Add sensor attributes and register hwmon device Eddie James
2017-06-22 22:48 ` [PATCH 6/7] drivers/hwmon/occ: Add non-hwmon attributes Eddie James
2017-06-22 22:48 ` [PATCH 7/7] drivers/hwmon/occ: Add error handling Eddie James
2017-06-23 4:52 ` [PATCH 0/7] drivers/hwmon: Add On-Chip Controller (OCC) hwmon driver Guenter Roeck
2017-06-23 13:38 ` Eddie James [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=4d77d0b7-d7eb-d62f-a10e-63dde83bd407@linux.vnet.ibm.com \
--to=eajames@linux.vnet.ibm.com \
--cc=andrew@aj.id.au \
--cc=cbostic@linux.vnet.ibm.com \
--cc=devicetree@vger.kernel.org \
--cc=eajames@us.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.com \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--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).