Hi Srini, Ola, Maxime,
On Tue, 14 Apr 2015, Maxime Coquelin wrote:
On 04/14/2015 09:41 AM, Srinivas Kandagatla wrote:
+Adding Pete and Maxime
Thanks Srini, as I wouldn't have seen this otherwise.
snip
+
This patch would not let the SOC like STiH415/416 or zynq with
tied-to-cpu-freq
+Adding Pete and Maxime
Hi Ola,
Thankyou for sending the patch,
I like the Idea, but I have some specific concerns which would break
existing SOCs.
On 13/04/15 18:37, Ola Jeppsson wrote:
Some Cortex A9 CPU:s (e.g. zynq) have the tick tied to the CPU
frequency. On those CPU:s we cannot use
Hi Srini, Ola,
On 04/14/2015 09:41 AM, Srinivas Kandagatla wrote:
+Adding Pete and Maxime
Hi Ola,
Thankyou for sending the patch,
I like the Idea, but I have some specific concerns which would break
existing SOCs.
I like the idea too.
On 13/04/15 18:37, Ola Jeppsson wrote:
Some Cortex
On Tue, 2015-04-14 at 08:41AM +0100, Srinivas Kandagatla wrote:
+Adding Pete and Maxime
Hi Ola,
Thankyou for sending the patch,
I like the Idea, but I have some specific concerns which would break
existing SOCs.
On 13/04/15 18:37, Ola Jeppsson wrote:
Some Cortex A9 CPU:s (e.g. zynq)
On Mon, Apr 13, 2015 at 06:37:29PM +0100, Ola Jeppsson wrote:
Some Cortex A9 CPU:s (e.g. zynq) have the tick tied to the CPU
frequency. On those CPU:s we cannot use the global-timer as a reliable
clocksource with CPU frequency scaling enabled since this is not
currently taken into account by
Some Cortex A9 CPU:s (e.g. zynq) have the tick tied to the CPU
frequency. On those CPU:s we cannot use the global-timer as a reliable
clocksource with CPU frequency scaling enabled since this is not
currently taken into account by the driver.
Add a tied-to-cpu-freq boolean to the global-timer dt
