From: Hongbo Zhang
Currently the API to get CPU frequency is vague, it needs to be clarified
whether max or current frequency is returned, and now most use cases want
to get max capacity of CPU in fact, so this patch makes it clear that the
cpu_hz stand for max CPU frequency. (there is no need to
> -Original Message-
> From: ext hongbo.zh...@freescale.com
> [mailto:hongbo.zh...@freescale.com]
> Sent: Tuesday, August 11, 2015 10:34 AM
> To: lng-odp@lists.linaro.org
> Cc: mike.hol...@linaro.org; stuart.has...@arm.com; Savolainen, Petri
> (Nokia - FI/Espoo); petri.savolai...@linaro.o
Hi, Hongbo
On 11.08.15 10:33, hongbo.zh...@freescale.com wrote:
From: Hongbo Zhang
Currently the API to get CPU frequency is vague, it needs to be clarified
whether max or current frequency is returned, and now most use cases want
to get max capacity of CPU in fact, so this patch makes it clea
On 3 September 2015 at 21:47, Savolainen, Petri (Nokia - FI/Espoo)
wrote:
>
>
>> -Original Message-
>> From: ext hongbo.zh...@freescale.com
>> [mailto:hongbo.zh...@freescale.com]
>> Sent: Tuesday, August 11, 2015 10:34 AM
>> To: lng-odp@lists.linaro.org
>> Cc: mike.hol...@linaro.org; stuar
On 3 September 2015 at 22:47, Ivan Khoronzhuk
wrote:
> Hi, Hongbo
>
> On 11.08.15 10:33, hongbo.zh...@freescale.com wrote:
>>
>> From: Hongbo Zhang
>>
>> Currently the API to get CPU frequency is vague, it needs to be clarified
>> whether max or current frequency is returned, and now most use cas
On 07.09.15 14:08, Hongbo Zhang wrote:
On 3 September 2015 at 22:47, Ivan Khoronzhuk
wrote:
Hi, Hongbo
On 11.08.15 10:33, hongbo.zh...@freescale.com wrote:
From: Hongbo Zhang
Currently the API to get CPU frequency is vague, it needs to be clarified
whether max or current frequency is ret
