From: Martin Drab <drab@kepler.fjfi.cvut.cz>
To: Harish K Harshan <harish@arl.amrita.edu>
Cc: James Courtier-Dutton <James@superbug.co.uk>,
linux-kernel@vger.kernel.org
Subject: Re: DMA Transfer problem
Date: Mon, 30 Jan 2006 17:37:32 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.60.0601301726190.9429@kepler.fjfi.cvut.cz> (raw)
In-Reply-To: <43D62989.3070108@arl.amrita.edu>
On Tue, 24 Jan 2006, Harish K Harshan wrote:
> Thank You, James,
>
> But the problem with sound card drivers are that they dont have a
> configurable clock on them, do they??? and as far as i know, this ADC card
> involves a lot of register writings for the counter ICs that help configuring
> the clock speed for the DMA transfer.... First we set the control properties,
> which involves the IRQ, start channel, stop channel, etc (the card is an
> 8-channel ADC), (the jumper settings configure the DMA channels that should be
> used, 1 or 3). Now we initialize the DMA controller, so that it throws an
> interrupt once the transfer of DMA_COUNT samples of data. The interrupt
> service routine for this interrupt can handle the data transfer to the user
> program. Roughly thats how the driver works... Now, the problem is that, when
> running on the Chino-Laxsons board PCs, the DMA transfers take varying time to
> complete (say, if one transfer takes one second, the next might take one and a
I'm not really sure what do you mean by that, but there may be lots of
reasons for this. Bad bus latencies, other devices blocking the bus, bad
chipset, bad PCI/DMA controller on the device (this happend to me with
an AMCC S5933 MatchMaker PCI chip, since it has about 16 HW construction
bugs within it which makes it nearly impossible to reliably use it with
any reaonably new chipset - with very old chipsets the bugs didn't
demonstrate themselfs that much), etc. And you may also consider a hard
real-time system if it's really time critical and intensive.
Martin
next prev parent reply other threads:[~2006-01-30 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 5:00 DMA Transfer problem Harish K Harshan
2006-01-24 12:59 ` James Courtier-Dutton
2006-01-24 13:20 ` Harish K Harshan
2006-01-24 13:22 ` James Courtier-Dutton
2006-01-30 16:37 ` Martin Drab [this message]
2006-01-30 17:06 ` linux-os (Dick Johnson)
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=Pine.LNX.4.60.0601301726190.9429@kepler.fjfi.cvut.cz \
--to=drab@kepler.fjfi.cvut.cz \
--cc=James@superbug.co.uk \
--cc=harish@arl.amrita.edu \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).