From: srinivas.kandagatla@st.com (Srinivas KANDAGATLA)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: STi: Add cpu hotplug support
Date: Mon, 23 Sep 2013 09:52:45 +0100 [thread overview]
Message-ID: <5240015D.603@st.com> (raw)
In-Reply-To: <20130923082926.GR12758@n2100.arm.linux.org.uk>
On 23/09/13 09:29, Russell King - ARM Linux wrote:
> On Mon, Sep 23, 2013 at 09:22:10AM +0100, Srinivas KANDAGATLA wrote:
>> From: Srinivas Kandagatla <srinivas.kandagatla@st.com>
>>
>> This patch adds cpu hotplug support to STi series SoCs. This code is
>> cloned from arch/arm/mach-realview/hotplug.c.
>>
>> STiH415 and STiH416 SOCs do not have power control lines wired up to
>> each core, so all we can do is to put the core into WFI for hotplug
>> support.
>
> Note that this means you can't support KEXEC on this platform.
>
>
Yes I understand, we cant support kexec with the existing code in v3.12-rc1.
Kexec support on platforms like this is the other topic I would like to
discuss.
Thanks,
srini
prev parent reply other threads:[~2013-09-23 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 8:22 [PATCH] ARM: STi: Add cpu hotplug support Srinivas KANDAGATLA
2013-09-23 8:29 ` Russell King - ARM Linux
2013-09-23 8:52 ` Srinivas KANDAGATLA [this message]
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=5240015D.603@st.com \
--to=srinivas.kandagatla@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 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).