From: Bin Liu <b-liu@ti.com>
To: Felipe Balbi <felipe.balbi@linux.intel.com>
Cc: <linux-usb@vger.kernel.org>, <linux-media@vger.kernel.org>,
<nh26223@gmail.com>, <laurent.pinchart@ideasonboard.com>
Subject: Re: g_webcam Isoch high bandwidth transfer
Date: Mon, 26 Sep 2016 09:02:48 -0500 [thread overview]
Message-ID: <20160926140248.GF31827@uda0271908> (raw)
In-Reply-To: <87shsr5a3e.fsf@linux.intel.com>
On Fri, Sep 23, 2016 at 10:49:57AM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Bin Liu <b-liu@ti.com> writes:
> > +Fengwei Yin per his request.
> >
> > On Thu, Sep 22, 2016 at 10:48:40PM +0300, Felipe Balbi wrote:
> >>
> >> Hi,
> >>
> >> Bin Liu <b-liu@ti.com> writes:
> >>
> >> [...]
> >>
> >> >> Here's one that actually compiles, sorry about that.
> >> >
> >> > No worries, I was sleeping ;-)
> >> >
> >> > I will test it out early next week. Thanks.
> >>
> >> meanwhile, how about some instructions on how to test this out myself?
> >> How are you using g_webcam and what are you running on host side? Got a
> >> nice list of commands there I can use? I think I can get to bottom of
> >> this much quicker if I can reproduce it locally ;-)
> >
> > On device side:
> > - first patch g_webcam as in my first email in this thread to enable
> > 640x480@30fps;
> > - # modprobe g_webcam streaming_maxpacket=3072
> > - then run uvc-gadget to feed the YUV frames;
> > http://git.ideasonboard.org/uvc-gadget.git
>
> as is, g_webcam never enumerates to the host. It's calls to
Right, on mainline kernel (I tested 4.8.0-rc7) g_webcam is broken with
DWC3, g_webcam does not enumerate on the host. But it works on v4.4.21.
[snip]
>
> uvc-gadget keeps printing this error message:
>
> 159 if ((ret = ioctl(dev->fd, VIDIOC_DQBUF, &buf)) < 0) {
> 160 printf("Unable to dequeue buffer: %s (%d).\n", strerror(errno),
> 161 errno);
> 162 return ret;
> 163 }
I removed this printf, since it floods the console if start uvc-gadget
before connect to the host.
BTY, you don't have to start uvc-gadget first then connect usb cable. I
keep the cable always connected.
Regards,
-Bin.
next prev parent reply other threads:[~2016-09-26 14:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 17:04 g_webcam Isoch high bandwidth transfer Bin Liu
2016-09-21 8:01 ` Felipe Balbi
2016-09-21 13:27 ` Bin Liu
2016-09-21 14:58 ` Bin Liu
2016-09-22 7:37 ` Felipe Balbi
2016-09-22 8:08 ` Felipe Balbi
2016-09-22 10:06 ` Felipe Balbi
2016-09-22 13:33 ` Bin Liu
2016-09-22 19:48 ` Felipe Balbi
2016-09-22 20:11 ` Bin Liu
2016-09-23 0:23 ` yfw
2016-09-23 7:49 ` Felipe Balbi
2016-09-23 8:10 ` yfw
2016-09-23 8:27 ` Felipe Balbi
2016-09-26 16:06 ` Laurent Pinchart
2016-09-27 7:10 ` Felipe Balbi
2016-09-26 14:02 ` Bin Liu [this message]
2016-09-27 7:14 ` Felipe Balbi
2016-09-26 16:03 ` 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=20160926140248.GF31827@uda0271908 \
--to=b-liu@ti.com \
--cc=felipe.balbi@linux.intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nh26223@gmail.com \
/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).