On 29-06-17, 22:34, Rafael J. Wysocki wrote:
> Shouldn't drivers do that really?
Well they can, but the we will have some sort of code duplication
then. Or else we can provide a helper for them to find this value
dynamically and that would be fine too. And maybe we can add a
callback for the
On 29-06-17, 22:34, Rafael J. Wysocki wrote:
> Shouldn't drivers do that really?
Well they can, but the we will have some sort of code duplication
then. Or else we can provide a helper for them to find this value
dynamically and that would be fine too. And maybe we can add a
callback for the
On Thu, Jun 29, 2017 at 6:28 AM, Viresh Kumar wrote:
> On 02-06-17, 16:59, Viresh Kumar wrote:
>> The transition_latency_ns represents the maximum time it can take for
>> the hardware to switch from/to any frequency for a CPU.
>>
>> The transition_latency_ns is used
On Thu, Jun 29, 2017 at 6:28 AM, Viresh Kumar wrote:
> On 02-06-17, 16:59, Viresh Kumar wrote:
>> The transition_latency_ns represents the maximum time it can take for
>> the hardware to switch from/to any frequency for a CPU.
>>
>> The transition_latency_ns is used currently for two purposes:
>>
On 02-06-17, 16:59, Viresh Kumar wrote:
> The transition_latency_ns represents the maximum time it can take for
> the hardware to switch from/to any frequency for a CPU.
>
> The transition_latency_ns is used currently for two purposes:
>
> o To check if the hardware latency is over the maximum
On 02-06-17, 16:59, Viresh Kumar wrote:
> The transition_latency_ns represents the maximum time it can take for
> the hardware to switch from/to any frequency for a CPU.
>
> The transition_latency_ns is used currently for two purposes:
>
> o To check if the hardware latency is over the maximum
On 06-06-17, 18:48, Leonard Crestez wrote:
> I remember checking if transition latency is correct for imx6q-cpufreq
> and it does not appear to be. Maybe because i2c latency of regulator
> adjustments is not counted in?
+ software latency + other stuff based on platforms.
And that's why I am
On 06-06-17, 18:48, Leonard Crestez wrote:
> I remember checking if transition latency is correct for imx6q-cpufreq
> and it does not appear to be. Maybe because i2c latency of regulator
> adjustments is not counted in?
+ software latency + other stuff based on platforms.
And that's why I am
On Fri, 2017-06-02 at 16:59 +0530, Viresh Kumar wrote:
> The transition_latency_ns represents the maximum time it can take for
> the hardware to switch from/to any frequency for a CPU.
>
> The transition_latency_ns is used currently for two purposes:
>
> o To check if the hardware latency is
On Fri, 2017-06-02 at 16:59 +0530, Viresh Kumar wrote:
> The transition_latency_ns represents the maximum time it can take for
> the hardware to switch from/to any frequency for a CPU.
>
> The transition_latency_ns is used currently for two purposes:
>
> o To check if the hardware latency is
The transition_latency_ns represents the maximum time it can take for
the hardware to switch from/to any frequency for a CPU.
The transition_latency_ns is used currently for two purposes:
o To check if the hardware latency is over the maximum allowed for a
governor (only for ondemand and
The transition_latency_ns represents the maximum time it can take for
the hardware to switch from/to any frequency for a CPU.
The transition_latency_ns is used currently for two purposes:
o To check if the hardware latency is over the maximum allowed for a
governor (only for ondemand and
12 matches
Mail list logo