From: "bart@ardistech.com" <bart@ardistech.com>
To: Embedded Linux PPC List <linuxppc-embedded@lists.linuxppc.org>,
dmalek@jlc.net
Subject: MPC823: i2c-algo-8xx read interrupt?
Date: Fri, 08 Feb 2002 16:18:17 +0100 [thread overview]
Message-ID: <3C63EC39.ACEECA08@ardistech.com> (raw)
Hi,
When testing with i2c reading an eeprom on a MPC823e I get the message "IIC
read; complete but rbuf empty". IMHO this is because the interrupt in the TX
buffer is enabled intead of the the interrupt of the RX buffer. Is this a bug
or is there a reason behind this?
Best regards,
Bart Thissen, Ardis Technologies bv
i2c-algo-8xx.c: cpm_iic_read
Original (with TX interrupt and warning)
tbdf->cbd_datlen = count + 1;
tbdf->cbd_sc =
BD_SC_READY | BD_SC_INTRPT | BD_SC_LAST |
BD_SC_WRAP | BD_IIC_START;
rbdf->cbd_datlen = 0;
rbdf->cbd_bufaddr = __pa(buf);
rbdf->cbd_sc = BD_SC_EMPTY | BD_SC_WRAP;
With RX interrupt (without warning):
tbdf->cbd_datlen = count + 1;
tbdf->cbd_sc =
BD_SC_READY | BD_SC_LAST |
BD_SC_WRAP | BD_IIC_START;
rbdf->cbd_datlen = 0;
rbdf->cbd_bufaddr = __pa(buf);
rbdf->cbd_sc = BD_SC_EMPTY | BD_SC_WRAP | BD_SC_INTRPT;
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-02-08 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 15:18 bart [this message]
2002-02-08 17:04 ` MPC823: i2c-algo-8xx read interrupt? Dan Malek
[not found] ` <3C640C11.4080407@cambridgebroadband.com>
[not found] ` <3C6410F1.4000104@embeddededge.com>
2002-02-11 12:13 ` bart
[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=3C63EC39.ACEECA08@ardistech.com \
--to=bart@ardistech.com \
--cc=dmalek@jlc.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.