linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Florian Echtler <floe@butterbrot.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	linux-input@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] add raw video support for Samsung SUR40 touchscreen
Date: Wed, 04 Feb 2015 16:06:05 +0200	[thread overview]
Message-ID: <1606232.uUWpMankZz@avalon> (raw)
In-Reply-To: <54D21CEB.1090506@butterbrot.org>

Hi Florian,

On Wednesday 04 February 2015 14:21:47 Florian Echtler wrote:
> On 04.02.2015 12:39, Hans Verkuil wrote:
> > On 02/04/15 12:34, Laurent Pinchart wrote:
> >> On Wednesday 04 February 2015 11:56:58 Florian Echtler wrote:
> >>> That's what I assumed, however, I'm running into the same problem as
> >>> with dma-sg when I switch to vmalloc...?
> >> 
> >> I don't expect vmalloc to work, as you can't DMA to vmalloc memory
> >> directly without any IOMMU in the general case (the allocated memory
> >> being physically fragmented).
> >> 
> >> dma-sg should work though, but you won't be able to use usb_bulk_msg().
> >> You need to create the URBs manually, set their sg and num_sgs fields and
> >> submit them.
> 
> Can I also use usb_sg_init/_wait for this? I can't find any other driver
> which uses USB in conjunction with dma-sg, can you suggest one I could
> use as an example?

usb_sg_init() is an interesting abstraction that transparently splits SG lists 
into several URBs if the USB host controller can't support SG lists directly. 
Unfortunately the API is blocking. It shouldn't be too difficult to add an 
asynchronous option with a complete callback.

> > Anyway Florian, based on Laurent's explanation I think trying to make
> > dma-sg work seems to be the best solution. And I've learned something
> > new :-)
> 
> Thanks for the clarification, please ignore the v2 patch submission for
> now :-)

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2015-02-04 14:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 10:35 [PATCH] add raw video support for Samsung SUR40 touchscreen Florian Echtler
2015-01-19 10:38 ` Hans Verkuil
2015-01-20  9:24   ` Florian Echtler
2015-01-20  9:30     ` Hans Verkuil
2015-01-20 12:59       ` Laurent Pinchart
2015-01-20 13:03         ` Hans Verkuil
2015-01-20 13:06           ` Laurent Pinchart
2015-01-21 13:28             ` Florian Echtler
2015-01-21 13:29               ` Hans Verkuil
2015-01-29 21:35                 ` Florian Echtler
2015-02-03 20:45                   ` Florian Echtler
2015-02-04  8:08                     ` Hans Verkuil
2015-02-04 10:08                       ` Florian Echtler
2015-02-04 10:22                         ` Hans Verkuil
2015-02-04 10:56                           ` Florian Echtler
2015-02-04 11:34                             ` Laurent Pinchart
2015-02-04 11:39                               ` Hans Verkuil
2015-02-04 13:21                                 ` Florian Echtler
2015-02-04 14:06                                   ` Laurent Pinchart [this message]
2015-02-04 13:51                                 ` Laurent Pinchart

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=1606232.uUWpMankZz@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=floe@butterbrot.org \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-media@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).