From: Julien Grall <julien.grall@linaro.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Christoffer Dall <christoffer.dall@linaro.org>
Cc: Parth Dixit <parth.dixit@linaro.org>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH RFC] xen/arm : emulation of arm's psci v0.2 standard
Date: Fri, 20 Jun 2014 13:02:39 +0100 [thread overview]
Message-ID: <53A422DF.7040007@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1406201247110.6594@kaball.uk.xensource.com>
On 20/06/14 12:48, Stefano Stabellini wrote:
>> And yes, the idea is to have a single device tree node, and then psci
>> v0.1 only kernels can still use psci v0.1, and psci v0.2 can ignore
>> the function IDs and use the ones defined as per the spec.
>
> OK. From the Xen POV we need to expose a psci node compatible with both
> psci-0.2 and psci, because we want 3.15 to be able to boot with multiple
> vcpus on Xen 4.5.
>
AFAIU parth's patch, this is already possible. He doesn't add the
properties such as suspend because we don't support them on Xen for PSCI
v0.1
--
Julien Grall
next prev parent reply other threads:[~2014-06-20 12:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 10:14 PSCI v0.2 Emulation support in xen ( arm ) Parth Dixit
2014-06-19 10:14 ` [PATCH RFC] xen/arm : emulation of arm's psci v0.2 standard Parth Dixit
2014-06-19 12:47 ` Julien Grall
2014-06-19 16:00 ` Stefano Stabellini
2014-06-19 16:39 ` Julien Grall
2014-06-19 17:22 ` Stefano Stabellini
2014-06-19 18:02 ` Julien Grall
2014-06-19 18:20 ` Christoffer Dall
2014-06-20 11:48 ` Stefano Stabellini
2014-06-20 12:02 ` Julien Grall [this message]
2014-06-23 5:28 ` Parth Dixit
2014-06-23 7:55 ` Christoffer Dall
2014-06-23 10:28 ` Stefano Stabellini
2014-06-23 10:40 ` Stefano Stabellini
2014-06-23 12:30 ` Julien Grall
2014-06-23 16:57 ` Stefano Stabellini
2014-06-23 17:19 ` Julien Grall
2014-06-24 8:35 ` Christoffer Dall
2014-06-19 12:05 ` PSCI v0.2 Emulation support in xen ( arm ) Julien Grall
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=53A422DF.7040007@linaro.org \
--to=julien.grall@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=parth.dixit@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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.