Re: [microblaze-uclinux] usleep

[aurash <aurelian.lazarut@xxxxxxxxxxx>]

Hi John,

Actually I was thinking to something else, like timer (programable 
interval ) and each overflow to trigger the  ADC conversion , to ensure 
the right timing for the data aqusition process -then the ADC conversion 
ready will trigger the interrupt routine of the driver which takes the 
data from the ADC the latency here is not very relevant (unless is less 
then the interval between two aqusitions)
with this method you'll have a precise timing between aqusitions (low 
jitter) regardless of system overhead.

Aurash  

John Williams wrote:

> Hi Aurash,
>
> aurash wrote:
>
>> Guys,
>> another approach here could be the hardware (don't forget the whole 
>> thing is configurable platform)  a dedicated peripheral will give 
>> accurate timing and will leave CPU time for other "high level" things.
>
>
> I wondered about that - currently the 2nd channel of the opb_timer is 
> unused, it could be configured as a one-shot timeout - the trick is of 
> course that there would only be one available in the system - the 
> device driver would have to hook into the existing timer interrupt 
> handler, and so on.  An interesting experiment though.
>
> Does anyone know if there's a precedent in other linux's for this sort 
> of thing?
>
> John
>
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@itee.uq.edu.au
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : 
> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>
>


___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/