[PATCH 5/6] drivers: firmware: psci: add extended stateid power_state support
Lorenzo Pieralisi
lorenzo.pieralisi at arm.com
Mon Jun 8 04:03:52 PDT 2015
On Fri, Jun 05, 2015 at 03:16:36PM +0100, Ashwin Chaugule wrote:
> On 29 May 2015 at 08:16, Lorenzo Pieralisi <lorenzo.pieralisi at arm.com> wrote:
[...]
> > diff --git a/include/uapi/linux/psci.h b/include/uapi/linux/psci.h
> > index 187b828d..2598d7c 100644
> > --- a/include/uapi/linux/psci.h
> > +++ b/include/uapi/linux/psci.h
> > @@ -58,6 +58,13 @@
> > #define PSCI_0_2_POWER_STATE_AFFL_MASK \
> > (0x3 << PSCI_0_2_POWER_STATE_AFFL_SHIFT)
> >
> > +/* PSCI extended power state encoding for CPU_SUSPEND function */
> > +#define PSCI_EXT_POWER_STATE_ID_MASK 0xfffffff
> > +#define PSCI_EXT_POWER_STATE_ID_SHIFT 0
> > +#define PSCI_EXT_POWER_STATE_TYPE_SHIFT 30
> > +#define PSCI_EXT_POWER_STATE_TYPE_MASK \
> > + (0x1 << PSCI_EXT_POWER_STATE_TYPE_SHIFT)
> > +
>
> For consistency, dont you need version numbers here, like we have for v0.2?
According to the docs (page 49, 5.12.2 Implementation responsibilities)
the choice is between "Original Format(PSCI0.2)" and "extended stateid"
parameter.
Do we really need to add a version number to the extended stateid defines ?
I could add it, I am not not fussed about this.
> > /* PSCI v0.2 affinity level state returned by AFFINITY_INFO */
> > #define PSCI_0_2_AFFINITY_LEVEL_ON 0
> > #define PSCI_0_2_AFFINITY_LEVEL_OFF 1
> > @@ -78,6 +85,11 @@
> > #define PSCI_VERSION_MINOR(ver) \
> > ((ver) & PSCI_VERSION_MINOR_MASK)
> >
> > +/* PSCI features decoding (>=1.0) */
> > +#define PSCI_FEATURES_CPU_SUSPEND_PF_SHIFT 1
> > +#define PSCI_FEATURES_CPU_SUSPEND_PF_MASK \
> > + (0x1 << PSCI_FEATURES_CPU_SUSPEND_PF_SHIFT)
> > +
>
> Likewise.
I could do, yes.
Thanks,
Lorenzo
More information about the linux-arm-kernel
mailing list