linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep.KarkadaNagesha@arm.com (Sudeep KarkadaNagesha)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: vexpress: Enable platform-specific options in defconfig
Date: Thu, 17 Oct 2013 11:55:20 +0100	[thread overview]
Message-ID: <525FC218.7020404@arm.com> (raw)
In-Reply-To: <1382006321.27517.119.camel@hornet>

Hi Pawel,

On 17/10/13 11:38, Pawel Moll wrote:
> On Thu, 2013-10-17 at 10:57 +0100, Sudeep KarkadaNagesha wrote:
>>> +CONFIG_MTD_PHYSMAP=y
>>> +CONFIG_MTD_PHYSMAP_OF=y
>>
>> This could cause issues with CPUIdle on TC2. Since TC2 reset vector is in NOR
>> flash, NOR flash has to be in Read mode when CPU resets and enter reset vector.
>> But what I have seen is that NOR flash is left in Read Identifier Mode after the
>> driver is initialised. So we need to make sure NOR device is in Read mode
>> whenever CPU enters deeper C-states and also may have to register notifiers
>> which seems overkill IMO. Most of the platform have separate(or secure) flash
>> for this reason.
> 
> Oh boy, yes, I remember this now.
> 
>> Is it possible to disable flash on TC2 only in it's DT something like
>>          flash at 0,00000000 {
>>                 status = "disabled";
>>          };	
> 
> But flash is innocent, really... I may just remove CPU_IDLE for the time
> being.
> 

I tried disabling flash device only on TC2 in DT which seem to work for me.

Regards,
Sudeep

-->8
diff --git a/arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts b/arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts
index d2836a2..f649c58 100644
--- a/arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts
+++ b/arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts
@@ -418,3 +418,12 @@
                /include/ "vexpress-v2m-rs1.dtsi"
        };
 };
+/ {
+       smb {
+               motherboard {
+                       flash at 0,00000000 {
+                               status = "disabled";
+                       };
+               };
+       };
+};

  reply	other threads:[~2013-10-17 10:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16 13:36 [PATCH 0/2] Versatile Express config update for 3.13 Pawel Moll
2013-10-16 13:36 ` [PATCH 1/2] ARM: vexpress: Make defconfig work again Pawel Moll
2013-10-16 17:48   ` Christopher Covington
2013-10-17 10:07     ` Pawel Moll
2013-10-16 13:36 ` [PATCH 2/2] ARM: vexpress: Enable platform-specific options in defconfig Pawel Moll
2013-10-16 17:57   ` Christopher Covington
2013-10-17 10:16     ` Pawel Moll
2013-10-17  9:57   ` Sudeep KarkadaNagesha
2013-10-17 10:38     ` Pawel Moll
2013-10-17 10:55       ` Sudeep KarkadaNagesha [this message]
2013-10-28  4:05 ` [PATCH 0/2] Versatile Express config update for 3.13 Olof Johansson

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=525FC218.7020404@arm.com \
    --to=sudeep.karkadanagesha@arm.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 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).