From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: at91: Fix: Change internal SRAM memory type to "MT_MEMORY_SO"
Date: Fri, 24 May 2013 17:40:56 +0100 [thread overview]
Message-ID: <20130524164055.GA18614@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130524140322.GD24476@game.jcrosoft.org>
On Fri, May 24, 2013 at 04:03:22PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 12:20 Fri 24 May , Russell King - ARM Linux wrote:
> > On Fri, May 24, 2013 at 07:11:04AM +0000, Yang, Wenyou wrote:
> > > The story is: for sama5d3x with Cortex-A5 core, if not so, when copying
> > > code snippet to the internal SRAM, then jump to run this code, but fail
> > > to run.
> >
> > And that is where your mistake is - you forgot that you're working with
> > a CPU with harvard caches which will require some cache maintanence
> > between copying the code and executing it.
> >
> > You want to look at flush_icache_range() rather than making this memory
> > strongly ordered.
>
> I understand your point but today we map a SRAM as MT_DEVICE
If you map SRAM as MT_DEVICE then you won't be able to execute code from
it. It needs to be a normal memory mapping.
next prev parent reply other threads:[~2013-05-24 16:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 1:05 [PATCH] Change internal SRAM memory type to "MT_MEMORY_SO" Wenyou Yang
2013-05-20 1:06 ` [PATCH] ARM: at91: Fix: " Wenyou Yang
2013-05-21 9:06 ` Nicolas Ferre
2013-05-22 0:14 ` Russell King - ARM Linux
2013-05-24 7:11 ` Yang, Wenyou
2013-05-24 11:20 ` Russell King - ARM Linux
2013-05-24 14:03 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-24 16:40 ` Russell King - ARM Linux [this message]
2013-05-24 16:52 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-24 16:59 ` Russell King - ARM Linux
2013-05-24 17:11 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-21 9:06 ` [PATCH] " Nicolas Ferre
2013-06-08 2:17 ` [PATCH] Change the internal SRAM memory type MT_MEMORY_NONCACHED Wenyou Yang
2013-06-13 13:19 ` Nicolas Ferre
2013-06-13 13:43 ` Russell King - ARM Linux
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=20130524164055.GA18614@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).