From: Jean Delvare <jdelvare@suse.de>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-i2c@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] i2c: algo-bit: add support for I2C_M_STOP
Date: Wed, 21 Jun 2017 09:18:43 +0200 [thread overview]
Message-ID: <20170621091843.657de813@endymion> (raw)
In-Reply-To: <20170620172810.h2anac45n5u3oova@ninjato>
Hi Wolfram,
On Tue, 20 Jun 2017 19:28:10 +0200, Wolfram Sang wrote:
> Hi Jean,
>
> > > + bool did_stop = false;
> >
> > I'm pretty certain you want to declare and initialize this variable
> > outside the loop.
>
> Why? Well, it doesn't matter anymore but what is wrong with limiting the
> variable like this?
There's no problem with the scope. The problem is with the
initialization. The way you did, did_stop gets reset to false with
every iteration, which isn't what you want.
> > (...)
> > 1* Repeated start happens between messages of a same transaction, and
> > you handle that case above. However in the case of 10-bit address
> > clients, there is also a repeated start happening during the address
> > phase of the transaction, if the first message is a read. Did you check
> > what the SCCB protocol expects in that case?
>
> SCCB defines addresses to be 7 bit.
I looked at how 10-bit addressing works again and in fact it is simply
impossible to not use repeated start when reading from a 10-bit address
slave. Only the first 2 bits of the 10-bit address are repeated in the
read part of the transaction. If there was a stop between the two parts
then there would be no way to know which 10-bit slave should send the
data.
> > (...)
> > --- linux-4.11.orig/drivers/i2c/algos/i2c-algo-bit.c 2017-06-19 09:57:17.949074198 +0200
> > +++ linux-4.11/drivers/i2c/algos/i2c-algo-bit.c 2017-06-19 10:23:26.711088536 +0200
> > @@ -553,8 +553,17 @@ static int bit_xfer(struct i2c_adapter *
> > nak_ok = pmsg->flags & I2C_M_IGNORE_NAK;
> > if (!(pmsg->flags & I2C_M_NOSTART)) {
> > if (i) {
> > - bit_dbg(3, &i2c_adap->dev, "emitting "
> > - "repeated start condition\n");
> > + if (msgs[i - 1].flags & I2C_M_STOP) {
> > + bit_dbg(3, &i2c_adap->dev,
> > + "emitting enforced stop condition\n");
> > + i2c_stop(adap);
> > + bit_dbg(3, &i2c_adap->dev,
> > + "emitting start condition\n");
> > + i2c_start(adap);
> > + }
>
> else
Oops. Right, fixed, thanks.
>
> > +
> > + bit_dbg(3, &i2c_adap->dev,
> > + "emitting repeated start condition\n");
> > i2c_repstart(adap);
> > }
> > ret = bit_doAddress(i2c_adap, pmsg);
>
> A lot better! I like it very much. And also
>
> Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
>
> Do you want to cook up a patch or shall I? I'd just need a SoB then.
I'll send a proper patch shortly.
> Thanks for the improvement!
You're welcome.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2017-06-21 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 17:12 [PATCH] i2c: algo-bit: add support for I2C_M_STOP Wolfram Sang
2017-06-19 8:30 ` Jean Delvare
2017-06-20 17:28 ` Wolfram Sang
2017-06-21 7:18 ` Jean Delvare [this message]
2017-06-21 14:30 ` Wolfram Sang
2017-06-22 9:06 ` Jean Delvare
2017-06-22 10:15 ` Wolfram Sang
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=20170621091843.657de813@endymion \
--to=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@the-dreams.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).