On Thu, Jun 04, 2015 at 03:20:57PM -0700, Stephen Boyd wrote:
On 06/04, Felipe Balbi wrote:
On Thu, Jun 04, 2015 at 03:18:25PM -0500, Felipe Balbi wrote:
On Thu, Jun 04, 2015 at 03:08:50PM -0500, Felipe Balbi wrote:
Hi,
On Thu, Jun 04, 2015 at 11:46:59AM +0200, Mason wrote:
* Felipe Balbi ba...@ti.com [150604 13:41]:
On Thu, Jun 04, 2015 at 10:32:40PM +0200, Mason wrote:
On 04/06/2015 22:08, Felipe Balbi wrote:
On Thu, Jun 04, 2015 at 11:46:59AM +0200, Mason wrote:
Also, check /proc/timer_list for a Broadcast device. If you don't
define one, the TWD
On 04/06/2015 22:37, Felipe Balbi wrote:
On Thu, Jun 04, 2015 at 10:32:40PM +0200, Mason wrote:
On 04/06/2015 22:08, Felipe Balbi wrote:
On Thu, Jun 04, 2015 at 11:46:59AM +0200, Mason wrote:
Also, check /proc/timer_list for a Broadcast device. If you don't
define one, the TWD timers are set
On Thu, Jun 04, 2015 at 10:32:40PM +0200, Mason wrote:
On 04/06/2015 22:08, Felipe Balbi wrote:
On Thu, Jun 04, 2015 at 11:46:59AM +0200, Mason wrote:
Also, check /proc/timer_list for a Broadcast device. If you don't
define one, the TWD timers are set to periodic mode, with hrtimers
On 06/04, Felipe Balbi wrote:
On Thu, Jun 04, 2015 at 03:18:25PM -0500, Felipe Balbi wrote:
On Thu, Jun 04, 2015 at 03:08:50PM -0500, Felipe Balbi wrote:
Hi,
On Thu, Jun 04, 2015 at 11:46:59AM +0200, Mason wrote:
Also, check /proc/timer_list for a Broadcast device. If you don't
On Thu, Jun 04, 2015 at 03:18:25PM -0500, Felipe Balbi wrote:
On Thu, Jun 04, 2015 at 03:08:50PM -0500, Felipe Balbi wrote:
Hi,
On Thu, Jun 04, 2015 at 11:46:59AM +0200, Mason wrote:
Also, check /proc/timer_list for a Broadcast device. If you don't
define one, the TWD timers are set
On 04/06/2015 22:08, Felipe Balbi wrote:
On Thu, Jun 04, 2015 at 11:46:59AM +0200, Mason wrote:
Also, check /proc/timer_list for a Broadcast device. If you don't
define one, the TWD timers are set to periodic mode, with hrtimers
disabled.
Did you manage to turn global timer into Broadcast
On 03/06/2015 23:54, Felipe Balbi wrote:
On Wed, Jun 03, 2015 at 02:41:39PM -0700, Stephen Boyd wrote:
AM43xx, even though it's a single processor A9, it still has TWD and
global
timer. I was doing some profiling with RT v4.0 and latency is 3.5x lower
just
by switching from gptimer to
On Thu, Jun 04, 2015 at 11:46:59AM +0200, Mason wrote:
On 03/06/2015 23:54, Felipe Balbi wrote:
On Wed, Jun 03, 2015 at 02:41:39PM -0700, Stephen Boyd wrote:
AM43xx, even though it's a single processor A9, it still has TWD and
global
timer. I was doing some profiling with RT v4.0 and
Hi,
On Thu, Jun 04, 2015 at 11:46:59AM +0200, Mason wrote:
Also, check /proc/timer_list for a Broadcast device. If you don't
define one, the TWD timers are set to periodic mode, with hrtimers
disabled.
Did you manage to turn global timer into Broadcast device ?
--
balbi
signature.asc
On Thu, Jun 04, 2015 at 03:08:50PM -0500, Felipe Balbi wrote:
Hi,
On Thu, Jun 04, 2015 at 11:46:59AM +0200, Mason wrote:
Also, check /proc/timer_list for a Broadcast device. If you don't
define one, the TWD timers are set to periodic mode, with hrtimers
disabled.
Did you manage to
On Wednesday 03 June 2015 15:32:45 Felipe Balbi wrote:
Hi Tony and Russell,
AM43xx, even though it's a single processor A9, it still has TWD and global
timer. I was doing some profiling with RT v4.0 and latency is 3.5x lower just
by switching from gptimer to twd/global.
The only problem
Signed-off-by: Felipe Balbi ba...@ti.com
---
Hi Tony and Russell,
AM43xx, even though it's a single processor A9, it still has TWD and global
timer. I was doing some profiling with RT v4.0 and latency is 3.5x lower just
by switching from gptimer to twd/global.
The only problem is that
* Felipe Balbi ba...@ti.com [150603 13:36]:
AM43xx, even though it's a single processor A9, it still has TWD and global
timer. I was doing some profiling with RT v4.0 and latency is 3.5x lower just
by switching from gptimer to twd/global.
The only problem is that currently, is_smp() check
On Wed, Jun 03, 2015 at 10:55:27PM +0200, Arnd Bergmann wrote:
On Wednesday 03 June 2015 15:32:45 Felipe Balbi wrote:
Hi Tony and Russell,
AM43xx, even though it's a single processor A9, it still has TWD and global
timer. I was doing some profiling with RT v4.0 and latency is 3.5x
Hi,
On Wed, Jun 03, 2015 at 02:41:39PM -0700, Stephen Boyd wrote:
AM43xx, even though it's a single processor A9, it still has TWD and
global
timer. I was doing some profiling with RT v4.0 and latency is 3.5x lower
just
by switching from gptimer to twd/global.
The only problem is that
On 06/03/2015 02:28 PM, Felipe Balbi wrote:
On Wed, Jun 03, 2015 at 04:04:55PM -0500, Felipe Balbi wrote:
On Wed, Jun 03, 2015 at 10:55:27PM +0200, Arnd Bergmann wrote:
On Wednesday 03 June 2015 15:32:45 Felipe Balbi wrote:
Hi Tony and Russell,
AM43xx, even though it's a single processor A9,
* Felipe Balbi ba...@ti.com [150603 13:36]:
--- a/arch/arm/mach-omap2/timer.c
+++ b/arch/arm/mach-omap2/timer.c
@@ -655,20 +655,18 @@ static OMAP_SYS_32K_TIMER_INIT(4, 1, timer_32k_ck,
ti,timer-alwon,
static DEFINE_TWD_LOCAL_TIMER(twd_local_timer, OMAP44XX_LOCAL_TWD_BASE, 29);
void __init
On Wed, Jun 03, 2015 at 04:04:55PM -0500, Felipe Balbi wrote:
On Wed, Jun 03, 2015 at 10:55:27PM +0200, Arnd Bergmann wrote:
On Wednesday 03 June 2015 15:32:45 Felipe Balbi wrote:
Hi Tony and Russell,
AM43xx, even though it's a single processor A9, it still has TWD and
global
Hi,
On Wed, Jun 03, 2015 at 03:26:20PM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [150603 13:36]:
--- a/arch/arm/mach-omap2/timer.c
+++ b/arch/arm/mach-omap2/timer.c
@@ -655,20 +655,18 @@ static OMAP_SYS_32K_TIMER_INIT(4, 1, timer_32k_ck,
ti,timer-alwon,
static
20 matches
Mail list logo
