From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
linux-kernel@vger.kernel.org, Wenyou Yang <Wenyou.Yang@atmel.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: at91: sama5d4: Properly configure L2CC
Date: Mon, 9 Mar 2015 19:33:15 +0100 [thread overview]
Message-ID: <20150309183315.GA9188@piout.net> (raw)
In-Reply-To: <20150309172337.GA8656@n2100.arm.linux.org.uk>
On 09/03/2015 at 17:23:37 +0000, Russell King - ARM Linux wrote :
> On Wed, Mar 04, 2015 at 12:29:23PM +0100, Alexandre Belloni wrote:
> > As the bootloader may not properly configure the L2CC, enforce its configuration
> > in the kernel.
> >
> > Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>
> And I assume you never bothered to read the kernel messages which result
> from this? I guess this means I need to ensure that the kernel freezes
> if you do this kind of thing so you can't ignore the complaints from
> the L2C code.
>
> It would be much better if you configured the L2C in the boot loader/
> board firmware rather than trying to have the kernel do it.
>
As I understand, there is no proper way to enable prefetch from the
kernel so if it is not done by the bootloader or firmware (and it is
not), then we are out of luck.
Or is there something done right on berlin and exynos that I'm not doing
here?
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-03-09 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 11:29 [PATCH] ARM: at91: sama5d4: Properly configure L2CC Alexandre Belloni
2015-03-09 17:23 ` Russell King - ARM Linux
2015-03-09 18:33 ` Alexandre Belloni [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=20150309183315.GA9188@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=Wenyou.Yang@atmel.com \
--cc=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
/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