Hi Felipe, > -----Original Message----- > From: Felipe Balbi [mailto:balbi@xxxxxx] > Sent: Monday, June 04, 2012 8:44 PM > To: Bhupesh SHARMA > Cc: laurent.pinchart@xxxxxxxxxxxxxxxx; linux-usb@xxxxxxxxxxxxxxx; > balbi@xxxxxx; linux-media@xxxxxxxxxxxxxxx; gregkh@xxxxxxxxxxxxxxxxxxx > Subject: Re: [PATCH 4/5] usb: gadget/uvc: Port UVC webcam gadget to use > videobuf2 framework > > On Fri, Jun 01, 2012 at 03:08:57PM +0530, Bhupesh Sharma wrote: > > This patch reworks the videobuffer management logic present in the > UVC > > webcam gadget and ports it to use the "more apt" videobuf2 framework > > for video buffer management. > > > > To support routing video data captured from a real V4L2 video capture > > device with a "zero copy" operation on videobuffers (as they pass > from > > the V4L2 domain to UVC domain via a user-space application), we need > > to support USER_PTR IO method at the UVC gadget side. > > > > So the V4L2 capture device driver can still continue to use MMAO IO > > method and now the user-space application can just pass a pointer to > > the video buffers being DeQueued from the V4L2 device side while > > Queueing them at the UVC gadget end. This ensures that we have a > > "zero-copy" design as the videobuffers pass from the V4L2 capture > device to the UVC gadget. > > > > Note that there will still be a need to apply UVC specific payload > > headers on top of each UVC payload data, which will still require a > > copy operation to be performed in the 'encode' routines of the UVC > gadget. > > > > Signed-off-by: Bhupesh Sharma <bhupesh.sharma@xxxxxx> > > this patch doesn't apply. Please refresh on top of v3.5-rc1 or my > gadget branch which I will update in a while. > I rebased and submitted my changes on your "gadget-for-v3.5" tag. Should I now refresh my patches on top of your "v3.5-rc1" branch ? I am a bit confused on what is the latest gadget branch to be used now. Thanks for helping out. Regards, Bhupesh -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
