From: Henk Medenblik <yoda@deathstar2.nl>
To: linux-iio <linux-iio@vger.kernel.org>
Subject: multiple dma engines/ ring buffers
Date: Tue, 15 Mar 2022 14:18:55 +0100 [thread overview]
Message-ID: <cfc53292-35cf-28bb-3764-65a681eaedd9@deathstar2.nl> (raw)
Hi,
I am struggling with the concept of using two different DMA engines and
therefore two ring buffer definitions in a single driver.
My purpose is to have two different data paths which I want to select in
my iio device driver. One of them has the purpose to stream plain ADC 16
bit data to my backend while the second selection would be a hardware
FFT core output (complex 32 bit). So which one I stream to the backend
should be selectable.
Because both paths originate from different parts in my HW design I
implemented two different DMA engines and therefore I have two different
dma names. However, how to deal with that in my single driver? Has
anyone done that?
Regards
Henk
next reply other threads:[~2022-03-15 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 13:18 Henk Medenblik [this message]
2022-03-17 6:13 ` multiple dma engines/ ring buffers Alexandru Ardelean
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=cfc53292-35cf-28bb-3764-65a681eaedd9@deathstar2.nl \
--to=yoda@deathstar2.nl \
--cc=linux-iio@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