From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 03/13 v5] ARM: OMAP3: Add ARM Cortex A8 common directory
Date: Mon, 03 Nov 2008 21:34:13 +0100 [thread overview]
Message-ID: <490F6045.1030503@googlemail.com> (raw)
In-Reply-To: <20081102191749.20718832E40A@gemini.denx.de>
Wolfgang Denk wrote:
> Dear dirk.behme at googlemail.com,
>
> In message <490df313.1358560a.73b4.222e@mx.google.com> you wrote:
>
>>--===============1314021165==
>>
>>From: Dirk Behme <dirk.behme@gmail.com>
>>
>>Add ARM Cortex A8 common directory
>>
>>Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
>
> ...
>
>
>>+static void cp_delay(void)
>>+{
>>+ volatile int i;
>>+
>>+ /* Many OMAP regs need at least 2 nops */
>>+ for (i = 0; i < 100; i++) ;
>
>
> There is not much reason for the compiler not to optimize this code
> away.
>
>
>>+void icache_disable(void)
>>+{
>>+ ulong reg;
>>+
>>+ reg = read_p15_c1();
>>+ cp_delay();
>>+ write_p15_c1(reg & ~C1_IC);
>>+}
>>+
>>+void dcache_disable (void)
>>+{
>>+ ulong reg;
>>+
>>+ reg = read_p15_c1 ();
>>+ cp_delay ();
>>+ write_p15_c1 (reg & ~C1_DC);
>>+}
>
>
> Would it make sense to flush caches before disbling?
Basically yes. But regarding the logic used in existing code, e.g.
cpu/arm1176/cpu.c (cleanup_before_linux())
I'm not sure about this. The logic seems to be to provide single
functions for each cache operation and then call the functions in the
correct order.
>>+ /* someone ought to write a more effiction fiq_save_user_regs */
>
>
> effiction ?
>
>
> Best regards,
>
> Wolfgang Denk
>
prev parent reply other threads:[~2008-11-03 20:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 18:35 [U-Boot] [PATCH 03/13 v5] ARM: OMAP3: Add ARM Cortex A8 common directory dirk.behme at googlemail.com
2008-11-02 18:36 ` [U-Boot] [PATCH 04/13 v5] ARM: OMAP3: Add lowlevel init and sys_info common files dirk.behme at googlemail.com
2008-11-02 18:36 ` [U-Boot] [PATCH 05/13 v5] ARM: OMAP3: Add board, clock and interrupts " dirk.behme at googlemail.com
2008-11-02 18:37 ` [U-Boot] [PATCH 06/13 v5] ARM: OMAP3: Add memory and syslib " dirk.behme at googlemail.com
2008-11-09 14:07 ` Jean-Christophe PLAGNIOL-VILLARD
2008-11-09 19:41 ` Wolfgang Denk
2008-11-02 20:13 ` [U-Boot] [PATCH 05/13 v5] ARM: OMAP3: Add board, clock and interrupts " Wolfgang Denk
2008-11-09 14:04 ` Jean-Christophe PLAGNIOL-VILLARD
2008-11-09 14:10 ` Dirk Behme
2008-11-09 13:51 ` [U-Boot] [PATCH 04/13 v5] ARM: OMAP3: Add lowlevel init and sys_info " Jean-Christophe PLAGNIOL-VILLARD
2008-11-10 19:20 ` Dirk Behme
2008-11-02 19:17 ` [U-Boot] [PATCH 03/13 v5] ARM: OMAP3: Add ARM Cortex A8 common directory Wolfgang Denk
2008-11-03 20:34 ` Dirk Behme [this message]
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=490F6045.1030503@googlemail.com \
--to=dirk.behme@googlemail.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.