Linux USB
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: laurent.pinchart@ideasonboard.com, dan.scally@ideasonboard.com,
	m.grzeschik@pengutronix.de, jun.li@nxp.com, imx@lists.linux.dev,
	linux-usb@vger.kernel.org
Subject: Re: [RESEND] usb: gadget: uvc: queue pump work in uvcg_video_enable()
Date: Wed, 14 Aug 2024 16:10:53 +0200	[thread overview]
Message-ID: <2024081438-power-surplus-d4d4@gregkh> (raw)
In-Reply-To: <20240814134802.tksdhu7yexuuknqy@hippo>

On Wed, Aug 14, 2024 at 09:48:02PM +0800, Xu Yang wrote:
> On Wed, Aug 14, 2024 at 01:47:23PM +0200, Greg KH wrote:
> > On Wed, Aug 14, 2024 at 07:25:37PM +0800, Xu Yang wrote:
> > > Since commit "6acba0345b68 usb:gadget:uvc Do not use worker thread to pump
> > > isoc usb requests", pump work could only be queued in uvc_video_complete()
> > > and uvc_v4l2_qbuf(). If VIDIOC_QBUF is executed before VIDIOC_STREAMON,
> > > we can only depend on uvc_video_complete() to queue pump work. However,
> > > this requires some free requests in req_ready list. If req_ready list is
> > > empty all the time, pump work will never be queued and video datas will
> > > never be pumped to usb controller. Actually, this situation could happen
> > > when run uvc-gadget with static image:
> > > 
> > > $ ./uvc-gadget -i 1080p.jpg uvc.0
> > > 
> > > When capture image from this device, the user app will always block there.
> > > 
> > > The issue is uvc driver has queued video buffer before streamon, but the
> > > req_ready list is empty all the time after streamon. This will queue pump
> > > work in uvcg_video_enable() to fill some request to req_ready list so the
> > > uvc device could work properly.
> > > 
> > > Fixes: 6acba0345b68 ("usb:gadget:uvc Do not use worker thread to pump isoc usb requests")
> > > Cc: stable@vger.kernel.org
> > > Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
> > > ---
> > >  drivers/usb/gadget/function/uvc_video.c | 1 +
> > >  1 file changed, 1 insertion(+)
> > 
> > Why is this a RESEND?  What happened to the first one to require this?
> 
> I accidentally forgot to cc usb maillist in previous one. So I resend it.

Please always tell us why you are doing something, otherwise we have no
idea :(

  reply	other threads:[~2024-08-14 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 11:25 [RESEND] usb: gadget: uvc: queue pump work in uvcg_video_enable() Xu Yang
2024-08-14 11:47 ` Greg KH
2024-08-14 13:48   ` Xu Yang
2024-08-14 14:10     ` Greg KH [this message]
2024-08-15  2:02       ` Xu Yang

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=2024081438-power-surplus-d4d4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.scally@ideasonboard.com \
    --cc=imx@lists.linux.dev \
    --cc=jun.li@nxp.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.grzeschik@pengutronix.de \
    --cc=xu.yang_2@nxp.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