From: Jun Sun <jsun@mvista.com>
To: Dmitry Antipov <dmitry.antipov@mail.ru>
Cc: linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: IT8172G on-board timers
Date: Wed, 6 Aug 2003 09:59:46 -0700 [thread overview]
Message-ID: <20030806095946.C18963@mvista.com> (raw)
In-Reply-To: <3F2FB360.9040005@mail.ru>; from dmitry.antipov@mail.ru on Tue, Aug 05, 2003 at 05:38:40PM +0400
On Tue, Aug 05, 2003 at 05:38:40PM +0400, Dmitry Antipov wrote:
> Hello all,
>
> I'm working with IT8172-based MIPS board and want to use one of (or may
> be both) on-board timers.
> For my purposes, it's required to generate irq from timer rarely, for
> example, each 1 sec, or each 5 sec
> or so. (The usage of Linux timer interface (init_timer() etc...) is
> forbidden
Using linux timer seems perfect for the need. Why not? For an example
of using timer you can take a look of my real time test suite
http://linux.junsun.net/preemp-test/
> , and I don't want to touch
> system timer to avoid the potential damage for basic timekeeping,
> scheduling, etc.). I have two problems:
> - timer backward counter is 16-bit wide and reaches zero too fast, even
> starting from 0xffff;
> - timer input clock may be one of CPU clock, CPU clock /4, CPU clock/8
> or CPU clock /16, which looks
> very fast too
> So, the minimum interrupt frequency from both timers is 96 ints/HZ (with
> TCR0.PST0 is 0 and
> TCVR0 is 0xffff) and the maximum is around 150000 ints/HZ. Even the
> minimum is too large for me...
>
You can write a driver that "accumlates" the interrupts until a desired
duration is reached before it actually does anything useful.
Jun
prev parent reply other threads:[~2003-08-06 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 13:38 IT8172G on-board timers Dmitry Antipov
2003-08-06 16:59 ` Jun Sun [this message]
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=20030806095946.C18963@mvista.com \
--to=jsun@mvista.com \
--cc=dmitry.antipov@mail.ru \
--cc=linux-mips@linux-mips.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.