public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hong Xu <hong.xu@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3 v2] ARM: ARM926EJS - Add cache operations
Date: Mon, 22 Aug 2011 10:03:42 +0800	[thread overview]
Message-ID: <4E51B8FE.2080109@atmel.com> (raw)
In-Reply-To: <CALZhoSSCNoAVtvXifnGYzmp0GN7O=S1us-UW7rMLN-mhGr3dSg@mail.gmail.com>

Hi Lei,

On 08/19/2011 06:31 PM, Lei Wen wrote:
> Hi Hong,
>
> On Fri, Aug 19, 2011 at 5:23 PM, Hong Xu<hong.xu@atmel.com>  wrote:
>> Add a new file arch/arm/cpu/arm926ejs/cache.c and put cache operations
>> into this file.
>>
>> Signed-off-by: Hong Xu<hong.xu@atmel.com>
>> Tested-by: Elen Song<elen.song@atmel.com>
>> CC: Albert Aribaud<albert.u.boot@aribaud.net>
>> ---
>> Since V1
>>     Modified copyright line
>>     Fix for compiling warnings
>>     Changed the way to use CONFIG_SYS_CACHELINE_SIZE
>>     When unaligned buffer detected, emit ERROR instead of WARNING
>>
>>     Do not make a common v5,v6 cache file. It seems arm946 is lack of
>>     Test-and-Clean DCache operation. And maybe more differents...
>>
>>   arch/arm/cpu/arm926ejs/Makefile |    2 +-
>>   arch/arm/cpu/arm926ejs/cache.c  |  135 +++++++++++++++++++++++++++++++++++++++

[..]

>> +#include<common.h>
>> +
>> +#define FLUSH_CACHE_OP         0
>> +#define INVALIDATE_CACHE_OP    1
>> +
>> +#ifndef CONFIG_SYS_CACHELINE_SIZE
>> +/*
>> + * ARM926EJ-S Technical Reference Manual, Chap 2.3.1 Table 2-9
>> + * only b'10, aka. 32 bytes cache line len is valid
>> + */
>> +#define CONFIG_SYS_CACHELINE_SIZE 32
>
> I think we shouldn't make such assumption here.
> You could refer to Lukasz's patch over armv7:
> http://permalink.gmane.org/gmane.comp.boot-loaders.u-boot/105772
> And you also should export one method as: get_dcache_line_size(), so
> that we could malloc cache aligned buffer in mmc.c.

There was a long loop about this, see
http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/105113/focus=105137

I agree we may need something like get_dcache_line_size(). This will 
make driver sane if CONFIG_SYS_CACHELINE_SIZE is not defined.

BR,
Eric


> Best regards,
> Lei

  reply	other threads:[~2011-08-22  2:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19  9:23 [U-Boot] [PATCH 1/3 v2] ARM: Clean arch/arm/lib/cache.c Hong Xu
2011-08-19  9:23 ` [U-Boot] [PATCH 2/3 v2] ARM: ARM1136 - Remove flush_cache from arch/arm/lib/cache.c Hong Xu
2011-08-19  9:40   ` Marek Vasut
2011-08-19  9:59     ` Hong Xu
2011-08-19 12:57       ` Marek Vasut
2011-10-06 21:50   ` Wolfgang Denk
2011-08-19  9:23 ` [U-Boot] [PATCH 3/3 v2] ARM: ARM926EJS - Add cache operations Hong Xu
2011-08-19  9:37   ` Aneesh V
2011-08-19  9:46     ` Marek Vasut
2011-08-19 10:43       ` Aneesh V
2011-08-19 12:55         ` Marek Vasut
2011-08-19 14:16           ` Aneesh V
2011-08-28 19:16             ` Marek Vasut
2011-08-19  9:41   ` Marek Vasut
2011-08-19 10:17   ` Lei Wen
2011-08-19 10:30     ` Hong Xu
2011-08-19 10:31   ` Lei Wen
2011-08-22  2:03     ` Hong Xu [this message]
2011-08-19 14:20   ` Aneesh V
2011-08-22  2:14     ` Hong Xu
2011-08-22  3:31       ` V, Aneesh
2011-08-19  9:38 ` [U-Boot] [PATCH 1/3 v2] ARM: Clean arch/arm/lib/cache.c Marek Vasut
  -- strict thread matches above, loose matches on Subject: below --
2011-08-11  2:53 [U-Boot] [PATCH 3/3 v2] ARM: ARM926EJS - Add cache operations Hong Xu
2011-08-18 19:56 ` Marek Vasut

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=4E51B8FE.2080109@atmel.com \
    --to=hong.xu@atmel.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