All of lore.kernel.org
 help / color / mirror / Atom feed
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: do not mark CPU 0 as hotpluggable
Date: Fri, 22 Jul 2011 10:26:07 +0530	[thread overview]
Message-ID: <4E2902E7.6000108@ti.com> (raw)
In-Reply-To: <20110721133033.GN26574@n2100.arm.linux.org.uk>

On 7/21/2011 7:00 PM, Russell King - ARM Linux wrote:
> On Thu, Jul 21, 2011 at 11:03:04AM +0530, Santosh Shilimkar wrote:
>> Just talking on behalf of OMAP, we can't offline CPU0 and limitation
>> would remain in future OMAPs too.
>
> Apart from the broken IRQ migration, and the way CPU0 immediately
> reawakes if it is offlined on OMAP4 (even when IRQs are migrated off
> CPU0) because omap_read_auxcoreboot0() returns 0, is there any other
> reason?
>
> With fixed IRQ migration and forcing CPU0 into an infinite WFI loop,
> I can offline CPU0 and still have a running system.
>
The secure software runs only on CPU0 and that's the biggest limitation.
Other issues like hand-shake as you pointed out, power sequencing etc
can be worked around.

Regards
Santosh

  reply	other threads:[~2011-07-22  4:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20 23:32 [PATCH] ARM: do not mark CPU 0 as hotpluggable Mike Turquette
2011-07-21  3:02 ` Rob Herring
2011-07-21  5:33   ` Santosh Shilimkar
2011-07-21 13:30     ` Russell King - ARM Linux
2011-07-22  4:56       ` Santosh Shilimkar [this message]
2011-07-22 12:45         ` Woodruff, Richard
2011-07-22 12:53           ` Santosh Shilimkar
2011-08-12  1:31             ` Turquette, Mike
2011-07-21  7:45 ` Russell King - ARM Linux
2011-07-21 21:22   ` Woodruff, Richard
2011-07-21 22:18   ` Turquette, Mike

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=4E2902E7.6000108@ti.com \
    --to=santosh.shilimkar@ti.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.