From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx6: Set shared override bit in PL310 AUX_CTRL register
Date: Thu, 12 Mar 2015 09:41:00 -0400 [thread overview]
Message-ID: <20150312134100.GC32541@bill-the-cat> (raw)
In-Reply-To: <1426104732-26695-1-git-send-email-festevam@gmail.com>
On Wed, Mar 11, 2015 at 05:12:12PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Having bit 22 cleared in the PL310 Auxiliary Control register (shared
> attribute override enable) has the side effect of transforming Normal
> Shared Non-cacheable reads into Cacheable no-allocate reads.
>
> Coherent DMA buffers in Linux always have a Cacheable alias via the
> kernel linear mapping and the processor can speculatively load cache
> lines into the PL310 controller. With bit 22 cleared, Non-cacheable
> reads would unexpectedly hit such cache lines leading to buffer
> corruption.
>
> This was inspired by a patch from Catalin Marinas [1] and also from recent
> discussions in the linux-arm-kernel list [2] where Russell King and Rob Herring
> suggested that bootloaders should initialize the cache.
>
> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2010-November/031810.html
> [2] https://lkml.org/lkml/2015/2/20/199
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> arch/arm/cpu/armv7/mx6/soc.c | 8 ++++++++
> arch/arm/include/asm/pl310.h | 2 ++
> 2 files changed, 10 insertions(+)
>
> diff --git a/arch/arm/cpu/armv7/mx6/soc.c b/arch/arm/cpu/armv7/mx6/soc.c
> index ef02972..5aab305 100644
> --- a/arch/arm/cpu/armv7/mx6/soc.c
> +++ b/arch/arm/cpu/armv7/mx6/soc.c
> @@ -506,6 +506,14 @@ void v7_outer_cache_enable(void)
> struct pl310_regs *const pl310 = (struct pl310_regs *)L2_PL310_BASE;
> unsigned int val;
>
> +
> + /*
> + * Set bit 22 in the auxiliary control register. If this bit
> + * is cleared, PL310 treats Normal Shared Non-cacheable
> + * accesses as Cacheable no-allocate.
> + */
> + setbits_le32(&pl310->pl310_aux_ctrl, L310_SHARED_ATT_OVERRIDE_ENABLE);
> +
> #if defined CONFIG_MX6SL
> struct iomuxc *iomux = (struct iomuxc *)IOMUXC_BASE_ADDR;
> val = readl(&iomux->gpr[11]);
We should put this somewhere a bit more common that other A9 cores can
also call into like OMAP4, SoCFPGA and maybe zynq later (based on a
quick git grep pl310).
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150312/eace60c5/attachment.sig>
next prev parent reply other threads:[~2015-03-12 13:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 20:12 [U-Boot] [PATCH] mx6: Set shared override bit in PL310 AUX_CTRL register Fabio Estevam
2015-03-12 1:04 ` Russell King - ARM Linux
2015-03-12 2:27 ` Fabio Estevam
2015-03-12 9:31 ` Catalin Marinas
2015-03-12 9:32 ` Catalin Marinas
2015-03-12 13:41 ` Tom Rini [this message]
2015-03-12 13:57 ` Fabio Estevam
2015-03-12 14:25 ` Fabio Estevam
2015-03-12 14:43 ` Nishanth Menon
2015-03-12 15:15 ` Fabio Estevam
2015-03-12 15:34 ` Nishanth Menon
2015-04-10 0:35 ` Fabio Estevam
2015-04-10 5:45 ` Nishanth Menon
2015-03-12 14:17 ` Nishanth Menon
2015-05-15 13:35 ` Stefano Babic
2015-05-15 13:37 ` Fabio Estevam
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=20150312134100.GC32541@bill-the-cat \
--to=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox