All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC/PATCH] davinci: disable dcache on boards with EMAC
Date: Mon, 28 Nov 2011 13:56:50 +0100	[thread overview]
Message-ID: <4ED38512.3030202@aribaud.net> (raw)
In-Reply-To: <20111127193612.65CA21FFB3AD@gemini.denx.de>

Hi all,

Le 27/11/2011 20:36, Wolfgang Denk a ?crit :

>> Don't you think that adding stub implementation for cache functions on
>> arm926ejs and fixing the driver is better?
>
> Yes, that would be the 4th approach, listed as "much better" :-)

Better yet, have an ARM-wide, not only ARM926EJ-S, cache framework with 
a hierarchy of cache function implementations, from ARM architectures to 
Cores / SoCs or even boards.

My general idea is that:

- each ISA (ARMv4/5/4/7/etc) should provide generic implementations for 
cache handling functions to all cores, SoCs, boards that use this ISA, 
and that implementation should be used by default;

- each core / SoC should be able to easily provide specific cache 
function variants to all boards based on it, on a function granularity 
(i.e. reuse as much of the ISA cache handling code as possible);

- maybe a board should be able to easily provide specific cache 
functions as well;

- the cache API should hide L1 / L2 intricacies at the client level, 
i.e. a driver that wants to flush to memory should just call 
'cache_flush_range(address, size)' without wondering which caches the 
board provides;

- global cache enable/disable/flush (as opposed to cache range) should 
be used only in very few cases (init and exit, meaning U-Boot startup 
and jum-to-OS cases).

The system of 'overloading' between lib, ISA and SoC / Core could be 
achieved through weak symbols maybe, or a set of CONFIG variables, e.g. 
CONFIG_ARM_CACHE_FLUSH would be set to the name of the function to use 
for cache flushing, etc.

However, I have very little time ATM even to try and keep up with 
patches and pull reqs, so I simply cannot submit any code for ARM cache 
handling. Thus anyone wishing to submit code along the lines above, or 
provide an RFC if they feel there is a better approach, is more than 
welcome, and I *promise* I'll give such submissions first priority -- at 
which point I suggest making sure I am in the "To:" list of the patch 
submission mails.

> Best regards,
>
> Wolfgang Denk

Amicalement,
-- 
Albert.

  reply	other threads:[~2011-11-28 12:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 21:56 [U-Boot] [RFC/PATCH] davinci: disable dcache on boards with EMAC Ilya Yanok
2011-11-11 22:10 ` Andy Fleming
2011-11-11 23:53   ` Tom Rini
2011-11-14 14:07     ` Ben Gardiner
2011-11-15  0:09       ` [U-Boot] [PATCH V2] " Ilya Yanok
2011-11-27 15:09         ` Wolfgang Denk
2011-11-27 15:09 ` [U-Boot] [RFC/PATCH] " Wolfgang Denk
2011-11-27 16:41   ` Tom Rini
2011-11-27 18:09     ` Wolfgang Denk
2011-11-27 18:18       ` Tom Rini
2011-11-27 18:43         ` Wolfgang Denk
2011-11-27 18:51           ` Tom Rini
2011-11-27 19:16             ` Wolfgang Denk
2011-11-27 18:37       ` Ilya Yanok
2011-11-27 18:49         ` Wolfgang Denk
2011-11-27 19:22           ` Ilya Yanok
2011-11-27 19:36             ` Wolfgang Denk
2011-11-28 12:56               ` Albert ARIBAUD [this message]
2011-11-28 16:45                 ` Ilya Yanok
2011-11-28 12:06     ` Christian Riesch
2011-11-28 14:53       ` Tom Rini
2011-11-28 15:43         ` Christian Riesch
2011-11-28 15:59           ` Wolfgang Denk
2011-11-29  7:56             ` Christian Riesch
2011-11-28 16:02           ` Ilya Yanok
2011-11-28 16:36             ` Wolfgang Denk
2011-11-29  7:58             ` Christian Riesch

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=4ED38512.3030202@aribaud.net \
    --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 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.