All of lore.kernel.org
 help / color / mirror / Atom feed
From: shiraz.hashim@st.com (Shiraz HASHIM)
To: linux-arm-kernel@lists.infradead.org
Subject: Query: ARM Cortex A9: Is invalidating L1 data cache mandatory before	usage
Date: Sat, 17 Apr 2010 15:58:21 +0530	[thread overview]
Message-ID: <4BC98D45.9080900@st.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02C4F1657F@dbde02.ent.ti.com>

Hello Santosh,

On 4/17/2010 3:37 PM, Shilimkar, Santosh wrote:
>> -----Original Message-----
>> From: linux-arm-kernel-bounces at lists.infradead.org [mailto:linux-arm-kernel-
>> bounces at lists.infradead.org] On Behalf Of Shiraz HASHIM
>> Sent: Saturday, April 17, 2010 3:26 PM
>> To: linux-arm-kernel at lists.infradead.org
>> Subject: Query: ARM Cortex A9: Is invalidating L1 data cache mandatory before usage
>>
>> Hello,
>>
>> I am trying to port Linux on ARM Cortex A9 based platform and what
>> I see is that if I don't invalidate the data cache before enabling
>> and using it (in arch/arm/boot/compressed/head.S) the system crashes.
> 
> Are you enabling $L1 D in your bootloader before jumping into the kernel??

No. uboot is not enabling data cache. The first time it gets enabled is
in head.S before Linux decompression.

>> I need to do the same for second core before calling secondary_startup.
>>
>> Is it normal? Why then other platforms (cortex A9 based) are not doing
>> this. What am I missing?
>>
>> thanks for your help.

regards
Shiraz

  reply	other threads:[~2010-04-17 10:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17  9:56 Query: ARM Cortex A9: Is invalidating L1 data cache mandatory before usage Shiraz HASHIM
2010-04-17 10:07 ` Shilimkar, Santosh
2010-04-17 10:28   ` Shiraz HASHIM [this message]
2010-04-17 18:14 ` Russell King - ARM Linux
2010-04-18 14:35   ` shiraz hashim
2010-04-18 15:43   ` shiraz hashim
2010-04-18 15:56     ` 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=4BC98D45.9080900@st.com \
    --to=shiraz.hashim@st.com \
    --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 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.