From: Peter Delevoryas <peter@pjd.dev>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: peter.maydell@linaro.org, andrew@aj.id.au, joel@jms.id.au,
hskinnemoen@google.com, kfting@nuvoton.com, qemu-arm@nongnu.org,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 5/5] hw/nvram/eeprom_at24c: Make reset behavior more like hardware
Date: Tue, 17 Jan 2023 10:29:52 -0800 [thread overview]
Message-ID: <Y8bpICXfvTkHMVno@pdel-mbp> (raw)
In-Reply-To: <356419e3-339d-b45e-c8d2-2e3679e701f4@kaod.org>
On Tue, Jan 17, 2023 at 08:42:46AM +0100, Cédric Le Goater wrote:
> On 1/17/23 00:56, Peter Delevoryas wrote:
> > EEPROM's are a form of non-volatile memory. After power-cycling an EEPROM,
> > I would expect the I2C state machine to be reset to default values, but I
> > wouldn't really expect the memory to change at all.
>
>
> >
> > The current implementation of the at24c EEPROM resets its internal memory on
> > reset. This matches the specification in docs/devel/reset.rst:
> >
> > Cold reset is supported by every resettable object. In QEMU, it means we reset
> > to the initial state corresponding to the start of QEMU; this might differ
> > from what is a real hardware cold reset. It differs from other resets (like
> > warm or bus resets) which may keep certain parts untouched.
> >
> > But differs from my intuition. For example, if someone writes some information
> > to an EEPROM, then AC power cycles their board, they would expect the EEPROM to
> > retain that information. It's very useful to be able to test things like this
> > in QEMU as well, to verify software instrumentation like determining the cause
> > of a reboot.
>
> Yes. should we take into account the "writable" property ? It is not set to
> false in any model but it could.
We're already using "writable" in at24c_eeprom_send to control writes, do we
need to use it anywhere else? I would assume we shouldn't use it in init/reset,
but maybe you have something specific in mind.
>
> Thanks,
>
> C.
>
> > Fixes: 5d8424dbd3e8 ("nvram: add AT24Cx i2c eeprom")
> > Signed-off-by: Peter Delevoryas <peter@pjd.dev>
> > ---
> > hw/nvram/eeprom_at24c.c | 22 ++++++++++------------
> > 1 file changed, 10 insertions(+), 12 deletions(-)
> >
> > diff --git a/hw/nvram/eeprom_at24c.c b/hw/nvram/eeprom_at24c.c
> > index bb9ee75864fe..6bcded7b496c 100644
> > --- a/hw/nvram/eeprom_at24c.c
> > +++ b/hw/nvram/eeprom_at24c.c
> > @@ -185,18 +185,6 @@ static void at24c_eeprom_realize(DeviceState *dev, Error **errp)
> > }
> > ee->mem = g_malloc0(ee->rsize);
> > -
> > -}
> > -
> > -static
> > -void at24c_eeprom_reset(DeviceState *state)
> > -{
> > - EEPROMState *ee = AT24C_EE(state);
> > -
> > - ee->changed = false;
> > - ee->cur = 0;
> > - ee->haveaddr = 0;
> > -
> > memset(ee->mem, 0, ee->rsize);
> > if (ee->blk) {
> > @@ -214,6 +202,16 @@ void at24c_eeprom_reset(DeviceState *state)
> > }
> > }
> > +static
> > +void at24c_eeprom_reset(DeviceState *state)
> > +{
> > + EEPROMState *ee = AT24C_EE(state);
> > +
> > + ee->changed = false;
> > + ee->cur = 0;
> > + ee->haveaddr = 0;
> > +}
> > +
> > static Property at24c_eeprom_props[] = {
> > DEFINE_PROP_UINT32("rom-size", EEPROMState, rsize, 0),
> > DEFINE_PROP_BOOL("writable", EEPROMState, writable, true),
>
prev parent reply other threads:[~2023-01-17 18:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 23:55 [PATCH v2 0/5] hw/nvram/eeprom_at24c: Cleanup + FRUID EEPROM init example Peter Delevoryas
2023-01-16 23:56 ` [PATCH v2 1/5] hw/arm: Extract at24c_eeprom_init helper from Aspeed and Nuvoton boards Peter Delevoryas
2023-01-17 7:12 ` Cédric Le Goater
2023-01-17 8:00 ` Philippe Mathieu-Daudé
2023-01-17 18:32 ` Peter Delevoryas
2023-01-17 22:25 ` Peter Delevoryas
2023-01-16 23:56 ` [PATCH v2 2/5] hw/arm/aspeed: Replace aspeed_eeprom_init with at24c_eeprom_init Peter Delevoryas
2023-01-16 23:56 ` [PATCH v2 3/5] hw/nvram/eeprom_at24c: Add init_rom field and at24c_eeprom_init_rom helper Peter Delevoryas
2023-01-17 7:35 ` Cédric Le Goater
2023-01-17 17:57 ` Peter Delevoryas
2023-01-16 23:56 ` [PATCH v2 4/5] hw/arm/aspeed: Add aspeed_eeprom.c Peter Delevoryas
2023-01-17 7:39 ` Cédric Le Goater
2023-01-17 8:08 ` Philippe Mathieu-Daudé
2023-01-17 9:20 ` Cédric Le Goater
2023-01-17 18:34 ` Peter Delevoryas
2023-01-17 17:59 ` Peter Delevoryas
2023-01-16 23:56 ` [PATCH v2 5/5] hw/nvram/eeprom_at24c: Make reset behavior more like hardware Peter Delevoryas
2023-01-17 7:42 ` Cédric Le Goater
2023-01-17 18:29 ` Peter Delevoryas [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=Y8bpICXfvTkHMVno@pdel-mbp \
--to=peter@pjd.dev \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=hskinnemoen@google.com \
--cc=joel@jms.id.au \
--cc=kfting@nuvoton.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@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).