From: Miles Glenn <milesg@linux.vnet.ibm.com>
To: "Cédric Le Goater" <clg@kaod.org>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: "Nicholas Piggin" <npiggin@gmail.com>,
"Frédéric Barrat" <fbarrat@linux.ibm.com>
Subject: Re: [PATCH v2 3/8] ppc/pnv: PNV I2C engines assigned incorrect XSCOM addresses
Date: Tue, 14 Nov 2023 09:27:50 -0600 [thread overview]
Message-ID: <8d7e592694b2c01d8c0334db7fa04f8f99f5730b.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <d9424b8a-0b4a-4e5c-b5a1-f49fd2afc0d6@kaod.org>
On Mon, 2023-11-13 at 10:07 +0100, Cédric Le Goater wrote:
> On 11/10/23 20:49, Glenn Miles wrote:
> > The PNV I2C engines for power9 and power10 were being assigned a
> > base
> > XSCOM address that was off by one I2C engine's address range such
> > that engine 0 had engine 1's address and so on. The xscom address
> > assignment was being based on the device tree engine numbering,
> > which
> > starts at 1. Rather than changing the device tree numbering to
> > start
> > with 0, the addressing was changed to be based on the existing
> > device
> > tree numbers minus one.
> >
> > Signed-off-by: Glenn Miles <milesg@linux.vnet.ibm.com>
>
> Looks like a fix to me. Please add a Fixes: tag and the patch will
> be queued for 8.2
>
> Thanks,
>
> C.
>
Yes, I agree. Sorry, still learning about all of these tags!
Thanks,
Glenn
>
> > ---
> > hw/ppc/pnv.c | 6 ++++--
> > hw/ppc/pnv_i2c.c | 2 +-
> > 2 files changed, 5 insertions(+), 3 deletions(-)
> >
> > diff --git a/hw/ppc/pnv.c b/hw/ppc/pnv.c
> > index 0b24d7d8ed..516434bc9c 100644
> > --- a/hw/ppc/pnv.c
> > +++ b/hw/ppc/pnv.c
> > @@ -1623,7 +1623,8 @@ static void
> > pnv_chip_power9_realize(DeviceState *dev, Error **errp)
> > return;
> > }
> > pnv_xscom_add_subregion(chip, PNV9_XSCOM_I2CM_BASE +
> > - chip9->i2c[i].engine *
> > PNV9_XSCOM_I2CM_SIZE,
> > + (chip9->i2c[i].engine - 1) *
> > + PNV9_XSCOM_I2CM_SIZE,
> > &chip9->i2c[i].xscom_regs);
> > qdev_connect_gpio_out(DEVICE(&chip9->i2c[i]), 0,
> > qdev_get_gpio_in(DEVICE(&chip9-
> > >psi),
> > @@ -1871,7 +1872,8 @@ static void
> > pnv_chip_power10_realize(DeviceState *dev, Error **errp)
> > return;
> > }
> > pnv_xscom_add_subregion(chip, PNV10_XSCOM_I2CM_BASE +
> > - chip10->i2c[i].engine *
> > PNV10_XSCOM_I2CM_SIZE,
> > + (chip10->i2c[i].engine - 1) *
> > + PNV10_XSCOM_I2CM_SIZE,
> > &chip10->i2c[i].xscom_regs);
> > qdev_connect_gpio_out(DEVICE(&chip10->i2c[i]), 0,
> > qdev_get_gpio_in(DEVICE(&chip10-
> > >psi),
> > diff --git a/hw/ppc/pnv_i2c.c b/hw/ppc/pnv_i2c.c
> > index f75e59e709..b2c738da50 100644
> > --- a/hw/ppc/pnv_i2c.c
> > +++ b/hw/ppc/pnv_i2c.c
> > @@ -593,7 +593,7 @@ static int pnv_i2c_dt_xscom(PnvXScomInterface
> > *dev, void *fdt,
> > int i2c_offset;
> > const char i2c_compat[] = "ibm,power8-i2cm\0ibm,power9-i2cm";
> > uint32_t i2c_pcba = PNV9_XSCOM_I2CM_BASE +
> > - i2c->engine * PNV9_XSCOM_I2CM_SIZE;
> > + (i2c->engine - 1) * PNV9_XSCOM_I2CM_SIZE;
> > uint32_t reg[2] = {
> > cpu_to_be32(i2c_pcba),
> > cpu_to_be32(PNV9_XSCOM_I2CM_SIZE)
next prev parent reply other threads:[~2023-11-14 15:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 19:49 [PATCH v2 0/8] Add powernv10 I2C devices and tests Glenn Miles
2023-11-10 19:49 ` [PATCH v2 1/8] ppc/pnv: Add pca9552 to powernv10 for PCIe hotplug power control Glenn Miles
2023-11-13 9:05 ` Cédric Le Goater
2023-11-13 17:40 ` Miles Glenn
2023-11-10 19:49 ` [PATCH v2 2/8] ppc/pnv: Wire up pca9552 GPIO pins " Glenn Miles
2023-11-10 19:49 ` [PATCH v2 3/8] ppc/pnv: PNV I2C engines assigned incorrect XSCOM addresses Glenn Miles
2023-11-13 9:07 ` Cédric Le Goater
2023-11-14 15:27 ` Miles Glenn [this message]
2023-11-10 19:49 ` [PATCH v2 4/8] ppc/pnv: Fix PNV I2C invalid status after reset Glenn Miles
2023-11-13 9:10 ` Cédric Le Goater
2023-11-14 15:26 ` Miles Glenn
2023-11-14 17:55 ` Cédric Le Goater
2023-11-14 18:34 ` Miles Glenn
2023-11-10 19:49 ` [PATCH v2 5/8] ppc/pnv: Use resettable interface to reset child I2C buses Glenn Miles
2023-11-10 19:49 ` [PATCH v2 6/8] misc: Add a pca9554 GPIO device model Glenn Miles
2023-11-10 19:49 ` [PATCH v2 7/8] ppc/pnv: Add a pca9554 I2C device to powernv10 Glenn Miles
2023-11-10 19:49 ` [PATCH v2 8/8] ppc/pnv: Test pnv i2c master and connected devices Glenn Miles
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=8d7e592694b2c01d8c0334db7fa04f8f99f5730b.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).