On Thu, Jun 9, 2016 at 5:09 AM, Sudeep Holla wrote:
>
>
> On 08/06/16 20:31, Jon Mason wrote:
>>
>> On Wed, Jun 08, 2016 at 09:34:06AM +0100, Sudeep Holla wrote:
>>>
>>>
>>>
>>> On 07/06/16 22:08, Jon Mason wrote:
Query the CPU core clock in the device tree to determine the core clock
>>
On 08/06/16 20:31, Jon Mason wrote:
On Wed, Jun 08, 2016 at 09:34:06AM +0100, Sudeep Holla wrote:
On 07/06/16 22:08, Jon Mason wrote:
Query the CPU core clock in the device tree to determine the core clock
speed.
How do guarantee that it's the current frequency of the CPU ?
I am basing
On Wed, Jun 08, 2016 at 09:34:06AM +0100, Sudeep Holla wrote:
>
>
> On 07/06/16 22:08, Jon Mason wrote:
> >Query the CPU core clock in the device tree to determine the core clock
> >speed.
>
> How do guarantee that it's the current frequency of the CPU ?
I am basing it on the assumption (perhap
On 07/06/16 22:08, Jon Mason wrote:
Query the CPU core clock in the device tree to determine the core clock
speed.
How do guarantee that it's the current frequency of the CPU ?
It doesn't even represent the mix or max frequency, so it's incorrect.
Some DTs have boot frequency in that entry.
Query the CPU core clock in the device tree to determine the core clock
speed. Output this clock rate in /proc/cpuinfo to match the output
from other architectures. The output is intentionally patterned after
the x86 output, to match existing (and possibly expected) convention.
If any errors are
5 matches
Mail list logo