From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Enrik Berkhan <Enrik.Berkhan-JJi787mZWgc@public.gmane.org>
Cc: Ian Campbell <icampbell-2sJRl1BP9u0AvxtiuMwx3w@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH, v2] Let PCA9564 recover from unacked data byte (state 0x30)
Date: Tue, 14 Apr 2009 19:01:07 +0200 [thread overview]
Message-ID: <20090414170107.GA4260@pengutronix.de> (raw)
In-Reply-To: <20090409093855.GB539-wEgbaqU1+uOv+36yZLenwA0JkcsJGQge@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2655 bytes --]
Hi Enrik,
one minor nit. If that is sorted out, you can add
Reviewed-by: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Thanks for the patch,
Wolfram
On Thu, Apr 09, 2009 at 11:38:55AM +0200, Enrik Berkhan wrote:
> Currently, the i2c-algo-pca driver does nothing if the chip enters state
> 0x30 (Data byte in I2CDAT has been transmitted; NOT ACK has been
> received). Thus, the i2c bus connected to the controller gets stuck
> afterwards.
>
> I have seen this kind of error on a custom board in certain load
> situations most probably caused by interference or noise.
>
> A possible reaction is to let the controller generate a STOP condition.
> This is documented in the controller data sheet and the same is done for
> other NACK states as well.
>
> Further, state 0x38 isn't handled completely, either. Try to do another
> START in this case like the manual says. As this couldn't be tested,
> I've added a comment to try to reset the chip if the START doesn't help
> as suggested by Wolfram Sang.
>
> Signed-off-by: Enrik Berkhan <Enrik.Berkhan-JJi787mZWgc@public.gmane.org>
> ---
> drivers/i2c/algos/i2c-algo-pca.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> Index: drivers/i2c/algos/i2c-algo-pca.c
> ===================================================================
> --- drivers/i2c/algos/i2c-algo-pca.c.orig 2009-04-07 11:23:08.000000000 +0200
> +++ drivers/i2c/algos/i2c-algo-pca.c 2009-04-09 11:10:11.000000000 +0200
> @@ -270,10 +270,17 @@ static int pca_xfer(struct i2c_adapter *
>
> case 0x30: /* Data byte in I2CDAT has been transmitted; NOT ACK has been received */
> DEB2("NOT ACK received after data byte\n");
> + pca_stop(adap);
> goto out;
>
> case 0x38: /* Arbitration lost during SLA+W, SLA+R or data bytes */
> DEB2("Arbitration lost\n");
> + /*
> + * The manual says to send another start
> + * condition in this case. If this won't be
A pointer, where the manual says it, is always helpful (revision, chapter, page
number or such).
> + * sufficient, try pca_reset() instead.
> + */
> + pca_start(adap);
> goto out;
>
> case 0x58: /* Data byte has been received; NOT ACK has been returned */
> --
> To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-04-14 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 10:38 [PATCH] Let PCA9564 recover from unacked data byte (state 0x30) Enrik Berkhan
[not found] ` <20090407103847.GA13586-wEgbaqU1+uOv+36yZLenwA0JkcsJGQge@public.gmane.org>
2009-04-07 21:04 ` Wolfram Sang
[not found] ` <20090407210409.GA21933-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-04-09 9:18 ` Enrik Berkhan
2009-04-09 9:38 ` [PATCH, v2] " Enrik Berkhan
[not found] ` <20090409093855.GB539-wEgbaqU1+uOv+36yZLenwA0JkcsJGQge@public.gmane.org>
2009-04-14 17:01 ` Wolfram Sang [this message]
[not found] ` <20090414170107.GA4260-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-04-15 7:45 ` [PATCH, v3] " Enrik Berkhan
[not found] ` <20090415074500.GA629-wEgbaqU1+uOv+36yZLenwA0JkcsJGQge@public.gmane.org>
2009-04-24 10:32 ` Wolfram Sang
[not found] ` <20090424103218.GE26169-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-04-24 11:33 ` Jean Delvare
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=20090414170107.GA4260@pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=Enrik.Berkhan-JJi787mZWgc@public.gmane.org \
--cc=icampbell-2sJRl1BP9u0AvxtiuMwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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