linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	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:01:46 +0000	[thread overview]
Message-ID: <20101208040146.GP20097@trinity.fluff.org> (raw)
In-Reply-To: <20101207160739.0d7141f3-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>

On Tue, Dec 07, 2010 at 04:07:39PM +0100, Jean Delvare wrote:
> Hi Ben,
> 
> On Tue, 7 Dec 2010 11:53:25 +0000, Ben Dooks 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.

> > > +	if (bit_adap->getscl == NULL) {
> > > +		dev_warn(&adap->dev, "Not I2C compliant: can't read SCL\n");
> > 
> > I'll have a think about wording. I might be able to improve it.
> > 
> > As a note, I always prefer cannot to can't. 
> 
> And I thought you were a busy developer ;)

I've my reasons for this, blame my parents.
 
> There is no trend one way or another, neither in the kernel tree nor
> even in drivers/i2c specifically.

no, just my preference.
 
> > > +		dev_warn(&adap->dev, "Bus may be unreliable\n");
> > 
> > if there are any other warnings, should we print just one unreliable warning
> > at the end of the scan?
> 
> I'm not sure what "scan" you refer to, and in all honesty I'm not sure
> I get your point at all.

ok, looking at the code it isn't important.

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

  parent reply	other threads:[~2010-12-08  4:01 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 [this message]
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

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=20101208040146.GP20097@trinity.fluff.org \
    --to=ben-i2c-elnmno+kys3ytjvyw6ydsg@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).