From: Corey Minyard <cminyard@mvista.com>
To: Titus Rwantare <titusr@google.com>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org, f4bug@amsat.org
Subject: Re: [PATCH v3 0/5] Add support for PMBus in QEMU
Date: Tue, 18 May 2021 14:45:18 -0500 [thread overview]
Message-ID: <20210518194518.GY11196@minyard.net> (raw)
In-Reply-To: <20210518184527.1037888-1-titusr@google.com>
On Tue, May 18, 2021 at 11:45:22AM -0700, Titus Rwantare wrote:
> Hello,
>
> This patch series adds an interface to start supporting PMBus devices in QEMU.
> I’ve included two PMBus devices: MAX34451 and ADM1272.
I've reviewed all these patches, and beyond my one comment, they look
good.
I'm not too excited about putting the device files in misc. I know some
SMBus sensors are in there, but they really aren't miscellaneous. They
are really sensors. But unless we want to create a sensors directory
and move things into that, misc will have to do, I guess.
-corey
>
> PMBus is a variant of SMBus meant for digital management of power supplies.
> PMBus adds to the SMBus standard by defining a number of constants and commands
> used by compliant devices. The specification for PMBus can be found at:
>
> https://pmbus.org/specification-archives/
>
> Currently, the goal for these devices is to emulate basic functionality by
> reading and writing registers. Timing, and some logical operation is not
> implemented. This implementation supports nearly all available registers for
> PMBus including:
> - Voltage inputs and outputs
> - Current inputs and outputs
> - Temperature sensors
>
> Unimplimented registers get passed through to the device model, and device
> models can opt out of using the standard registers with flags. The included
> devices make use of these fields and illustrate how to interface with the pmbus
> class.
>
> Datasheets for sensors:
>
> https://datasheets.maximintegrated.com/en/ds/MAX34451.pdf
> https://www.analog.com/media/en/technical-documentation/data-sheets/ADM1272.pdf
>
> Since v2:
> - bump for feedback
> - removed commented out code
>
> Since v1:
> - addressed Joel's comments
> - split out tests into their own patches
>
> Thanks for reviewing,
>
> Titus Rwantare
>
> Titus Rwantare (5):
> hw/i2c: add support for PMBus
> hw/misc: add ADM1272 device
> tests/qtest: add tests for ADM1272 device model
> hw/misc: add MAX34451 device
> tests/qtest: add tests for MAX34451 device model
>
> include/hw/i2c/pmbus_device.h | 506 +++++++++++
> hw/i2c/pmbus_device.c | 1596 +++++++++++++++++++++++++++++++++
> hw/misc/adm1272.c | 543 +++++++++++
> hw/misc/max34451.c | 716 +++++++++++++++
> tests/qtest/adm1272-test.c | 445 +++++++++
> tests/qtest/max34451-test.c | 336 +++++++
> hw/arm/Kconfig | 3 +
> hw/i2c/Kconfig | 4 +
> hw/i2c/meson.build | 1 +
> hw/misc/Kconfig | 8 +
> hw/misc/meson.build | 2 +
> tests/qtest/meson.build | 2 +
> 12 files changed, 4162 insertions(+)
> create mode 100644 include/hw/i2c/pmbus_device.h
> create mode 100644 hw/i2c/pmbus_device.c
> create mode 100644 hw/misc/adm1272.c
> create mode 100644 hw/misc/max34451.c
> create mode 100644 tests/qtest/adm1272-test.c
> create mode 100644 tests/qtest/max34451-test.c
>
> --
> 2.31.1.751.gd2f1c929bd-goog
>
next prev parent reply other threads:[~2021-05-18 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 18:45 [PATCH v3 0/5] Add support for PMBus in QEMU Titus Rwantare
2021-05-18 18:45 ` [PATCH v3 1/5] hw/i2c: add support for PMBus Titus Rwantare
2021-05-18 19:37 ` Corey Minyard
2021-05-18 19:46 ` Titus Rwantare
2021-05-18 18:45 ` [PATCH v3 2/5] hw/misc: add ADM1272 device Titus Rwantare
2021-05-18 18:45 ` [PATCH v3 3/5] tests/qtest: add tests for ADM1272 device model Titus Rwantare
2021-05-18 18:45 ` [PATCH v3 4/5] hw/misc: add MAX34451 device Titus Rwantare
2021-05-18 18:45 ` [PATCH v3 5/5] tests/qtest: add tests for MAX34451 device model Titus Rwantare
2021-05-18 19:45 ` Corey Minyard [this message]
2021-05-18 19:50 ` [PATCH v3 0/5] Add support for PMBus in QEMU Titus Rwantare
2021-05-18 20:59 ` Corey Minyard
2021-05-18 21:43 ` Titus Rwantare
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=20210518194518.GY11196@minyard.net \
--to=cminyard@mvista.com \
--cc=f4bug@amsat.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=titusr@google.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).