From: Glenn Miles <milesg@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: "Glenn Miles" <milesg@linux.vnet.ibm.com>,
"Cédric Le Goater" <clg@kaod.org>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Frédéric Barrat" <fbarrat@linux.ibm.com>
Subject: [PATCH v3 1/8] ppc/pnv: Add pca9552 to powernv10 for PCIe hotplug power control
Date: Tue, 14 Nov 2023 13:56:52 -0600 [thread overview]
Message-ID: <20231114195659.1219821-2-milesg@linux.vnet.ibm.com> (raw)
In-Reply-To: <20231114195659.1219821-1-milesg@linux.vnet.ibm.com>
The Power Hypervisor code expects to see a pca9552 device connected
to the 3rd PNV I2C engine on port 1 at I2C address 0x63 (or left-
justified address of 0xC6). This is used by hypervisor code to
control PCIe slot power during hotplug events.
Signed-off-by: Glenn Miles <milesg@linux.vnet.ibm.com>
---
Based-on: <20231024181144.4045056-3-milesg@linux.vnet.ibm.com>
[PATCH v3 2/2] misc/pca9552: Let external devices set pca9552 inputs
No changes from v2
hw/ppc/Kconfig | 1 +
hw/ppc/pnv.c | 7 +++++++
2 files changed, 8 insertions(+)
diff --git a/hw/ppc/Kconfig b/hw/ppc/Kconfig
index 56f0475a8e..f77ca773cf 100644
--- a/hw/ppc/Kconfig
+++ b/hw/ppc/Kconfig
@@ -32,6 +32,7 @@ config POWERNV
select XIVE
select FDT_PPC
select PCI_POWERNV
+ select PCA9552
config PPC405
bool
diff --git a/hw/ppc/pnv.c b/hw/ppc/pnv.c
index 9c29727337..7afaf1008f 100644
--- a/hw/ppc/pnv.c
+++ b/hw/ppc/pnv.c
@@ -1877,6 +1877,13 @@ static void pnv_chip_power10_realize(DeviceState *dev, Error **errp)
qdev_get_gpio_in(DEVICE(&chip10->psi),
PSIHB9_IRQ_SBE_I2C));
}
+
+ /*
+ * Add a PCA9552 I2C device for PCIe hotplug control
+ * to engine 2, bus 1, address 0x63
+ */
+ i2c_slave_create_simple(chip10->i2c[2].busses[1], "pca9552", 0x63);
+
}
static uint32_t pnv_chip_power10_xscom_pcba(PnvChip *chip, uint64_t addr)
--
2.31.1
next prev parent reply other threads:[~2023-11-14 19:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 19:56 [PATCH v3 0/8] Add powernv10 I2C devices and tests Glenn Miles
2023-11-14 19:56 ` Glenn Miles [this message]
2023-11-15 7:28 ` [PATCH v3 1/8] ppc/pnv: Add pca9552 to powernv10 for PCIe hotplug power control Cédric Le Goater
2023-11-15 16:37 ` Miles Glenn
2023-11-15 22:34 ` Cédric Le Goater
2023-11-16 22:43 ` Miles Glenn
2023-11-17 16:04 ` Cédric Le Goater
2023-11-17 19:08 ` Miles Glenn
2023-11-14 19:56 ` [PATCH v3 2/8] ppc/pnv: Wire up pca9552 GPIO pins " Glenn Miles
2023-11-14 19:56 ` [PATCH v3 3/8] ppc/pnv: PNV I2C engines assigned incorrect XSCOM addresses Glenn Miles
2023-11-15 22:19 ` Cédric Le Goater
2023-11-18 7:36 ` Cédric Le Goater
2023-11-14 19:56 ` [PATCH v3 4/8] ppc/pnv: Fix PNV I2C invalid status after reset Glenn Miles
2023-11-15 22:20 ` Cédric Le Goater
2023-11-18 7:36 ` Cédric Le Goater
2023-11-14 19:56 ` [PATCH v3 5/8] ppc/pnv: Use resettable interface to reset child I2C buses Glenn Miles
2023-11-14 19:56 ` [PATCH v3 6/8] misc: Add a pca9554 GPIO device model Glenn Miles
2023-11-14 19:56 ` [PATCH v3 7/8] ppc/pnv: Add a pca9554 I2C device to powernv10 Glenn Miles
2023-11-14 19:56 ` [PATCH v3 8/8] ppc/pnv: Test pnv i2c master and connected devices Glenn Miles
2023-11-15 10:03 ` [PATCH v3 0/8] Add powernv10 I2C devices and tests Cédric Le Goater
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=20231114195659.1219821-2-milesg@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).