public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] OMAP3 Move cache routines to cache.S
Date: Wed, 12 Aug 2009 17:38:51 -0500	[thread overview]
Message-ID: <4A83447B.3010304@windriver.com> (raw)
In-Reply-To: <20090812211316.GF21725@game.jcrosoft.org>

Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 10:42 Wed 12 Aug     , Tom Rix wrote:
>   
>> v7_flush_dcache_all, because it depends on omap ROM code is not
>> generic.  Rename the function to 'invalidate_dcache' and move it
>> to the omap cpu directory.
>>
>>     
<snip>

> for the l2 cache ACK
> for the invalidate cache NACK
>
> we do not need to call the rom code as the armv7 flush cache work fine
> on omap3 and duplicate armv7 code with really few code (non needed) no
>
>   
Jean,

I disagree on the invalidate cache NAK.

First, you were fine with change earlier
 From an earlier email.

flush_dcache was chosen to match other boards/cpu's and one of the
> main reasons for this change.  If Jean is ok changing flush_dcache
> to invalidate_dcache,  I will make that change too.

invalidate_dcache is fine for me

Best Regards,
J.


Second, removing the invalidate_dcache will change OMAP.
This is different from this change which is really just moving code around.
As a separate change, it should be submitted as a new change.

Without moving invalidate_dcache and the l2_* functions to cache.S,
we are so close to where we are now, with l2_* in cache.c that I am
not sure what you really want.

Tom
> Best Regards,
> J.
>   

  reply	other threads:[~2009-08-12 22:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-12 15:42 [U-Boot] RE ARM Cortex8 Rename and move v7_flush_dcache_all to flush_dcache Tom Rix
2009-08-12 15:42 ` [U-Boot] [PATCH] OMAP3 Move cache routines to cache.S Tom Rix
2009-08-12 16:35   ` Dirk Behme
2009-08-12 21:13   ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-12 22:38     ` Tom [this message]
2009-08-12 21:49   ` Wolfgang Denk
2009-08-12 22:17     ` Tom
2009-09-10 23:39   ` Paulraj, Sandeep
2009-09-11  1:11     ` Tom

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=4A83447B.3010304@windriver.com \
    --to=tom.rix@windriver.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