From: Joe Komlodi <komlodi@google.com>
To: qemu-devel@nongnu.org
Cc: venture@google.com, komlodi@google.com, minyard@acm.org
Subject: [PATCH v2 0/3] hw/i2c: smbus: Reset fixes
Date: Fri, 26 Jan 2024 00:55:38 +0000 [thread overview]
Message-ID: <20240126005541.1839038-1-komlodi@google.com> (raw)
Changelog:
v1 -> v2
- Dropped 4th patch "hw/i2c: smbus: mux: Reset SMBusDevice state
on reset". After more testing and Corey's comment, I realized it
wasn't needed.
Original message:
Hi all,
This series adds some resets for SMBus and for the I2C core. Along with
it, we make SMBus slave error printing a little more helpful.
These reset issues were very infrequent, they would maybe occur in 1 out
of hundreds of resets in our testing, but the way they happen is pretty
straightforward.
Basically as long as a reset happens in the middle of a transaction, the
state of the old transaction would still partially be there after the
reset. Once a new transaction comes in, the partial stale state can
cause the new transaction to incorrectly fail.
Thanks,
Joe
Joe Komlodi (3):
hw/i2c: core: Add reset
hw/i2c/smbus_slave: Add object path on error prints
hw/i2c: smbus_slave: Reset state on reset
hw/i2c/core.c | 30 +++++++++++++++++++++++++-----
hw/i2c/smbus_slave.c | 17 +++++++++++++++--
include/hw/i2c/i2c.h | 6 +++++-
3 files changed, 45 insertions(+), 8 deletions(-)
--
2.43.0.429.g432eaa2c6b-goog
next reply other threads:[~2024-01-26 0:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 0:55 Joe Komlodi [this message]
2024-01-26 0:55 ` [PATCH v2 1/3] hw/i2c: core: Add reset Joe Komlodi
2024-02-01 15:24 ` Peter Maydell
2024-02-02 20:44 ` Joe Komlodi
2024-01-26 0:55 ` [PATCH v2 2/3] hw/i2c/smbus_slave: Add object path on error prints Joe Komlodi
2024-02-01 15:14 ` Peter Maydell
2024-01-26 0:55 ` [PATCH v2 3/3] hw/i2c: smbus_slave: Reset state on reset Joe Komlodi
2024-02-01 15:25 ` Peter Maydell
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=20240126005541.1839038-1-komlodi@google.com \
--to=komlodi@google.com \
--cc=minyard@acm.org \
--cc=qemu-devel@nongnu.org \
--cc=venture@google.com \
/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).