All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] change cpu.c under cpu/arm_cortexa8 dir to	common code.
Date: Wed, 27 May 2009 22:52:56 +0200	[thread overview]
Message-ID: <20090527205256.GC16219@game.jcrosoft.org> (raw)
In-Reply-To: <4A1D8A5B.5000205@googlemail.com>

> The only thing I'd like to discuss is how to name the functions. Naming 
> the functions board_*() doesn't seem to fit. Cache functionality isn't 
> really board related. Regarding L2Cache, this is CPU/SoC related. So 
> maybe omap3_l2cache_*()?
actually I'd like to have a better cache management API and you point the
board_ does not fit here as the code is soc or arch specific
>
> Regarding cache_flush()/board_cache_flush() below maybe Jean-Christophe 
> can help if we have already something generic for this somewhere? If not, 
> we should use something like omap3_cache_flush().
as we will support only one arch simultany I'll prefer to not specify it's
name at all.

you will ask why? The reason is that I do want have a common cache management
and a common cleanup before linux

so I'll propose l2_cache_flush as done for the Marvell orion

for non-l2 cache I prefer to manage it via armvXX as they will be common

Best Regards,
J.

  reply	other threads:[~2009-05-27 20:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 11:16 [U-Boot] [PATCH] change cpu.c under cpu/arm_cortexa8 dir to common code Kim, Heung Jun
2009-05-27 11:22 ` Kim, Heung Jun
2009-05-27 18:45 ` Dirk Behme
2009-05-27 20:52   ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-05-28  4:23     ` Kim, Heung Jun

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=20090527205256.GC16219@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.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 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.