From: Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
Mark Brown
<broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>,
Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 2/2] i2c-algo-bit: Complain about masters which can't read SCL
Date: Wed, 8 Dec 2010 04:03:47 +0000 [thread overview]
Message-ID: <20101208040347.GQ20097@trinity.fluff.org> (raw)
In-Reply-To: <20101207162933.3ad206a8-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
On Tue, Dec 07, 2010 at 04:29:33PM +0100, Jean Delvare wrote:
> Hi Marc, Ben,
>
> On Tue, 7 Dec 2010 12:30:11 +0000, Ben Dooks wrote:
> > On Tue, Dec 07, 2010 at 12:10:10PM +0000, Mark Brown wrote:
> > > On Tue, Dec 07, 2010 at 11:07:05AM +0100, Jean Delvare wrote:
> > > > The I2C specification explicitly describes both SDA and SCL as
> > > > bidirectional lines. An I2C master with a read-only SCL is thus not
> > > > compliant. If a slow slave stretches the clock, errors will happen,
> > > > so the bus can't be considered as reliable.
> > > >
> > > > Signed-off-by: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
> > >
> > > It'd be good to also flag this via sysfs so that it's more readily
> > > visible to things like diagnostic tools.
>
> In what form do you expect this, and what do you expect diagnostic
> tools to do about it?
>
> I can't think of anything straightforward and useful. We could abuse
> one functionality flag for unreliable masters, but then this is a
> boolean flag, with no way to report the actual problem to the customer.
> And write-only SCL is only one thing they can do wrongly.
Hmm, something to think about.
> > Could be, I wonder how many other hardware based adapters just don't
> > do this. Quite a few devices i've seen don't use it as they're generally
> > fast enough, or implement some other status polling system.
>
> I don't know either, and I didn't mean to provide a general solution to
> this problem as I have no clue so far that a general problem exists.
> This patch is in response to the thread started by Matthias Zacharias
> where we were troubleshooting his I2C bus problems. I just wanted to
> make sure that the same problem doesn't happen again, i.e. developers
> don't set getscl to NULL in the hope that it will help in any way.
yes, sounds good.
> I don't know of that many pieces of hardware driven by i2c-algo-bit and
> not having a bidirectional SCL line. In fact I only know of the
> i2c-parport, i2c-parport-light and i2c-gpio drivers doing this, and
> then again, only for some of the supported devices. So I'm not sure
> there is much point in spending a lot of time on this.
I was talking all hardware, not just ones integrated with this specific
driver. Not to worry, this is just rambling on.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
prev parent reply other threads:[~2010-12-08 4:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 10:07 [PATCH 2/2] i2c-algo-bit: Complain about masters which can't read SCL Jean Delvare
[not found] ` <20101207110705.69792a1a-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2010-12-07 11:53 ` Ben Dooks
[not found] ` <20101207115325.GN20097-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2010-12-07 15:07 ` Jean Delvare
[not found] ` <20101207160739.0d7141f3-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2010-12-08 4:01 ` Ben Dooks
2010-12-07 12:10 ` Mark Brown
[not found] ` <20101207121009.GD10722-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2010-12-07 12:30 ` Ben Dooks
[not found] ` <20101207123011.GO20097-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2010-12-07 15:29 ` Jean Delvare
[not found] ` <20101207162933.3ad206a8-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2010-12-07 15:35 ` Mark Brown
2010-12-08 4:03 ` Ben Dooks [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=20101208040347.GQ20097@trinity.fluff.org \
--to=ben-i2c-elnmno+kys3ytjvyw6ydsg@public.gmane.org \
--cc=broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@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;
as well as URLs for NNTP newsgroup(s).