From: Miles Glenn <milesg@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: "Cédric Le Goater" <clg@kaod.org>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Frédéric Barrat" <fbarrat@linux.ibm.com>
Subject: Re: [PATCH 0/8] Add powernv10 I2C devices and tests
Date: Fri, 10 Nov 2023 11:51:12 -0600 [thread overview]
Message-ID: <7ab0ff7e881340b8649b18f890ef751e03e9afc2.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20231110172248.3885194-1-milesg@linux.vnet.ibm.com>
On Fri, 2023-11-10 at 11:22 -0600, Glenn Miles wrote:
> This series of patches includes support, tests and fixes for
> adding PCA9552 and PCA9554 I2C devices to the powernv10 chip.
>
> The PCA9552 device is used for PCIe slot hotplug power control
> and monitoring, while the PCA9554 device is used for presence
> detection of IBM CableCard devices. Both devices are required
> by the Power Hypervisor Firmware on Power10 platforms.
>
Sorry folks, I got a ahead of myself and forgot to test this on
the master branch. Looks like it's currently failing 'make check'
there so I'll be coming out with a v2 once I get it working.
Regards,
Glenn
> Glenn Miles (8):
> ppc/pnv: Add pca9552 to powernv10 for PCIe hotplug power control
> ppc/pnv: Wire up pca9552 GPIO pins for PCIe hotplug power control
> ppc/pnv: PNV I2C engines assigned incorrect XSCOM addresses
> ppc/pnv: Fix PNV I2C invalid status after reset
> ppc/pnv: Use resettable interface to reset child I2C buses
> misc: Add a pca9554 GPIO device model
> ppc/pnv: Add a pca9554 I2C device to powernv10
> ppc/pnv: Test pnv i2c master and connected devices
>
> MAINTAINERS | 2 +
> hw/misc/Kconfig | 4 +
> hw/misc/meson.build | 1 +
> hw/misc/pca9554.c | 328 ++++++++++++++++
> hw/ppc/Kconfig | 2 +
> hw/ppc/pnv.c | 35 +-
> hw/ppc/pnv_i2c.c | 47 ++-
> include/hw/misc/pca9554.h | 36 ++
> include/hw/misc/pca9554_regs.h | 19 +
> tests/qtest/meson.build | 1 +
> tests/qtest/pnv-host-i2c-test.c | 653
> ++++++++++++++++++++++++++++++++
> 11 files changed, 1106 insertions(+), 22 deletions(-)
> create mode 100644 hw/misc/pca9554.c
> create mode 100644 include/hw/misc/pca9554.h
> create mode 100644 include/hw/misc/pca9554_regs.h
> create mode 100644 tests/qtest/pnv-host-i2c-test.c
>
prev parent reply other threads:[~2023-11-10 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 17:22 [PATCH 0/8] Add powernv10 I2C devices and tests Glenn Miles
2023-11-10 17:22 ` [PATCH 1/8] ppc/pnv: Add pca9552 to powernv10 for PCIe hotplug power control Glenn Miles
2023-11-10 17:22 ` [PATCH 2/8] ppc/pnv: Wire up pca9552 GPIO pins " Glenn Miles
2023-11-10 17:22 ` [PATCH 3/8] ppc/pnv: PNV I2C engines assigned incorrect XSCOM addresses Glenn Miles
2023-11-10 17:22 ` [PATCH 4/8] ppc/pnv: Fix PNV I2C invalid status after reset Glenn Miles
2023-11-10 17:22 ` [PATCH 5/8] ppc/pnv: Use resettable interface to reset child I2C buses Glenn Miles
2023-11-10 17:22 ` [PATCH 6/8] misc: Add a pca9554 GPIO device model Glenn Miles
2023-11-10 17:22 ` [PATCH 7/8] ppc/pnv: Add a pca9554 I2C device to powernv10 Glenn Miles
2023-11-10 17:22 ` [PATCH 8/8] ppc/pnv: Test pnv i2c master and connected devices Glenn Miles
2023-11-10 17:51 ` Miles Glenn [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=7ab0ff7e881340b8649b18f890ef751e03e9afc2.camel@linux.vnet.ibm.com \
--to=milesg@linux.vnet.ibm.com \
--cc=clg@kaod.org \
--cc=fbarrat@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).