From: "Joakim Tjernlund" <Joakim.Tjernlund@lumentis.se>
To: <kd@flaga.is>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: RE:CPM interrupts raised to early? (was More I2C stuff,)
Date: Mon, 29 Oct 2001 22:45:51 +0100 [thread overview]
Message-ID: <000701c160c3$1465f540$23d9b5d4@jocke> (raw)
Hi Kari
This rings a bell in my mind. There is(was?) a line early in the irq routine
where i2cmod(?) is disabled(there is a comment that states that this is
due to some chip errata).
First a commeted this line and my I2C was starting to work. Later
I moved it to someplace directly after IRQ context and now my I2C is
working fine. Do you know what this "chip errata" referes to? I could
not find any reference to this in any Motorola doc.
If you want, I can send you my version of the i2c-algo-8xx.c driver(I am at
home
now and don't have access to the driver now)
Regards
Joakim Tjernlund
PS.
I am also using motorola I2C microcode patch
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-10-29 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 21:45 Joakim Tjernlund [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-29 15:07 RE:CPM interrupts raised to early? (was More I2C stuff,) Kári Davíðsson
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='000701c160c3$1465f540$23d9b5d4@jocke' \
--to=joakim.tjernlund@lumentis.se \
--cc=kd@flaga.is \
--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