From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH v2 1/2] xen/arm: Add support of PSCI v1.0 for the host Date: Fri, 23 Oct 2015 11:39:11 +0100 Message-ID: <1445596751.2374.113.camel@citrix.com> References: <1444664352-16057-1-git-send-email-julien.grall@citrix.com> <1444664352-16057-2-git-send-email-julien.grall@citrix.com> <1445528531.2374.17.camel@citrix.com> <56291A34.7010107@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZpZkh-0001QM-Oz for xen-devel@lists.xenproject.org; Fri, 23 Oct 2015 10:39:15 +0000 In-Reply-To: <56291A34.7010107@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Julien Grall , xen-devel@lists.xenproject.org Cc: Mark Rutland , Andre Przywara , stefano.stabellini@eu.citrix.com List-Id: xen-devel@lists.xenproject.org On Thu, 2015-10-22 at 18:17 +0100, Julien Grall wrote: > Hi, > > On 22/10/15 16:42, Ian Campbell wrote: > > On Mon, 2015-10-12 at 16:39 +0100, Julien Grall wrote: > > > > Subject: support PSCI v1.0 for the host. > > > > > From Xen point of view, PSCI v0.2 and PSCI v1.0 are very similar. All > > Xen's > > > > > the PSCI calls used within Xen (PSCI_VERSION, CPU_ON, SYSTEM_OFF and > > > SYSTEM_RESET) behaves exactly the same. > > > > behave > > > > > Furthermore, based on the spec (5.3.1 DEN0022C), any 1.y version must > > > be > > > compatible with 1.x when y > x for any functions existing in 1.x. > > > > > > So check the presence of the new compatible string [1] and allow Xen > > > to > > > boot on any platform using PSCI 1.x. > > > > > > [1] > > > http://lists.infradead.org/pipermail/linux-arm-kernel/2015-October/37 > > > 4547.html > > > > > > Signed-off-by: Julien Grall > > > > Acked-by: Ian Campbell > > Shall I resend a new version with those typos fixed? Or do you plan to > do it when you'll commit the patch? Looks like those are the only changes required, so assuming you are are happy with them I'll just do them on commit.