On Fri, Sep 05, 2014 at 06:34:55PM +0100, Lorenzo Pieralisi wrote: > This patch implements a generic CPU idle driver for ARM64 machines. > > It relies on the DT idle states infrastructure to initialize idle > states count and respective parameters. Current code assumes the driver > is managing idle states on all possible CPUs but can be easily > generalized to support heterogenous systems and build cpumasks at > runtime using MIDRs or DT cpu nodes compatible properties. > > The driver relies on the arm64 CPU operations to call the idle > initialization hook used to parse and save suspend back-end specific > idle states information upon probing. > > Idle state index 0 is always initialized as a simple wfi state, ie always > considered present and functional on all ARM64 platforms. > > Idle state indices higher than 0 trigger idle state entry by calling > the cpu_suspend function, that triggers the suspend operation through > the CPU operations suspend back-end hook. cpu_suspend passes the idle > state index as a parameter so that the CPU operations suspend back-end > can retrieve the required idle state data by using the idle state > index to execute a look-up on its internal data structures. > > Reviewed-by: Ashwin Chaugule <ashwin.chaugule@xxxxxxxxxx> > Reviewed-by: Catalin Marinas <catalin.marinas@xxxxxxx> > Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@xxxxxxx> > --- > drivers/cpuidle/Kconfig | 5 ++ > drivers/cpuidle/Kconfig.arm64 | 14 +++++ > drivers/cpuidle/Makefile | 4 ++ > drivers/cpuidle/cpuidle-arm64.c | 133 ++++++++++++++++++++++++++++++++++++++++ > 4 files changed, 156 insertions(+) > create mode 100644 drivers/cpuidle/Kconfig.arm64 > create mode 100644 drivers/cpuidle/cpuidle-arm64.c Daniel, do you have any preference for how this patch should go in? You can either ack it so that I can take it via the arm64 tree or you take it separately (though it doesn't make sense on its own without the arm64 infrastructure in place, we need a bit of synchronisation but it's not something difficult). Thanks. -- Catalin -- 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
