From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: "Ben Dooks (embedded platforms)" <ben-linux@fluff.org>,
Wolfram Sang <w.sang@pengutronix.de>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: i2c-i801 retries on lost arbitration (resent: no gpg)
Date: Fri, 30 Apr 2010 13:07:09 +0300 [thread overview]
Message-ID: <20100430100709.GD3553@swordfish.minsk.epam.com> (raw)
In-Reply-To: <20100430114822.1a5e0cf9@hyperion.delvare>
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
On (04/30/10 11:48), Jean Delvare wrote:
> Hi Sergey,
>
>
> > Both i2c spec and ICH7 datasheet requires to restart transaction in
> > case of lost arbitration.
> >
> > "No information is lost during the arbitration process. A master that
> > loses the arbitration can generate clock pulses until the end of the
> > byte in which it loses the arbitration and must restart its transaction
> > when the bus is idle."
> >
> > Please see the following patch. Is it correct?
>
> No, it's not. As you wrote above, this is not specific to the Intel ICH
> but a general I2C issue. As such it must be handled in i2c-core and not
> by individual drivers. And as a matter of fact, it is already handled.
> Look at functions i2c_transfer and i2c_smbus_xfer in i2c-core.c, see
> the comments "Retry automatically on arbitration loss", the code is
> already there. It's just a matter of bus drivers properly setting
> adapter->retries (which i2c-i801.c does already.)
>
Thanks.
> So I don't know which kernel you're using, but with the latest upstream
> kernel, things should work just fine already.
>
OK. Thanks a lot.
Sergey
[-- Attachment #2: Type: application/pgp-signature, Size: 316 bytes --]
prev parent reply other threads:[~2010-04-30 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 9:44 i2c-i801 retries on lost arbitration (resent: no gpg) Sergey Senozhatsky
2010-04-30 9:48 ` Jean Delvare
2010-04-30 10:07 ` Sergey Senozhatsky [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=20100430100709.GD3553@swordfish.minsk.epam.com \
--to=sergey.senozhatsky@gmail.com \
--cc=ben-linux@fluff.org \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=w.sang@pengutronix.de \
/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).