From: Stefan Hajnoczi <stefanha@gmail.com>
To: Andrzej Zaborowski <balrog@zabor.org>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
Marcus Comstedt <marcus@mc.pp.se>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] bitbang_i2c: Fix spurious slave read after NACK
Date: Sat, 28 May 2011 20:52:29 +0100 [thread overview]
Message-ID: <BANLkTinbdHYTdPgmZHwUBOb4xEmA=mjHnQ@mail.gmail.com> (raw)
In-Reply-To: <yf9sjryq3gn.fsf@chiyo.mc.pp.se>
On Sat, May 28, 2011 at 3:55 PM, Marcus Comstedt <marcus@mc.pp.se> wrote:
> After NACKing a read operation, a raising SCL should not trigger a new
> read from the slave. Introduce a new state which just waits for a stop
> or start condition after NACK.
>
> Signed-off-by: Marcus Comstedt <marcus@mc.pp.se>
> ---
> hw/bitbang_i2c.c | 5 ++++-
> 1 files changed, 4 insertions(+), 1 deletions(-)
Seems like a simple change but I'm not familiar with the code or I2C
details. Andrzej, care to take a look?
> diff --git a/hw/bitbang_i2c.c b/hw/bitbang_i2c.c
> index 4ee99a1..2937b5c 100644
> --- a/hw/bitbang_i2c.c
> +++ b/hw/bitbang_i2c.c
> @@ -38,7 +38,8 @@ typedef enum bitbang_i2c_state {
> RECEIVING_BIT2,
> RECEIVING_BIT1,
> RECEIVING_BIT0,
> - SENDING_ACK
> + SENDING_ACK,
> + SENT_NACK
> } bitbang_i2c_state;
>
> struct bitbang_i2c_interface {
> @@ -115,6 +116,7 @@ int bitbang_i2c_set(bitbang_i2c_interface *i2c, int line, int level)
> }
> switch (i2c->state) {
> case STOPPED:
> + case SENT_NACK:
> return bitbang_i2c_ret(i2c, 1);
>
> case SENDING_BIT7 ... SENDING_BIT0:
> @@ -155,6 +157,7 @@ int bitbang_i2c_set(bitbang_i2c_interface *i2c, int line, int level)
> i2c->state = RECEIVING_BIT7;
> if (data != 0) {
> DPRINTF("NACKED\n");
> + i2c->state = SENT_NACK;
> i2c_nack(i2c->bus);
> } else {
> DPRINTF("ACKED\n");
> --
> 1.7.4.1
>
>
>
next prev parent reply other threads:[~2011-05-28 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 14:55 [Qemu-devel] [PATCH] bitbang_i2c: Fix spurious slave read after NACK Marcus Comstedt
2011-05-28 19:52 ` Stefan Hajnoczi [this message]
2011-05-29 1:49 ` [Qemu-devel] [Qemu-trivial] " andrzej zaborowski
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='BANLkTinbdHYTdPgmZHwUBOb4xEmA=mjHnQ@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=balrog@zabor.org \
--cc=marcus@mc.pp.se \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).