From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM1136: Fix cache_flush() error and correct cpu_init_crit() comments
Date: Mon, 10 May 2010 16:02:40 +0200 [thread overview]
Message-ID: <4BE81200.7070700@googlemail.com> (raw)
In-Reply-To: <1273093774-10836-1-git-send-email-gdavis@mvista.com>
Hi George,
On 05.05.2010 23:09, George G. Davis wrote:
> The ARM1136 cache_flush() function uses the "mcr p15, 0, rn, c7, c7, 0"
> instruction which means "Invalidate Both Caches
... Also flushes the branch target cache"
> " when in fact the intent
> is to "Clean and Invalidate Entire Data Cache".
Why don't we have to invalidate/flush the I- and BT-Cache here? I.e.
why is it sufficient to clean & invalidate the D-Cache here, only, and
remove the existing I- and BT-Cache invalidation/flushing?
What's about just adding an additional clean of the data cache before
the 'invalidate all':
+ asm ("mcr p15, 0, %0, c7, c10, 0": :"r" (i)); /* clean entire data
cache */
asm ("mcr p15, 0, %0, c7, c7, 0": :"r" (i)); /* invalidate both
caches and flush btb */
asm ("mcr p15, 0, %0, c7, c10, 4": :"r" (i)); /* mem barrier to sync
things */
?
Thanks for finding this and best regards
Dirk
next prev parent reply other threads:[~2010-05-10 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 21:09 [U-Boot] [PATCH] ARM1136: Fix cache_flush() error and correct cpu_init_crit() comments George G. Davis
2010-05-10 14:02 ` Dirk Behme [this message]
2010-05-11 3:33 ` George G. Davis
2010-05-11 8:56 ` Wolfgang Denk
2010-05-11 13:13 ` George G. Davis
2010-05-11 14:15 ` [U-Boot] [PATCH v2] " gdavis at mvista.com
2010-05-13 9:41 ` Dirk Behme
2010-05-28 15:12 ` George G. Davis
2010-06-01 14:38 ` Tom Rix
2010-06-02 3:02 ` George G. Davis
-- strict thread matches above, loose matches on Subject: below --
2010-05-05 20:57 [U-Boot] [PATCH] " George G. Davis
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=4BE81200.7070700@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=u-boot@lists.denx.de \
/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