high resolution timer

[Gu, John A. (US SSA)]

I have a ADC (Analog-to-Digital Converter, Maxim 197) integrated with a
SBC (Single Board Computer) running the Linux Kernel. The ADC has its
sample rate of 10K per second (100 usec interval). The ADC can only
operate on a single trigger and read fashion. Creating a driver is a
good way to handle it. But I don't see any proper timer or delay logic
available for my situation. By using udelay() will block all the other
processes. 

As mentioned from you guys, getting some RT-patch may be the only way
out.

John

-----Original Message-----
From: fedora-list-bounces at redhat.com
[mailto:fedora-list-bounces at redhat.com] On Behalf Of Mike McCarty
Sent: Thursday, January 19, 2006 1:02 PM
To: For users of Fedora Core releases
Subject: Re: high resolution timer

Erwin Rol wrote:

[some good information followed by]

> You also might want to critically look at your software/hardware on 
> why you need those timers. Maybe if you explain what you are trying to

> do someone has a better/different solution for you that does work with

> the normal kernel.

I second this advice. It's pretty abnormal to need 100us resolution in
timing, especially in a "sloppy scheduling environment" like that
provided by the standard Linux kernels. Ask yourself whether you really
really need that, or if you don't have a design masquerading as
requirements. What does this timing requirement stem from? Surely there
is some reason for its existence. That is probably a real requirement.
See if you can accomplish the same result without needing stringent
timing.

Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!

--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list