[PATCH v2] OMAP:GPTIMER:1ms tick generation correction

2010-06-21 Thread Tarun Kanti DebBarma
Generation of 1ms granular GPTIMER events using 32KHz or system clocks as inputs does not have whole number count value to load into the register. This inaccurate count value with respect to 1ms period leads to time drift subsequently. OMAP3 and later silicons have dedicated registers for

Re: [PATCH v2] OMAP:GPTIMER:1ms tick generation correction

2010-06-21 Thread Nishanth Menon
NAK - my prev comments are not fixed here either. On 06/21/2010 03:23 PM, Tarun Kanti DebBarma wrote: Generation of 1ms granular GPTIMER events using 32KHz or system clocks as inputs does not have whole number count value to load into the register. This inaccurate count value with respect to

RE: [PATCH v2] OMAP:GPTIMER:1ms tick generation correction

2010-06-21 Thread DebBarma, Tarun Kanti
Nishant, -Original Message- From: Nishanth Menon [mailto:menon.nisha...@gmail.com] Sent: Monday, June 21, 2010 4:15 PM To: DebBarma, Tarun Kanti Cc: linux-omap@vger.kernel.org; R, Sricharan Subject: Re: [PATCH v2] OMAP:GPTIMER:1ms tick generation correction NAK - my prev comments

Re: [PATCH v2] OMAP:GPTIMER:1ms tick generation correction

2010-06-21 Thread Nishanth Menon
] OMAP:GPTIMER:1ms tick generation correction NAK - my prev comments are not fixed here either. On 06/21/2010 03:23 PM, Tarun Kanti DebBarma wrote: Generation of 1ms granular GPTIMER events using 32KHz or system clocks as inputs does not have whole number count value to load into the register

RE: [PATCH v2] OMAP:GPTIMER:1ms tick generation correction

2010-06-21 Thread DebBarma, Tarun Kanti
-Original Message- From: Menon, Nishanth Sent: Monday, June 21, 2010 6:27 PM To: DebBarma, Tarun Kanti Cc: linux-omap@vger.kernel.org; R, Sricharan Subject: Re: [PATCH v2] OMAP:GPTIMER:1ms tick generation correction DebBarma, Tarun Kanti had written, on 06/21/2010 07:51 AM

Re: [PATCH v2] OMAP:GPTIMER:1ms tick generation correction

2010-06-21 Thread Nishanth Menon
DebBarma, Tarun Kanti had written, on 06/21/2010 08:19 AM, the following: [...] --- arch/arm/plat-omap/dmtimer.c | 131 + arch/arm/plat-omap/include/plat/dmtimer.h |1 + 2 files changed, 96 insertions(+), 36 deletions(-) diff --git

RE: [PATCH v2] OMAP:GPTIMER:1ms tick generation correction

2010-06-21 Thread DebBarma, Tarun Kanti
-Original Message- From: Menon, Nishanth Sent: Monday, June 21, 2010 6:56 PM To: DebBarma, Tarun Kanti Cc: linux-omap@vger.kernel.org; R, Sricharan Subject: Re: [PATCH v2] OMAP:GPTIMER:1ms tick generation correction DebBarma, Tarun Kanti had written, on 06/21/2010 08:19 AM

Re: [PATCH v2] OMAP:GPTIMER:1ms tick generation correction

2010-06-21 Thread David Brownell
Doesn't the generic clock code have logic to handle such rounding issues? I'm pretty sure I remember dealing with that issue for 32K timers on AT91 processors. If so that means the setup is done wrong, and is fixable. -- To unsubscribe from this list: send the line unsubscribe linux-omap in

RE: [PATCH v2] OMAP:GPTIMER:1ms tick generation correction

2010-06-21 Thread DebBarma, Tarun Kanti
David, -Original Message- From: David Brownell [mailto:davi...@pacbell.net] Sent: Monday, June 21, 2010 7:51 PM To: DebBarma, Tarun Kanti; Nishanth Menon Cc: linux-omap@vger.kernel.org; R, Sricharan Subject: Re: [PATCH v2] OMAP:GPTIMER:1ms tick generation correction Doesn't

RE: [PATCH v2] OMAP:GPTIMER:1ms tick generation correction

2010-06-21 Thread DebBarma, Tarun Kanti
Kevin, -Original Message- From: Kevin Hilman [mailto:khil...@deeprootsystems.com] Sent: Monday, June 21, 2010 9:24 PM To: DebBarma, Tarun Kanti Cc: linux-omap@vger.kernel.org; R, Sricharan Subject: Re: [PATCH v2] OMAP:GPTIMER:1ms tick generation correction Tarun Kanti DebBarma