Re: [PATCH] cpuidle: Invert CPUIDLE_FLAG_TIME_VALID logic

2014-11-17 Thread Daniel Lezcano
On 11/13/2014 03:56 PM, Lorenzo Pieralisi wrote: On Wed, Nov 12, 2014 at 03:03:50PM +, Daniel Lezcano wrote: The only place where the time is invalid is when the ACPI_CSTATE_FFH entry method is not set. Otherwise for all the drivers, the time can be correctly measured. Instead of

Re: [PATCH] cpuidle: Invert CPUIDLE_FLAG_TIME_VALID logic

2014-11-17 Thread Daniel Lezcano
On 11/13/2014 03:56 PM, Lorenzo Pieralisi wrote: On Wed, Nov 12, 2014 at 03:03:50PM +, Daniel Lezcano wrote: The only place where the time is invalid is when the ACPI_CSTATE_FFH entry method is not set. Otherwise for all the drivers, the time can be correctly measured. Instead of

Re: [PATCH] cpuidle: Invert CPUIDLE_FLAG_TIME_VALID logic

2014-11-14 Thread Rafael J. Wysocki
On Wednesday, November 12, 2014 04:03:50 PM Daniel Lezcano wrote: > The only place where the time is invalid is when the ACPI_CSTATE_FFH entry > method is not set. Otherwise for all the drivers, the time can be correctly > measured. > > Instead of duplicating the CPUIDLE_FLAG_TIME_VALID flag in

Re: [PATCH] cpuidle: Invert CPUIDLE_FLAG_TIME_VALID logic

2014-11-14 Thread Rafael J. Wysocki
On Wednesday, November 12, 2014 04:03:50 PM Daniel Lezcano wrote: The only place where the time is invalid is when the ACPI_CSTATE_FFH entry method is not set. Otherwise for all the drivers, the time can be correctly measured. Instead of duplicating the CPUIDLE_FLAG_TIME_VALID flag in all

Re: [PATCH] cpuidle: Invert CPUIDLE_FLAG_TIME_VALID logic

2014-11-13 Thread Daniel Lezcano
On 11/13/2014 03:56 PM, Lorenzo Pieralisi wrote: On Wed, Nov 12, 2014 at 03:03:50PM +, Daniel Lezcano wrote: The only place where the time is invalid is when the ACPI_CSTATE_FFH entry method is not set. Otherwise for all the drivers, the time can be correctly measured. Instead of

Re: [PATCH] cpuidle: Invert CPUIDLE_FLAG_TIME_VALID logic

2014-11-13 Thread Lorenzo Pieralisi
On Wed, Nov 12, 2014 at 03:03:50PM +, Daniel Lezcano wrote: > The only place where the time is invalid is when the ACPI_CSTATE_FFH entry > method is not set. Otherwise for all the drivers, the time can be correctly > measured. > > Instead of duplicating the CPUIDLE_FLAG_TIME_VALID flag in all

Re: [PATCH] cpuidle: Invert CPUIDLE_FLAG_TIME_VALID logic

2014-11-13 Thread Lorenzo Pieralisi
On Wed, Nov 12, 2014 at 03:03:50PM +, Daniel Lezcano wrote: The only place where the time is invalid is when the ACPI_CSTATE_FFH entry method is not set. Otherwise for all the drivers, the time can be correctly measured. Instead of duplicating the CPUIDLE_FLAG_TIME_VALID flag in all the

Re: [PATCH] cpuidle: Invert CPUIDLE_FLAG_TIME_VALID logic

2014-11-13 Thread Daniel Lezcano
On 11/13/2014 03:56 PM, Lorenzo Pieralisi wrote: On Wed, Nov 12, 2014 at 03:03:50PM +, Daniel Lezcano wrote: The only place where the time is invalid is when the ACPI_CSTATE_FFH entry method is not set. Otherwise for all the drivers, the time can be correctly measured. Instead of

[PATCH] cpuidle: Invert CPUIDLE_FLAG_TIME_VALID logic

2014-11-12 Thread Daniel Lezcano
The only place where the time is invalid is when the ACPI_CSTATE_FFH entry method is not set. Otherwise for all the drivers, the time can be correctly measured. Instead of duplicating the CPUIDLE_FLAG_TIME_VALID flag in all the drivers for all the states, just invert the logic by replacing it by

[PATCH] cpuidle: Invert CPUIDLE_FLAG_TIME_VALID logic

2014-11-12 Thread Daniel Lezcano
The only place where the time is invalid is when the ACPI_CSTATE_FFH entry method is not set. Otherwise for all the drivers, the time can be correctly measured. Instead of duplicating the CPUIDLE_FLAG_TIME_VALID flag in all the drivers for all the states, just invert the logic by replacing it by