From: Nicolas Pitre <nicolas.pitre@linaro.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Will Deacon <will.deacon@arm.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"arnd@arndb.de" <arnd@arndb.de>,
Marc Zyngier <Marc.Zyngier@arm.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>
Subject: Re: [PATCH v3] [RFC] arm: use PSCI if available
Date: Thu, 28 Mar 2013 10:51:11 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.03.1303281048060.1372@syhkavp.arg> (raw)
In-Reply-To: <alpine.DEB.2.02.1303281225050.4430@kaball.uk.xensource.com>
On Thu, 28 Mar 2013, Stefano Stabellini wrote:
> - the interface to bring up secondary cpus is different and based on
> PSCI, in fact Xen is going to add a PSCI node to the device tree so that
> Dom0 can use it.
>
> Oh wait, Dom0 is not going to use the PSCI interface even if the node is
> present on device tree because it's going to prefer the platform smp_ops
> instead.
Waitaminute... I must have missed this part.
Who said platform specific methods must be used in preference to PSCI?
If DT does provide PSCI description, then PSCI should be used. Doing
otherwise is senseless. If PSCI is not to be used, then it should not
be present in DT.
Nicolas
next prev parent reply other threads:[~2013-03-28 14:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 12:50 Stefano Stabellini
2013-03-27 13:35 ` Marc Zyngier
2013-03-27 16:20 ` Rob Herring
2013-03-27 13:38 ` Will Deacon
2013-03-27 16:23 ` Stefano Stabellini
2013-03-27 16:35 ` Rob Herring
2013-03-27 17:10 ` Stefano Stabellini
2013-03-27 17:24 ` Nicolas Pitre
2013-03-27 18:22 ` Stefano Stabellini
2013-03-27 17:45 ` Rob Herring
2013-03-27 18:03 ` Arnd Bergmann
2013-03-27 18:14 ` Stefano Stabellini
2013-03-27 17:23 ` Will Deacon
2013-03-28 12:48 ` Stefano Stabellini
2013-03-28 14:51 ` Nicolas Pitre [this message]
2013-03-28 15:04 ` Rob Herring
2013-03-28 15:36 ` Stefano Stabellini
2013-03-28 15:39 ` Nicolas Pitre
2013-03-28 16:00 ` Will Deacon
2013-03-28 16:06 ` Nicolas Pitre
2013-03-28 16:20 ` Stefano Stabellini
2013-03-28 18:38 ` Rob Herring
2013-03-29 13:22 ` Stefano Stabellini
2013-03-29 13:54 ` Rob Herring
2013-03-29 14:47 ` Stefano Stabellini
2013-03-27 16:33 ` Rob Herring
2013-03-27 17:05 ` Will Deacon
2013-03-27 17:50 ` Arnd Bergmann
2013-03-27 18:12 ` Will Deacon
2013-03-27 19:10 ` Rob Herring
2013-03-27 19:14 ` Arnd Bergmann
2013-03-27 14:55 ` Rob Herring
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=alpine.LFD.2.03.1303281048060.1372@syhkavp.arg \
--to=nicolas.pitre@linaro.org \
--cc=Marc.Zyngier@arm.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=stefano.stabellini@eu.citrix.com \
--cc=will.deacon@arm.com \
--cc=xen-devel@lists.xensource.com \
/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
all inboxes | Powered by JetHome®