From: bgat@billgatliff.com (Bill Gatliff)
To: linux-arm-kernel@lists.infradead.org
Subject: Generic GPIO I2C bitbang kernel question
Date: Fri, 02 Oct 2009 10:31:59 -0500 [thread overview]
Message-ID: <4AC61CEF.2020003@billgatliff.com> (raw)
In-Reply-To: <3d1967ab0909301917g1acc4fd4ga49eb1906a8fccf5@mail.gmail.com>
Brian Hutchinson wrote:
> Hi,
>
> I'm trying to get i2c-core gpio bitbang I2C adapter working on a picoChip
> PC205 (ARM926EJS core)
>
> I have soft i2c bit banging working in u-boot and am now trying to get it
> working in Linux.
>
What is the response time of the slave? I have at times had troubles
over-running my slave's address checking code, which would result in
false NAK reporting. The quick fix was to slow down the i2c clock to
give the slave more time to respond.
Presumably, if your hardware is working in u-boot then your pullup
resistors and other hardware must be right. But at higher speeds, is it
_really_ right? If your pullup resistors have low resistance, the slave
might not be able to sink them fast enough for the master to see the ACK.
Just a couple of things that have bitten me in the bit-bang code. But
when the above aren't issues, I have found the current implementation to
be solid. I haven't checked the .31+ kernels, but I did thoroughly test
the .30 and previous ones.
HTH,
b.g.
--
Bill Gatliff
bgat at billgatliff.com
next prev parent reply other threads:[~2009-10-02 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 2:17 Generic GPIO I2C bitbang kernel question Brian Hutchinson
2009-10-02 15:31 ` Bill Gatliff [this message]
[not found] ` <3d1967ab0910021119g5d81e8dar1056ef37ca8d4e35@mail.gmail.com>
2009-10-02 18:26 ` Bill Gatliff
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=4AC61CEF.2020003@billgatliff.com \
--to=bgat@billgatliff.com \
--cc=linux-arm-kernel@lists.infradead.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).