mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Masters <jcm@jonmasters.org>
To: Alex Williams <alex.williams@ni.com>, linux-kernel@vger.kernel.org
Cc: Moritz Fischer <moritz.fischer@ettus.com>,
	Sinan Kaya <okaya@codeaurora.org>
Subject: Re: Generic DMA-capable streaming device driver looking for home
Date: Thu, 27 Apr 2017 10:00:04 -0400	[thread overview]
Message-ID: <d925a1cb-26c8-b1cf-bd99-d4cf18e6816e@jonmasters.org> (raw)
In-Reply-To: <1492726231.2029.36.camel@ni.com>

On 04/20/2017 06:10 PM, Alex Williams wrote:
> Hi all,
> 
> We're writing a device driver and having some difficulty matching a
> subsystem to the driver/device properties. Can anyone help with
> direction?
> 
> These are some basic properties:
> 1) Device is used to carry generic data to/from userspace. It's a pair
>    of dumb streams with one sink and one source for each direction (no
>    addressable endpoints for the other side).
> 2) Data goes to/from a DMA engine in an FPGA at high throughput.
> 3) The driver enables userspace to queue multiple DMA-able buffers for
>    asynchronous, pipelined data transfer. We currently use the
>    videobuf2 API to provide the feature. We're not carrying video data
>    in general, though.
> 
> It's a piece of a software-defined radio system, and while it can carry
> data from DACs/ADCs, the device is only a generic transport. It doesn't
> know what data it's carrying, so neither would the driver.
> 
> Some guidance would be greatly appreciated. Thanks!

This might be close enough to hidma that Sinan would have suggestions?

  reply	other threads:[~2017-04-27 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 22:10 Alex Williams
2017-04-27 14:00 ` Jon Masters [this message]
2017-04-27 14:50   ` Sinan Kaya
2017-04-27 16:33     ` Lars-Peter Clausen

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=d925a1cb-26c8-b1cf-bd99-d4cf18e6816e@jonmasters.org \
    --to=jcm@jonmasters.org \
    --cc=alex.williams@ni.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moritz.fischer@ettus.com \
    --cc=okaya@codeaurora.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

all inboxes | Powered by JetHome®