From: "bart@ardistech.com" <bart@ardistech.com>
To: Dan Malek <dan@embeddededge.com>
Cc: Alex Zeffertt <ajz@cambridgebroadband.com>,
Embedded Linux PPC List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: MPC823: i2c-algo-8xx read interrupt?
Date: Mon, 11 Feb 2002 13:13:05 +0100 [thread overview]
Message-ID: <3C67B551.75074F10@ardistech.com> (raw)
In-Reply-To: 3C6410F1.4000104@embeddededge.com
>
> > ..... Alternatively, turn off the TX
> > interrupt and use the RX interrupt instead....
>
I turned of the TX interrupt and used the RX interrupt, and this very often works :(
But not always. Approx. one out of 300 reads (reading one byte off a I2C expander chip)
the RX interrupt gets 'lost' (in the CPM?). Maybe the distance in time between the RX
and TX internal interrupt flags get to close and one of them wins? Or something like
Wolgang Denk found in RISC timers overwriting port B data register, but now parts
of the RISC software competing for the I2CER?
Anyway, I now use the TX interrupt again because the RX is not reliable.
Bart
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-11 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 15:18 MPC823: i2c-algo-8xx read interrupt? bart
2002-02-08 17:04 ` Dan Malek
[not found] ` <3C640C11.4080407@cambridgebroadband.com>
[not found] ` <3C6410F1.4000104@embeddededge.com>
2002-02-11 12:13 ` bart [this message]
[not found] ` <3C6776CC.634AB65D@ardistech.com>
2002-02-11 15:30 ` Dan Malek
2002-02-11 15:45 ` bart
2002-02-11 16:02 ` Dan Malek
2002-02-11 16:19 ` bart
-- strict thread matches above, loose matches on Subject: below --
2002-02-11 15:49 Pergola, Michael
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=3C67B551.75074F10@ardistech.com \
--to=bart@ardistech.com \
--cc=ajz@cambridgebroadband.com \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.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).