From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] keystone: psci: adds cpu_die implementation
Date: Fri, 26 Jun 2015 17:59:29 +0100 [thread overview]
Message-ID: <20150626165929.GB31602@leverpostej> (raw)
In-Reply-To: <558D8492.2090503@ti.com>
> OK. Now I'm confused :) We may have several different configurations here:
>
> 1) CONFIG_HOTPLUG_CPU and CONFIG_ARM_PSCI are not set.
> In this case keystone arch needs to have
> keystone_smp_boot_secondary();
>
> 2) CONFIG_HOTPLUG_CPU=y and CONFIG_ARM_PSCI is not set.
> keystone_smp_boot_secondary() is required and non PSCI
> implementation of keystone_cpu_die() is also required.
>
> 3) CONFIG_HOTPLUG_CPU is not set and CONFIG_ARM_PSCI=y
> 4) CONFIG_HOTPLUG_CPU=y and CONFIG_ARM_PSCI=y
>
> How do I boot secondary CPUs in cases of 3 and 4?
> Do I need to implement PSCI version of the
> keystone_smp_boot_secondary() of adding PSCI commands to DTB is
> enough?
The DTB additions alone _should_ be sufficient.
> Do I need to implement keystone_cpu_die() if PSCI commands are
> added to DTB?
You _should not_ need to add any platform code to use PSCI.
However, if you have existing platform code which pokes the hardware
logically owned by your FW PSCI implementation, you need to ensure that
this code doesn't poke that hardware when PSCI is in use.
Thanks,
Mark.
next prev parent reply other threads:[~2015-06-26 16:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 14:02 [PATCH] keystone: psci: adds cpu_die implementation Vitaly Andrianov
2015-06-25 14:45 ` Mark Rutland
2015-06-25 14:59 ` santosh shilimkar
2015-06-25 16:01 ` Vitaly Andrianov
2015-06-25 16:13 ` Mark Rutland
2015-06-25 16:55 ` Vitaly Andrianov
2015-06-25 16:57 ` Mark Rutland
2015-06-25 17:20 ` Mark Rutland
2015-06-25 18:42 ` santosh shilimkar
2015-06-26 16:57 ` Vitaly Andrianov
2015-06-26 16:59 ` Mark Rutland [this message]
2015-06-26 17:47 ` Grygorii Strashko
2015-06-26 18:06 ` Vitaly Andrianov
2015-06-26 18:41 ` santosh shilimkar
2015-06-25 14:54 ` santosh shilimkar
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=20150626165929.GB31602@leverpostej \
--to=mark.rutland@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