On 03/09/2017 11:33 AM, Vlad Zakharov wrote:
>
>> And while we are at it - one of my wish list has been to print the core clk
>> in
>> early boot - i.e. in setup_processor()->arc_cpu_mumbojumbo() call path which
>> is
>> different from the other case u fixed. Any ideas how to do that - clk
>> fr
Hi Vineet,
On Wed, 2017-02-22 at 10:49 -0800, Vineet Gupta wrote:
> On 02/22/2017 02:36 AM, Vlad Zakharov wrote:
> > We were reading clock rate directly from device tree "clock-frequency"
> > property of corresponding clock node in show_cpuinfo function.
> >
> > Such approach is correct only in c
Hi Vineet,
On Wed, 2017-02-22 at 10:34 -0800, Vineet Gupta wrote:
> On 02/22/2017 02:36 AM, Vlad Zakharov wrote:
> >
> > We were reading clock rate directly from device tree "clock-frequency"
> > property of corresponding clock node in show_cpuinfo function.
> >
> > Such approach is correct only
On 02/22/2017 02:36 AM, Vlad Zakharov wrote:
> We were reading clock rate directly from device tree "clock-frequency"
> property of corresponding clock node in show_cpuinfo function.
>
> Such approach is correct only in case cpu is always clocked by
> "fixed-clock". If we use clock driver that all
On 02/22/2017 02:36 AM, Vlad Zakharov wrote:
> We were reading clock rate directly from device tree "clock-frequency"
> property of corresponding clock node in show_cpuinfo function.
>
> Such approach is correct only in case cpu is always clocked by
> "fixed-clock". If we use clock driver that all
We were reading clock rate directly from device tree "clock-frequency"
property of corresponding clock node in show_cpuinfo function.
Such approach is correct only in case cpu is always clocked by
"fixed-clock". If we use clock driver that allows rate to be changed
this won't work as rate may chan
