On Fri, 15 Nov 2013, Rob Herring wrote: > On 11/15/2013 08:48 AM, Stefano Stabellini wrote: > > On Thu, 19 Sep 2013, Rob Herring wrote: > >> From: Rob Herring <rob.herring@xxxxxxxxxxx> > >> > >> The PSCI spec from ARM has been updated to 0.2 version. Update the > >> binding document to reflect the spec changes. For the binding, the > >> major changes are the addition of psci_version, affinity_info, > >> migrate_info_type, migrate_info_up_cpu, system_reset and system_off > >> functions. The recommended function ID numbering has also changed. > >> > >> This update also defines 32 and 64 bit calling conventions. The calling > >> convention is defined on a per function ID basis. > >> > >> Signed-off-by: Rob Herring <rob.herring@xxxxxxxxxxx> > >> Cc: Dave Martin <Dave.Martin@xxxxxxx> > >> Cc: Mark Rutland <mark.rutland@xxxxxxx> > >> Cc: Ian Campbell <Ian.Campbell@xxxxxxxxxx> > >> Cc: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> > >> Cc: Marc Zyngier <Marc.Zyngier@xxxxxxx> > >> Cc: Christoffer Dall <christoffer.dall@xxxxxxxxxx>, > >> Cc: Charles Garcia-Tobin <Charles.Garcia-Tobin@xxxxxxx> > >> Cc: Matt Sealey <neko@xxxxxxxxxxxxx> > >> Cc: devicetree@xxxxxxxxxxxxxxx > > > > Rob, > > I noticed that this patch hasn't gone upstream yet. Is the interface > > still under discussion? > > I am thinking of implementing the Xen side of it. > > Since we can't seem to agree on how to extend the binding, I plan to go > back to something more simple which is simply adding 2 optional > properties to the existing "arm,psci" binding. This would be enough to > meet the needs of KVM, Xen, and highbank. A future binding can deal with > the whole 32 and 64-bit calling convention issue. OK. TBH Xen doesn't need anything more than what is already specified in "arm,psci". However it would have been nice to fully implement the latest PSCI spec. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
