From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: yfw <nh26223@gmail.com>, Bin Liu <b-liu@ti.com>,
linux-usb@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: g_webcam Isoch high bandwidth transfer
Date: Tue, 27 Sep 2016 10:10:24 +0300 [thread overview]
Message-ID: <87lgyd4y3j.fsf@linux.intel.com> (raw)
In-Reply-To: <1685763.WH6ULF9Rxs@avalon>
[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]
Hi,
Laurent Pinchart <laurent.pinchart@ideasonboard.com> writes:
> Hi Felipe,
>
> On Friday 23 Sep 2016 11:27:26 Felipe Balbi wrote:
>> yfw <nh26223@gmail.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
>> >> usb_function_active() and usb_function_deactivate() are unbalanced. Do
>> >> you have any other changes to g_webcam?
>> >
>> > With uvc function gadget driver, user daemon uvc-gadget must be started
>> > before connect to host. Not sure whether g_webcam has same requirement.
>>
>> f_uvc.c should be handling that by means for usb_function_deactivate().
>>
>> I'll try keeping cable disconnected until uvc-gadget is running.
>
> Things might have changed since we've discussed the issue several years ago,
> but back then at least the musb UDC started unconditionally connected.
That's kinda of not the case anymore. We deactivate during function
registration if a certain flag is set.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
next prev parent reply other threads:[~2016-09-27 7:10 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 [this message]
2016-09-26 14:02 ` Bin Liu
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=87lgyd4y3j.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=b-liu@ti.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).