From: David Herrmann <dh.herrmann@gmail.com>
To: Florian Echtler <floe@butterbrot.org>
Cc: linux-input <linux-input@vger.kernel.org>,
Oliver Neukum <oneukum@suse.de>,
Alan Stern <stern@rowland.harvard.edu>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [sur40] videobuf2 and/or DMA?
Date: Thu, 11 Dec 2014 09:58:59 +0100 [thread overview]
Message-ID: <CANq1E4QXAyGccPExgvZJO74aBwEOHHM8_Ysv8nx8dLmcmVBnCA@mail.gmail.com> (raw)
In-Reply-To: <54855856.3070207@butterbrot.org>
Hi
On Mon, Dec 8, 2014 at 8:50 AM, Florian Echtler <floe@butterbrot.org> wrote:
> Hello everyone,
>
> I'm preparing to finally add support for the raw sensor video stream to
> my driver for the SUR40 touchscreen. However, after an extensive amount
> of Googling, I'm still not clear on the relationship between DMA
> transfers, the USB core and the videobuf2 framework.
>
> Specifically, I'd like to know:
>
> - Can I always use DMA on the USB side (for bulk transfers), or does
> this in any way require support from the USB device's hardware? (I'm
> guessing no, but a definite answer would be great.)
I thought the USB API hides that from you? Nevertheless, this is a
question for linux-usb, not linux-input. I put some people on CC which
work on both, HID and USB. Maybe they can help you.
> - Regardless of the USB side of things, can I use the videobuf2
> framework without _having_ to use DMA? That way, I could get a basic
> driver running without DMA and switch later when it's convenient and/or
> the speedup is justified.
This is definitely a question for linux-media.
Thanks
David
prev parent reply other threads:[~2014-12-11 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 7:50 [sur40] videobuf2 and/or DMA? Florian Echtler
2014-12-11 8:58 ` David Herrmann [this message]
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=CANq1E4QXAyGccPExgvZJO74aBwEOHHM8_Ysv8nx8dLmcmVBnCA@mail.gmail.com \
--to=dh.herrmann@gmail.com \
--cc=floe@butterbrot.org \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=stern@rowland.harvard.edu \
/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).