public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Albrecht Dreß" <albrecht.dress@arcor•de>
To: joakim.tjernlund@transmode•se
Cc: linuxppc-dev@ozlabs•org, devicetree-discuss@lists•ozlabs.org,
	ben-linux@fluff•org, iws@ovro•caltech.edu
Subject: Re: [Patch v2 1/2] 5200/mpc: improve i2c bus error recovery
Date: Thu, 18 Feb 2010 10:09:23 +0100 (CET)	[thread overview]
Message-ID: <33411516.1266484163759.JavaMail.ngmail@webmail09.arcor-online.net> (raw)
In-Reply-To: <OF3D88A7A0.9A4F1639-ONC12576CE.002C0FB9-C12576CE.002CCBBB@transmode.se>


[-- Attachment #1.1: Type: text/plain, Size: 897 bytes --]

Hi Joakim:

> Does this reset sequence also send a START condition for every clock?

Please see the attached scan from a scope output, showing the first two out of the 9 sequences at 375 kHz (that's what the 5200's divider makes from 400 kHz requested).  Resolution is 2us/div and 1V/div for both signals.  The waveform itself for each of the 9 sequences is exactly the same we had before with the old solution, just the timing is faster and adjusted to the ii2c clock, i.e. the /relative/ waveforms look identical for slower clocks.

Any insight if this is *really* correct would be great, as I'm not an i2c expert.  I can only say it reliably fixes the bus hangs I saw!

Thanks,
Albrecht.

Immer auf dem Laufenden! Sport, Auto, Reise, Politik und Promis. Von uns für Sie: der neue Arcor.de-Newsletter!
Jetzt anmelden und einfach alles wissen: http://www.arcor.de/rd/footer.newsletter

[-- Attachment #2: i2c-fixup.png --]
[-- Type: image/png, Size: 17960 bytes --]

  reply	other threads:[~2010-02-18  9:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 18:59 [Patch v2 1/2] 5200/mpc: improve i2c bus error recovery Albrecht Dreß
2010-02-17 20:10 ` Grant Likely
2010-02-18  8:09 ` Joakim Tjernlund
2010-02-18  9:09   ` Albrecht Dreß [this message]
2010-02-18 12:33     ` Joakim Tjernlund
2010-02-18 13:23 ` Joakim Tjernlund
2010-05-05 22:09 ` Ira W. Snyder
2010-05-06 17:54   ` Albrecht Dreß
2010-05-06 18:06     ` Grant Likely
2010-05-16 17:47       ` Albrecht Dreß
2010-05-19 16:02         ` Grant Likely
2010-06-16 19:30           ` Albrecht Dreß
2013-03-13  5:30 ` panpan2523
  -- strict thread matches above, loose matches on Subject: below --
2010-02-18 15:04 Albrecht Dreß
2010-02-18 17:14 ` Joakim Tjernlund
2010-02-18 17:41   ` Grant Likely
2010-02-18 18:07     ` Joakim Tjernlund
2010-02-18 18:45   ` Albrecht Dreß

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=33411516.1266484163759.JavaMail.ngmail@webmail09.arcor-online.net \
    --to=albrecht.dress@arcor$(echo .)de \
    --cc=ben-linux@fluff$(echo .)org \
    --cc=devicetree-discuss@lists$(echo .)ozlabs.org \
    --cc=iws@ovro$(echo .)caltech.edu \
    --cc=joakim.tjernlund@transmode$(echo .)se \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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