From: Guenter Roeck <guenter.roeck@ericsson.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] i2cdetect running slow but not "bus inactive" slow,
Date: Tue, 20 Dec 2011 16:18:53 +0000 [thread overview]
Message-ID: <20111220161853.GA9089@ericsson.com> (raw)
In-Reply-To: <CAN=k24=RXfkyzdLqF2=xSU6nHT28YGwFFu9TDfJihn7wg8tsLQ@mail.gmail.com>
On Tue, Dec 20, 2011 at 11:00:35AM -0500, Wayne Tams wrote:
> Hi Guenter,
>
> Turns out it was an I2C voltage translator had popped, thankfully all
> my I2C devices are ok. Did not realise i2cdetect could behave in such
> a peculiar way.
>
Hi Wayne,
please don't top-post.
Nothing to do with i2cdetect, but with the i2c bus driver. i2cdetect tries to read,
and the bus driver ends up getting a transfer timeout for each read. Depending on
the I2C bus chip and the driver, timeouts can be _very_ long, up to 500ms per read
or even more.
Guenter
> Thanks
>
> Wayne
>
> On Fri, Dec 16, 2011 at 4:29 PM, Guenter Roeck
> <guenter.roeck@ericsson.com> wrote:
> > On Fri, 2011-12-16 at 10:33 -0500, Wayne Tams wrote:
> >> Hi,
> >>
> >> i2cdetect is behaving in a fashion that I have not seen before and I
> >> just would like to know if anyone has a suggestion on what it is
> >> telling me.
> >>
> >> Normally i2cdetect returns in <1s, if the bus were inactive it would
> >> take closer to 20s. However I'm finding that the scanning is taken a
> >> round 5s and the addresses returned appear random, except for one.
> >> Obviously there must be a fault in my hardware, but I just wanted to
> >> make sure that was/wasn't a common explanation for this behaviour
> >> before I go debugging up the wrong tree.
> >
> > I typically see this kind of problem if there is something wrong on the
> > i2c bus, for example if a signal is pulled high or low. I have also seen
> > it after I managed to physically "destroy" an I2C controller by applying
> > a reversed voltage to the i2c signal pins.
> >
> > If you have a logic analyzer or a scope, you might want to connect it to
> > the clock and data lines to see what is happening on the bus.
> >
> > Guenter
> >
> >
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2011-12-20 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 15:33 [lm-sensors] i2cdetect running slow but not "bus inactive" slow, Wayne Tams
2011-12-16 16:29 ` Guenter Roeck
2011-12-20 16:00 ` Wayne Tams
2011-12-20 16:18 ` Guenter Roeck [this message]
2011-12-20 16:26 ` Wayne Tams
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=20111220161853.GA9089@ericsson.com \
--to=guenter.roeck@ericsson.com \
--cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.