On Tue, Mar 03, 2015 at 01:29:33PM +0100, Daniel Lezcano wrote:
> diff --git a/arch/arm64/include/asm/cpuidle.h
> b/arch/arm64/include/asm/cpuidle.h
> index 0710654..1bee287 100644
> --- a/arch/arm64/include/asm/cpuidle.h
> +++ b/arch/arm64/include/asm/cpuidle.h
> @@ -15,5 +15,8 @@ static inline
On Tue, Mar 03, 2015 at 01:29:33PM +0100, Daniel Lezcano wrote:
diff --git a/arch/arm64/include/asm/cpuidle.h
b/arch/arm64/include/asm/cpuidle.h
index 0710654..1bee287 100644
--- a/arch/arm64/include/asm/cpuidle.h
+++ b/arch/arm64/include/asm/cpuidle.h
@@ -15,5 +15,8 @@ static inline int
On 03/18/2015 02:14 AM, Stephen Boyd wrote:
On 03/17/15 04:29, Lorenzo Pieralisi wrote:
On Mon, Mar 16, 2015 at 10:08:19PM +, Stephen Boyd wrote:
On 03/03/15 04:29, Daniel Lezcano wrote:
The code is optimized to use the __init section intensively in order to reduce
the memory footprint
On 03/18/2015 02:14 AM, Stephen Boyd wrote:
On 03/17/15 04:29, Lorenzo Pieralisi wrote:
On Mon, Mar 16, 2015 at 10:08:19PM +, Stephen Boyd wrote:
On 03/03/15 04:29, Daniel Lezcano wrote:
The code is optimized to use the __init section intensively in order to reduce
the memory footprint
On 03/17/15 04:29, Lorenzo Pieralisi wrote:
> On Mon, Mar 16, 2015 at 10:08:19PM +, Stephen Boyd wrote:
>> On 03/03/15 04:29, Daniel Lezcano wrote:
>>> The code is optimized to use the __init section intensively in order to
>>> reduce
>>> the memory footprint after the driver is initialized
On Mon, Mar 16, 2015 at 10:08:19PM +, Stephen Boyd wrote:
> On 03/03/15 04:29, Daniel Lezcano wrote:
> >
> > 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.
On 03/16/2015 07:16 PM, Lorenzo Pieralisi wrote:
On Tue, Mar 03, 2015 at 12:29:33PM +, Daniel Lezcano wrote:
The current state of the different cpuidle drivers is the different PM
Nit: "The current state of cpuidle drivers is such that different ..."
Ok.
operations are passed via the
On 03/16/2015 07:16 PM, Lorenzo Pieralisi wrote:
On Tue, Mar 03, 2015 at 12:29:33PM +, Daniel Lezcano wrote:
The current state of the different cpuidle drivers is the different PM
Nit: The current state of cpuidle drivers is such that different ...
Ok.
operations are passed via the
On 03/17/15 04:29, Lorenzo Pieralisi wrote:
On Mon, Mar 16, 2015 at 10:08:19PM +, Stephen Boyd wrote:
On 03/03/15 04:29, Daniel Lezcano wrote:
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
On Mon, Mar 16, 2015 at 10:08:19PM +, Stephen Boyd wrote:
On 03/03/15 04:29, Daniel Lezcano wrote:
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.
In
On 03/03/15 04:29, Daniel Lezcano wrote:
>
> 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.
>
> In order to prevent multiple declarations and the specific cpuidle ops
On Tue, Mar 03, 2015 at 12:29:33PM +, Daniel Lezcano wrote:
> The current state of the different cpuidle drivers is the different PM
Nit: "The current state of cpuidle drivers is such that different ..."
> operations are passed via the platform_data using the platform driver
> paradigm.
>
>
On Tue, Mar 03, 2015 at 12:29:33PM +, Daniel Lezcano wrote:
The current state of the different cpuidle drivers is the different PM
Nit: The current state of cpuidle drivers is such that different ...
operations are passed via the platform_data using the platform driver
paradigm.
This
On 03/03/15 04:29, Daniel Lezcano wrote:
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.
In order to prevent multiple declarations and the specific cpuidle ops to be
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 complains about
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 complains about
16 matches
Mail list logo
