public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: tony@atomide.com
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: OMAP-Linux <linux-omap-open-source@linux.omap.com>
Subject: Re: [RFC] [PATCH] ARM: OMAP1: Add clocksource driver for OMAP1
Date: Thu, 30 Nov 2006 14:37:40 -0800	[thread overview]
Message-ID: <20061130223739.GA9605@atomide.com> (raw)
In-Reply-To: <EA12F909C0431D458B9D18A176BEE4A508CE053E@dlee02.ent.ti.com>

* Woodruff, Richard <r-woodruff2@ti.com> [061130 14:24]:
> > Thanks for the info, I guess I was looking for the continuously
> running
> > 32KHz timer in addition to that, as then we could use the same dyntick
> > code on 1510 also. Do you know if there is continuously running 32KHz
> > timer on 1510?
> 
> You are looking for 32K Sync timer? I don't think 1510 had one.  1510
> did have an RTC which 32K goes to and can wake you.  Other OMAPs dropped
> it. I seem to recall it may have used to much current and the
> recommendation was to use an external one.  Granularity isn't so great.

Yeah, sync timer was what I was looking. If it does not exist on 1510,
then the dyntick code should use the 32KHz timer as the freely running
timer, and one of the mpu timers for the interrupts.

Regards,

Tony

  reply	other threads:[~2006-11-30 22:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 15:32 [RFC] [PATCH] ARM: OMAP1: Add clocksource driver for OMAP1 Dirk Behme
     [not found] ` <4550CA9E.6090500@mvista.com>
2006-11-08 16:44   ` Dirk Behme
2006-11-10  0:29     ` Tony Lindgren
2006-11-10  0:48       ` Kevin Hilman
2006-11-10  0:53         ` Tony Lindgren
2006-11-30 19:57           ` Woodruff, Richard
2006-11-30 21:30             ` David Brownell
2006-11-30 21:49               ` Woodruff, Richard
2006-11-30 22:32                 ` David Brownell
2006-11-30 22:57                   ` Woodruff, Richard
2006-11-30 22:12               ` tony
2006-11-30 21:59             ` tony
2006-11-30 22:24               ` Woodruff, Richard
2006-11-30 22:37                 ` tony [this message]
2006-11-30 17:55   ` Dirk Behme
2006-11-30 17:50     ` Daniel Walker
2006-12-01 16:12       ` Dirk Behme
2006-12-02  3:21         ` Daniel Walker
2006-12-02  6:11           ` Dirk Behme
2006-12-02  6:54             ` Daniel Walker
2006-12-02  7:06               ` Dirk Behme
2006-12-02  7:18                 ` Daniel Walker
2006-12-04 23:34                 ` Kevin Hilman
2006-11-30 19:14     ` David Brownell
2006-11-30 20:33       ` Dirk Behme
2006-11-30 21:22         ` [RFC] [PATCH] ARM: Add clocksource driver for OMAP1 and OMAP2 David Brownell
2006-12-01 18:21           ` Dirk Behme
2006-12-01 19:03             ` David Brownell
2006-12-01 22:13               ` Tony Lindgren
2006-12-03  2:58                 ` David Brownell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061130223739.GA9605@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=r-woodruff2@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox