From: "bart@ardistech.com" <bart@ardistech.com>
To: joakim.tjernlund@lumentis.se
Cc: Stephan Linke <Stephan.Linke@epygi.de>,
Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 8xx i2c refers to unspecified chip errata
Date: Fri, 11 Oct 2002 14:55:04 +0200 [thread overview]
Message-ID: <3DA6CA28.4F84FDFB@ardistech.com> (raw)
In-Reply-To: IGEFJKJNHJDCBKALBJLLEEAPFHAA.joakim.tjernlund@lumentis.se
Hi,
> Look in cpm_iic_read() for:
> /* flush will invalidate too. */
> flush_dcache_range((unsigned long)buf, (unsigned long)(buf+count));
>
> You can't just do invalidate_dcache_range() since it will invalidate more than your buffer
>
In my case it did invalidate the stack :(
> if it's not cache line aligned. Therefore you must flush to memory first and then invalidate.
> But you don't need an explicit invalidate_dcache_range() since flush_dcache_range() will flush to
> memory AND invalidate.
>
Better would be to have a special DMA region for this. Or as Dan suggest forget the
whole CPM IIC and do it by software.
Cheers,
Bart
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-10-11 12:55 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 20:14 8xx i2c refers to unspecified chip errata Barker Michael-r43496
2002-10-10 10:35 ` Joakim Tjernlund
2002-10-10 16:18 ` Dan Malek
2002-10-10 16:35 ` Dr. Craig Hollabaugh
2002-10-11 7:28 ` Joakim Tjernlund
2002-10-11 7:50 ` bart
2002-10-11 9:12 ` Joakim Tjernlund
2002-10-11 9:56 ` bart
2002-10-11 12:02 ` Stephan Linke
2002-10-11 12:14 ` bart
2002-10-11 12:31 ` Stephan Linke
2002-10-11 12:46 ` Joakim Tjernlund
2002-10-11 12:44 ` Joakim Tjernlund
2002-10-11 12:55 ` bart [this message]
2002-10-11 13:10 ` Joakim Tjernlund
2002-10-15 16:57 ` Tom Rini
2002-10-22 9:15 ` Joakim Tjernlund
2005-05-19 6:23 ` Joakim Tjernlund
2002-10-24 16:10 ` Tom Rini
2005-05-19 6:23 ` Tom Rini
2002-10-24 18:21 ` Joakim Tjernlund
2005-05-19 6:23 ` Joakim Tjernlund
2002-11-01 11:01 ` Joakim Tjernlund
2002-11-01 19:19 ` Tom Rini
2002-11-17 20:51 ` Mark D. Studebaker
2005-05-19 6:23 ` Mark D. Studebaker
2002-11-17 21:44 ` Joakim Tjernlund
2002-11-18 14:10 ` Tom Rini
2005-05-19 6:23 ` Tom Rini
2002-11-18 19:04 ` Mark D. Studebaker
2005-05-19 6:23 ` Mark D. Studebaker
2002-11-18 19:24 ` Joakim Tjernlund
2005-05-19 6:23 ` Joakim Tjernlund
2002-11-18 19:31 ` Tom Rini
2005-05-19 6:23 ` Tom Rini
2002-11-18 19:42 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2002-11-18 19:46 ` Tom Rini
2005-05-19 6:23 ` Tom Rini
2005-05-19 6:23 ` Joakim Tjernlund
2005-05-19 6:23 ` Mark D. Studebaker
2005-05-19 6:23 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2002-10-10 17:01 Barker Michael-r43496
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=3DA6CA28.4F84FDFB@ardistech.com \
--to=bart@ardistech.com \
--cc=Stephan.Linke@epygi.de \
--cc=joakim.tjernlund@lumentis.se \
--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.