qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 4/8] ppc/pnv: Fix PNV I2C invalid status after reset
Date: Tue, 14 Nov 2023 12:34:02 -0600	[thread overview]
Message-ID: <105757d802eb509315a71426b5f0b794664aa42e.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <38f88e9d-7679-4cd6-b117-3c893f9e3e7c@kaod.org>

On Tue, 2023-11-14 at 18:55 +0100, Cédric Le Goater wrote:
> On 11/14/23 16:26, Miles Glenn wrote:
> > On Mon, 2023-11-13 at 10:10 +0100, Cédric Le Goater wrote:
> > > On 11/10/23 20:49, Glenn Miles wrote:
> > > > The PNV I2C Controller was clearing the status register
> > > > after a reset without repopulating the "upper threshold
> > > > for I2C ports", "Command Complete" and the SCL/SDA input
> > > > level fields.
> > > > 
> > > > Fixed this for resets caused by a system reset as well
> > > > as from writing to the "Immediate Reset" register.
> > > > 
> > > > Signed-off-by: Glenn Miles <milesg@linux.vnet.ibm.com>
> > > > ---
> > > >    hw/ppc/pnv_i2c.c | 42 ++++++++++++++++++------------------
> > > > ------
> > > >    1 file changed, 18 insertions(+), 24 deletions(-)
> > > > 
> > > > diff --git a/hw/ppc/pnv_i2c.c b/hw/ppc/pnv_i2c.c
> > > > index b2c738da50..f80589157b 100644
> > > > --- a/hw/ppc/pnv_i2c.c
> > > > +++ b/hw/ppc/pnv_i2c.c
> > > > @@ -462,6 +462,23 @@ static uint64_t pnv_i2c_xscom_read(void
> > > > *opaque, hwaddr addr,
> > > >        return val;
> > > >    }
> > > >    
> > > > +static void pnv_i2c_reset(void *dev)
> > > > +{
> > > > +    PnvI2C *i2c = PNV_I2C(dev);
> > > > +
> > > > +    memset(i2c->regs, 0, sizeof(i2c->regs));
> > > > +
> > > > +    i2c->regs[I2C_STAT_REG] =
> > > > +        SETFIELD(I2C_STAT_UPPER_THRS, 0ull, i2c->num_busses -
> > > > 1) |
> > > > +        I2C_STAT_CMD_COMP | I2C_STAT_SCL_INPUT_LEVEL |
> > > > +        I2C_STAT_SDA_INPUT_LEVEL;
> > > > +    i2c->regs[I2C_EXTD_STAT_REG] =
> > > > +        SETFIELD(I2C_EXTD_STAT_FIFO_SIZE, 0ull,
> > > > PNV_I2C_FIFO_SIZE)
> > > > +        SETFIELD(I2C_EXTD_STAT_I2C_VERSION, 0ull, 23); /* last
> > > > version */
> > > > +
> > > > +    fifo8_reset(&i2c->fifo);
> > > > +}
> > > > +
> > > >    static void pnv_i2c_xscom_write(void *opaque, hwaddr addr,
> > > >                                    uint64_t val, unsigned size)
> > > >    {
> > > > @@ -499,16 +516,7 @@ static void pnv_i2c_xscom_write(void
> > > > *opaque,
> > > > hwaddr addr,
> > > >            break;
> > > >    
> > > >        case I2C_RESET_I2C_REG:
> > > > -        i2c->regs[I2C_MODE_REG] = 0;
> > > > -        i2c->regs[I2C_CMD_REG] = 0;
> > > > -        i2c->regs[I2C_WATERMARK_REG] = 0;
> > > > -        i2c->regs[I2C_INTR_MASK_REG] = 0;
> > > > -        i2c->regs[I2C_INTR_COND_REG] = 0;
> > > > -        i2c->regs[I2C_INTR_RAW_COND_REG] = 0;
> > > > -        i2c->regs[I2C_STAT_REG] = 0;
> > > > -        i2c->regs[I2C_RESIDUAL_LEN_REG] = 0;
> > > > -        i2c->regs[I2C_EXTD_STAT_REG] &=
> > > > -            (I2C_EXTD_STAT_FIFO_SIZE |
> > > > I2C_EXTD_STAT_I2C_VERSION);
> > > > +        pnv_i2c_reset(i2c);
> > > 
> > > or simply call device_cold_reset()
> > > 
> > > 
> > > Thanks,
> > > 
> > > C.
> > > 
> > 
> > The device_cold_reset() function performs a recursive reset, which
> > I believe performs a reset on the specified device as well as a
> > reset
> > on all child devices.  For the case of doing an "immediate reset"
> > of
> > the i2c controller, I think we just want to reset the i2c
> > controller
> > and not any child devices, so I think I prefer leaving it how it is
> > if that is ok.
> 
> OK. Is is a fix for 8.2 ?
> 
> Thanks,
> 
> C.
> 

Yes, I will send out a v3 stating that.

Thanks,

Glenn

> 
> > Thanks,
> > 
> > Glenn
> > 
> > > 
> > > >            break;
> > > >    
> > > >        case I2C_RESET_ERRORS:
> > > > @@ -620,20 +628,6 @@ static int
> > > > pnv_i2c_dt_xscom(PnvXScomInterface
> > > > *dev, void *fdt,
> > > >        return 0;
> > > >    }
> > > >    
> > > > -static void pnv_i2c_reset(void *dev)
> > > > -{
> > > > -    PnvI2C *i2c = PNV_I2C(dev);
> > > > -
> > > > -    memset(i2c->regs, 0, sizeof(i2c->regs));
> > > > -
> > > > -    i2c->regs[I2C_STAT_REG] = I2C_STAT_CMD_COMP;
> > > > -    i2c->regs[I2C_EXTD_STAT_REG] =
> > > > -        SETFIELD(I2C_EXTD_STAT_FIFO_SIZE, 0ull,
> > > > PNV_I2C_FIFO_SIZE)
> > > > -        SETFIELD(I2C_EXTD_STAT_I2C_VERSION, 0ull, 23); /* last
> > > > version */
> > > > -
> > > > -    fifo8_reset(&i2c->fifo);
> > > > -}
> > > > -
> > > >    static void pnv_i2c_realize(DeviceState *dev, Error **errp)
> > > >    {
> > > >        PnvI2C *i2c = PNV_I2C(dev);



  reply	other threads:[~2023-11-14 18:34 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
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 [this message]
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=105757d802eb509315a71426b5f0b794664aa42e.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).