From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V1 1/1] MX5: Keep L2 cache enabled before jump to kernel
Date: Sat, 16 Apr 2011 11:55:56 +0200 [thread overview]
Message-ID: <4DA967AC.4010408@aribaud.net> (raw)
In-Reply-To: <BANLkTikn2ZP9fEs4AP8ng6LWAe1n+GrJow@mail.gmail.com>
Le 15/04/2011 17:55, Jason Liu a ?crit :
> Hi, Stefano,
>
> 2011/4/15 Stefano Babic<sbabic@denx.de>:
>> On 04/13/2011 03:25 PM, Jason Liu wrote:
>>
>> Hi Jason,
>>
>>> Currently, Linux kernel does not do any L2 cache enable
>>> Operation.So,Keep L2 cache enabled(L2EN=1) in the u-boot
>>> before Jump to the Linux Kernel and thus L2 cache can be
>>> effectively used in Linux Kernel.
>>
>> If the cache is not active in the kernel for MX5, this should be fixed
>> in the kernel for this architecture. Normally, cache is activated inside
>> the kernel itself, as I cann see for other architectures and other ARMV7
>> processors (omap)
>
> Here the cache is L2 cache. I have observed that if uboot does not enable it,
> then L2 cache will not get enabled through current ARM linux core code.
Which still does not tell us why Linux should depend on some bootloader
for enabling L2 cache. If Linux does not enable L2 cache, there is a
reason and we should not enable the L2 cache in Linux' back;
conversively, if Linux wants L2 cache enabled, then let Linux do it.
> And for the uboot itself it provide the following code in cpu.c to
> enable L2 cache
> before jump to linux kernel, and this code maybe implemented by omap guys:
> If linux kernel already enabled it, then there is no need for the L2
> related code here?
Turning caches OFF before jumping to Linux is a sane thing to do.
Re-enabling it, on the other hand, bears no reason that I can discern,
because Linux can do it just as well, and it is better if Linux does it
because it will do it exactly where and when it is ready for it, and
because this removes a dependency between Linux and the bootloader,
which is a Good Thing (tm).
Amicalement,
--
Albert.
prev parent reply other threads:[~2011-04-16 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 13:25 [U-Boot] [PATCH V1 1/1] MX5: Keep L2 cache enabled before jump to kernel Jason Liu
2011-04-14 12:09 ` Albert ARIBAUD
2011-04-15 15:09 ` Stefano Babic
2011-04-15 15:55 ` Jason Liu
2011-04-16 9:55 ` Albert ARIBAUD [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=4DA967AC.4010408@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox