[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150325213430.GA30227@codeaurora.org>
Date: Wed, 25 Mar 2015 14:34:30 -0700
From: Stephen Boyd <sboyd@...eaurora.org>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: rjw@...ysocki.net, lorenzo.pieralisi@....com,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
Catalin.Marinas@....com, robherring2@...il.com, arnd@...db.de,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
lina.iyer@...aro.org
Subject: Re: [PATCH V3 2/8] ARM: cpuidle: Add a cpuidle ops structure to be
used for DT
On 03/20, Daniel Lezcano wrote:
> The current state of the different cpuidle drivers is the different PM
> operations are passed via the platform_data using the platform driver
> paradigm.
>
> This approach allowed to split the low level PM code from the arch specific
> and the generic cpuidle code.
>
> Unfortunately there are complaints about this approach as, in the context of the
> single kernel image, we have multiple drivers loaded in memory for nothing and
> the platform driver is not adequate for cpuidle.
>
> This patch provides a common interface via cpuidle ops for all new cpuidle
> driver and a definition for the device tree.
>
> It will allow with the next patches to a have a common definition with ARM64
> and share the same cpuidle driver.
>
> The code is optimized to use the __init section intensively in order to reduce
> the memory footprint after the driver is initialized and unify the function
> names with ARM64.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@...aro.org>
> Acked-by: Kevin Hilman <khilman@...aro.org>
> Acked-by: Rob Herring <robherring2@...il.com>
Thanks for moving to OF tables. We can merge smp ops and cpuidle
ops later on.
Acked-by: Stephen Boyd <sboyd@...eaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists