Re: powerpc/powernv/idle: Round up latency and residency values

2017-11-14 Thread Michael Ellerman
On Wed, 2017-08-23 at 18:58:41 UTC, Vaidyanathan Srinivasan wrote: > On PowerNV platforms, firmware provides exit latency and > target residency for each of the idle states in nano > seconds. Cpuidle framework expects the values in micro > seconds. Round up to nearest micro seconds to avoid error

Re: [PATCH] powerpc/powernv/idle: Round up latency and residency values

2017-08-24 Thread Vaidyanathan Srinivasan
* Michael Ellerman [2017-08-24 20:28:19]: > Vaidyanathan Srinivasan writes: > > > On PowerNV platforms, firmware provides exit latency and > > target residency for each of the idle states in nano > > seconds. Cpuidle framework expects the values in micro > > seconds. Round up to nearest micro

Re: [PATCH] powerpc/powernv/idle: Round up latency and residency values

2017-08-24 Thread Michael Ellerman
Vaidyanathan Srinivasan writes: > On PowerNV platforms, firmware provides exit latency and > target residency for each of the idle states in nano > seconds. Cpuidle framework expects the values in micro > seconds. Round up to nearest micro seconds to avoid errors > in cases where the values are

Re: [PATCH] powerpc/powernv/idle: Round up latency and residency values

2017-08-23 Thread Gautham R Shenoy
Hi Vaidy, On Thu, Aug 24, 2017 at 12:28:41AM +0530, Vaidyanathan Srinivasan wrote: Cc'ing Rafael and linux-pm list. > On PowerNV platforms, firmware provides exit latency and > target residency for each of the idle states in nano > seconds. Cpuidle framework expects the values in micro > seconds

[PATCH] powerpc/powernv/idle: Round up latency and residency values

2017-08-23 Thread Vaidyanathan Srinivasan
On PowerNV platforms, firmware provides exit latency and target residency for each of the idle states in nano seconds. Cpuidle framework expects the values in micro seconds. Round up to nearest micro seconds to avoid errors in cases where the values are defined as fractional micro seconds. Defau