public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] usb: gadget: Kernel oops with UVC USB gadget and configfs
Date: Sun, 12 Feb 2017 13:02:52 +0100	[thread overview]
Message-ID: <8737fj1us3.fsf@belgarion.home> (raw)
In-Reply-To: <3faadfcb-5e0d-8f92-3e91-4bd745026644@tul.cz> (Petr Cvek's message of "Sun, 12 Feb 2017 02:15:43 +0100")

Petr Cvek <petr.cvek@tul.cz> writes:

> Hi
>
> any news?

Yeah, I don't have the error on my mainstone, which kind of hinders my debug
capability.

I have tried your script, and this is what I get :
  - dmesg | tail
	random: crng init done
	gadgetfs: USB Gadget filesystem, version 24 Aug 2004
	configfs-gadget gadget: uvc_function_bind
	[DEBUG] opts->streaming_maxpacket=256
	====name: ep1in-int, mp=16
	====name: ep1in-int, mp=16
	====name: ep2in-int, mp=16
	====name: ep3out-int, mp=16
	====name: ep4in-iso, mp=256
  - lsmod
	Module                  Size  Used by    Not tainted
	usb_f_uvc              40752  6 
	libcomposite           38099 14 usb_f_uvc
	pxa27x_udc             21131  0 
	gadgetfs               16173  0 
	videobuf2_vmalloc       4659  1 usb_f_uvc
	videobuf2_memops        1421  1 videobuf2_vmalloc

This was tried on a mainstone board, upon mainline kernel v4.8-rc3 with your
patch. but without an actual camera nor the USB cable attached to a host USB.

Cheers.

-- 
Robert

  reply	other threads:[~2017-02-12 12:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24 15:14 [BUG] usb: gadget: Kernel oops with UVC USB gadget and configfs Petr Cvek
2017-02-04 22:42 ` Robert Jarzmik
2017-02-05 23:01   ` Petr Cvek
2017-02-12  1:15   ` Petr Cvek
2017-02-12 12:02     ` Robert Jarzmik [this message]
2017-02-13  3:04       ` Petr Cvek
2017-02-13 19:29         ` Robert Jarzmik
2017-02-14 13:46           ` 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=8737fj1us3.fsf@belgarion.home \
    --to=robert.jarzmik@free.fr \
    --cc=linux-arm-kernel@lists.infradead.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