From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] arm: arm926ejs: flush cache before disable it
Date: Fri, 12 Jul 2013 09:35:19 +0200 [thread overview]
Message-ID: <20130712093519.7e234692@lilith> (raw)
In-Reply-To: <20130710173445.GA7512@Hardy>
Hi Sughosh,
On Wed, 10 Jul 2013 23:04:45 +0530, Sughosh Ganu
<urwithsughosh@gmail.com> wrote:
> hi Albert,
>
> On Wed Jul 10, 2013 at 02:30:30PM +0200, Albert ARIBAUD wrote:
>
> > > > You are correct re the other policies of the DDI0198E (ARM926EJ-S
> > > > TRM) MMU -- page 3-11, bits 3-2 of the section descriptor. Note however
> > > > that you may have to refer to your specific SoC's TRM or equivalent, as
> > > > the SoC designer may have defined its own system-level cache and MMU
> > > > architecture.
> > > >
> > > > Note in any case that none of the policies mentioned in DDI0198E is
> > > > described as read-allocate (let alone "read-allocate only" where writes
> > > > would bypass the enabled cache); on the contrary, the only cache
> > > > policies mentioned are write-through and write-back, both of which
> > > > contradict cache bypass on write.
> > >
> > > I was referring to the cache allocation policy mentioned in section
> > > 4.1 in the DDI0198E document -- this is also mentioned in table 12.1
> > > in chapter 12 of the arm developers guide.
> >
> > Can you please quote the exact part of 4.1 which describes the cache
> > policy and then explain what you think it means exactly?
>
> I was referring to this particular point in section 4.1
> "Allocate on read-miss is supported. The caches perform critical-word
> first cache refilling."
This is not equivalent to "the cache policy is read-allocate".
This paragraph does not specify the cache's general policy, only a read
policy, and only the *read allocation* policy. Its write policies are
not defined or even constrained by this paragraph.
> Based on the cache line allocation policies described in section
> 12.3.3 in the arm developers guide, my interpretation of 'allocate on
> read-miss' was as above.
The ARM926EJ-S is "allocate on read-miss" as well as "allocate on
write-miss"; and none of its write policies bypasses the cache.
> -sughosh
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-07-12 7:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 12:35 [U-Boot] [RFC PATCH] arm: arm926ejs: flush cache before disable it Bo Shen
2013-07-05 21:02 ` Albert ARIBAUD
2013-07-07 23:33 ` Bo Shen
2013-07-08 10:22 ` Albert ARIBAUD
2013-07-08 12:08 ` Sughosh Ganu
2013-07-08 12:32 ` Albert ARIBAUD
2013-07-08 14:07 ` Sughosh Ganu
2013-07-08 19:55 ` Albert ARIBAUD
2013-07-09 3:59 ` Sughosh Ganu
2013-07-09 6:11 ` Sughosh Ganu
2013-07-09 8:28 ` Albert ARIBAUD
2013-07-10 10:05 ` Sughosh Ganu
2013-07-10 12:30 ` Albert ARIBAUD
2013-07-10 17:34 ` Sughosh Ganu
2013-07-12 7:35 ` Albert ARIBAUD [this message]
2013-07-08 12:19 ` Sughosh Ganu
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=20130712093519.7e234692@lilith \
--to=albert.u.boot@aribaud.net \
--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