public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andrew Dyer <amdyer@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PATCH was(ack problem in common/soft_i2c.c)
Date: Tue, 26 Jul 2005 13:42:31 -0500	[thread overview]
Message-ID: <c166aa9f05072611422e9a1815@mail.gmail.com> (raw)
In-Reply-To: <42E0DABB.3030406@marekmicro.de>

On 7/22/05, Thomas Kastner <thomas.kastner@marekmicro.de> wrote:
> Andrew Dyer wrote:
> > I am working with the soft i2c code on my target and I believe
> > there is a problem in the send_ack() function.
> >
> [snip]
> > In my case changing the order to:
> >
> > I2C_SCL(0);
> > I2C_DELAY;
> > I2C_ACTIVE;
> 
> I ported U-Boot to the AT91M55800A (ARM7DTMI) which has multi-driver
> capable GPIOs, but didn't want to spend the time to change the I2C code
> and left the ACTIVE/TRISTATE mechanism - and also came across the same
> problem.
> A 24C08 worked fine, but e.g. a ADV7181 would only give me a few
> consecutive reads.
> 
> So yes, I can confirm there is a problem and also that the above
> mentioned fix is OK.
> 

Ok, here's a patch for the queue.

ChangeLog:

change the sequence of events in soft_i2c.c:send_ack() to keep from
incorrectly generating start/stop conditions on the bus.


-- 
Hardware, n.:
        The parts of a computer system that can be kicked.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: u-boot-soft_i2c.c-patch.diff
Type: text/x-patch
Size: 582 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20050726/4aa76b63/attachment.bin 

      reply	other threads:[~2005-07-26 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-11 23:05 [U-Boot-Users] ack problem in common/soft_i2c.c? Andrew Dyer
2005-07-12  7:07 ` AW: " Reinhard Meyer
2005-07-22 11:38 ` Thomas Kastner
2005-07-26 18:42   ` Andrew Dyer [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=c166aa9f05072611422e9a1815@mail.gmail.com \
    --to=amdyer@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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