public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Tom Deconinck" <t.deconinck@gmail.com>
To: ecos-devel@ecos.sourceware.org
Subject: Re: i2c driver for at91sam7x
Date: Mon, 10 Nov 2008 10:34:00 -0000	[thread overview]
Message-ID: <e37cb5250811100234v118babb7j1992b2da5f47e487@mail.gmail.com> (raw)
In-Reply-To: <e37cb5250811100228r502511f7qd34d94f5d83862ee@mail.gmail.com>

On Fri, Nov 7, 2008 at 5:14 PM, Andrew Lunn <andrew@lunn.ch> wrote:
>
> On Fri, Nov 07, 2008 at 08:39:23PM +0530, vibisreenivasan wrote:
> > hello,
> >       Is there any one working on i2c bus driver for at91sam7x.
>
> I know eCosCentric have one, but you need to pay for that.
>
> Other people have mentioned writing i2c drivers as well.
>
> However, you need to be careful. The i2c hardware is broken. The Linux
> kernel marks it as such. See:
>
> http://www.at91.com/samphpbb/viewtopic.php?t=4665&sid=1032a7cdc95b571dc784adb204d78d33
>
> From what i understand, if you are doing transfers of 1 byte, it is
> O.K, but multiple byte transfers can break.
>
> Writing a GPIO based driver should be reasonably easy as far as i
> understand and does not suffer from these problems.
>
>        Andrew

I have written such a driver some time ago, but I changed jobs since,
so I don't have access to the source anymore.
My experience: use GPIO and the eCos bit-banging interface, since the
hardware implementation is seriously broken.
The driver I wrote didn't work well using interrupts (latency problems
combined with a 'smart' hardware implementation that decides to
generate stop-conditions by itself, breaking multy-byte transfers,
etc.) It did work in polling mode.

Tom

      parent reply	other threads:[~2008-11-10 10:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1226070563.4223.2.camel@localhost.localdomain>
2008-11-07 16:22 ` Andrew Lunn
     [not found]   ` <e37cb5250811100228r502511f7qd34d94f5d83862ee@mail.gmail.com>
2008-11-10 10:34     ` Tom Deconinck [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=e37cb5250811100234v118babb7j1992b2da5f47e487@mail.gmail.com \
    --to=t.deconinck@gmail.com \
    --cc=ecos-devel@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).