From: titusr@google.com
To: philmd@linaro.org, minyard@acm.org
Cc: Titus Rwantare <titusr@google.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org,
Hao Wu <wuhaotsh@google.com>,
Corey Minyard <cminyard@mvista.com>,
Stephen Longfield <slongfield@google.com>,
Benjamin Streb <bstreb@google.com>,
Patrick Venture <venture@google.com>
Subject: [PATCH v4 0/8] PMBus fixes and new functions
Date: Mon, 23 Oct 2023 23:46:39 +0000 [thread overview]
Message-ID: <20231023-staging-pmbus-v3-v4-0-07a8cb7cd20a@google.com> (raw)
This patch series contains fixes and improvements to PMBus support in QEMU.
The following has been added:
- Support for block receive
- Support for devices with fans
- Support for the VCAP register for devices with onboard energy storage
- A bitfield struct for the vout mode register, whose bits determine the
formatting of several read commands in PMBus
Fixes:
- String read now handles now logs an error when passed an empty string
This series is in preparation for some additional sensors that exercise
this functionality that will be incoming shortly.
Changes in v4:
- Added missing commit tags
Changes in v3:
- Added fixes to PMBus: page resets and fault clearing
Changes in v2:
- Expanded commit descriptions
- Added the ADM1266 device model that uses new functions
Signed-off-by: Titus Rwantare <titusr@google.com>
---
Titus Rwantare (8):
hw/i2c: pmbus add support for block receive
hw/i2c: pmbus: add vout mode bitfields
hw/i2c: pmbus: add fan support
hw/i2c: pmbus: add VCAP register
hw/sensor: add ADM1266 device model
tests/qtest: add tests for ADM1266
hw/i2c: pmbus: immediately clear faults on request
hw/i2c: pmbus: reset page register for out of range reads
hw/arm/Kconfig | 1 +
hw/i2c/pmbus_device.c | 237 +++++++++++++++++++++++++++++++++++++--
hw/sensor/Kconfig | 5 +
hw/sensor/adm1266.c | 254 ++++++++++++++++++++++++++++++++++++++++++
hw/sensor/meson.build | 1 +
include/hw/i2c/pmbus_device.h | 17 +++
tests/qtest/adm1266-test.c | 123 ++++++++++++++++++++
tests/qtest/max34451-test.c | 24 ++++
tests/qtest/meson.build | 1 +
9 files changed, 653 insertions(+), 10 deletions(-)
---
base-commit: 384dbdda94c0bba55bf186cccd3714bbb9b737e9
change-id: 20231023-staging-pmbus-v3-62de60bff397
Best regards,
--
Titus Rwantare <titusr@google.com>
next reply other threads:[~2023-10-23 23:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 23:46 titusr [this message]
2023-10-23 23:46 ` [PATCH v4 1/8] hw/i2c: pmbus add support for block receive titusr
2023-10-23 23:46 ` [PATCH v4 2/8] hw/i2c: pmbus: add vout mode bitfields titusr
2023-10-23 23:46 ` [PATCH v4 3/8] hw/i2c: pmbus: add fan support titusr
2023-10-23 23:46 ` [PATCH v4 4/8] hw/i2c: pmbus: add VCAP register titusr
2023-10-23 23:46 ` [PATCH v4 5/8] hw/sensor: add ADM1266 device model titusr
2023-10-23 23:46 ` [PATCH v4 6/8] tests/qtest: add tests for ADM1266 titusr
2023-10-23 23:46 ` [PATCH v4 7/8] hw/i2c: pmbus: immediately clear faults on request titusr
2023-10-23 23:46 ` [PATCH v4 8/8] hw/i2c: pmbus: reset page register for out of range reads titusr
2023-10-24 9:58 ` [PATCH v4 0/8] PMBus fixes and new functions Philippe Mathieu-Daudé
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=20231023-staging-pmbus-v3-v4-0-07a8cb7cd20a@google.com \
--to=titusr@google.com \
--cc=bstreb@google.com \
--cc=cminyard@mvista.com \
--cc=minyard@acm.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=slongfield@google.com \
--cc=venture@google.com \
--cc=wuhaotsh@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).