linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Echtler <floe@butterbrot.org>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-input@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] add raw video support for Samsung SUR40 touchscreen
Date: Tue, 03 Feb 2015 21:45:55 +0100	[thread overview]
Message-ID: <54D13383.7010603@butterbrot.org> (raw)
In-Reply-To: <54CAA786.2040908@butterbrot.org>

[-- Attachment #1: Type: text/plain, Size: 2041 bytes --]

Sorry to bring this up again, but would it be acceptable to simply use
dma-contig after all? Since the GFP_DMA flag is gone, this shouldn't be
too big of an issue IMHO, and I was kind of hoping the patch could still
be part of 3.20.

Best, Florian

On 29.01.2015 22:35, Florian Echtler wrote:
> I'm still having a couple of issues sorting out the correct way to
> provide DMA access for my driver. I've integrated most of your
> suggestions, but I still can't switch from dma-contig to dma-sg.
> As far as I understood it, there is no further initialization required
> besides using vb2_dma_sg_memops, vb2_dma_sg_init_ctx and
> vb2_dma_sg_cleanup_ctx instead of the respective -contig- calls, correct?
> However, as soon as I swap the relevant function calls, the video image
> stays black and in dmesg, I get the following warning:
>
> Call Trace:
> [<ffffffff817c4584>] dump_stack+0x45/0x57
> [<ffffffff81076df7>] warn_slowpath_common+0x97/0xe0
> [<ffffffff81076ef6>] warn_slowpath_fmt+0x46/0x50
> [<ffffffff815aff0b>] usb_hcd_map_urb_for_dma+0x4eb/0x500
> [<ffffffff817d03b4>] ? schedule_timeout+0x124/0x210
> [<ffffffff815b0bd5>] usb_hcd_submit_urb+0x135/0x1c0
> [<ffffffff815b20a6>] usb_submit_urb.part.8+0x1f6/0x580
> [<ffffffff811bb542>] ? vmap_pud_range+0x122/0x1c0
> [<ffffffff815b2465>] usb_submit_urb+0x35/0x80
> [<ffffffff815b339a>] usb_start_wait_urb+0x6a/0x170
> [<ffffffff815b1cce>] ? usb_alloc_urb+0x1e/0x50
> [<ffffffff815b1cce>] ? usb_alloc_urb+0x1e/0x50
> [<ffffffff815b3570>] usb_bulk_msg+0xd0/0x1a0
> [<ffffffffc059a841>] sur40_poll+0x561/0x5e0 [sur40]
>
> Moreover, I'm getting the following test failure from v4l2-compliance:
> 
> Streaming ioctls:
> 	test read/write: OK
> 	test MMAP: OK
> 		fail: v4l2-test-buffers.cpp(951): buf.qbuf(node)
> 		fail: v4l2-test-buffers.cpp(994): setupUserPtr(node, q)
> 	test USERPTR: FAIL
> 	test DMABUF: Cannot test, specify --expbuf-device
> 
> Total: 45, Succeeded: 44, Failed: 1, Warnings: 0


-- 
SENT FROM MY DEC VT50 TERMINAL


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2015-02-03 20:45 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 [this message]
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
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=54D13383.7010603@butterbrot.org \
    --to=floe@butterbrot.org \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --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).