From: Jeff Vanhoof <jdv1029@gmail.com>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Jeffrey Vanhoof <jvanhoof@motorola.com>,
"balbi@kernel.org" <balbi@kernel.org>,
"corbet@lwn.net" <corbet@lwn.net>,
"dan.scally@ideasonboard.com" <dan.scally@ideasonboard.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"laurent.pinchart@ideasonboard.com"
<laurent.pinchart@ideasonboard.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"m.grzeschik@pengutronix.de" <m.grzeschik@pengutronix.de>,
"paul.elder@ideasonboard.com" <paul.elder@ideasonboard.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Dan Vacura <W36195@motorola.com>
Subject: Re: [PATCH v3 2/6] usb: dwc3: gadget: cancel requests instead of release after missed isoc
Date: Thu, 20 Oct 2022 15:53:10 -0500 [thread overview]
Message-ID: <20221020205308.GA6319@qjv001-XeonWs> (raw)
In-Reply-To: <20221020164732.GA25496@qjv001-XeonWs>
Hi Thinh,
> On Wed, Oct 19, 2022 at 11:06:08PM +0000, Thinh Nguyen wrote:
> > Hi,
> >
<snip>
> > >
> > > > The logic to detect underrun doesn't trigger because the queued list is
> > > > always non-empty, but the queued requests are expected to be missed
> > > > already. So you keep seeing missed isoc.
> > > >
> > > > There are a few things you can mitigate this issue:
> > > > 1) Don't set IMI if the request indicates no_interrupt. This reduces the
> > > > time software needs to handle interrupts.
> > >
> > >
> > > > 2) Improve the underrun detection logic.
> > >
> > >
> > > > 3) Increase the queuing frequency from the uvc to keep the request queue
> > > > full. Note that reduce/avoid setting no_interrupt will allow the
> > > > controller driver to update uvc often to keep requeuing new requests.
> > > >
> > > > Best option is 3), but maybe we can do all 3.
> > > >
> > >
I forgot about your option 2. Will start looking into it.
Thanks,
Jeff
next prev parent reply other threads:[~2022-10-20 20:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 20:49 [PATCH v3 2/6] usb: dwc3: gadget: cancel requests instead of release after missed isoc Jeffrey Vanhoof
2022-10-18 22:35 ` Thinh Nguyen
2022-10-19 1:41 ` Jeff Vanhoof
2022-10-19 2:02 ` Thinh Nguyen
2022-10-19 7:40 ` Jeff Vanhoof
2022-10-19 19:08 ` Thinh Nguyen
2022-10-19 21:34 ` Jeff Vanhoof
2022-10-19 23:06 ` Thinh Nguyen
2022-10-20 16:47 ` Jeff Vanhoof
2022-10-20 20:53 ` Jeff Vanhoof [this message]
2022-10-20 22:47 ` Thinh Nguyen
2022-10-21 0:55 ` Thinh Nguyen
2022-10-21 9:39 ` Jeff Vanhoof
2022-10-21 16:43 ` Thinh Nguyen
2022-10-21 18:28 ` Jeff Vanhoof
2022-10-21 19:09 ` Thinh Nguyen
2022-10-21 19:27 ` Jeff Vanhoof
-- strict thread matches above, loose matches on Subject: below --
2022-10-17 20:54 [PATCH v3 0/6] uvc gadget performance issues Dan Vacura
2022-10-17 20:54 ` [PATCH v3 2/6] usb: dwc3: gadget: cancel requests instead of release after missed isoc Dan Vacura
2022-10-17 21:30 ` Thinh Nguyen
2022-10-18 2:10 ` Dan Vacura
2022-10-18 18:45 ` Thinh Nguyen
2022-10-18 19:13 ` Michael Grzeschik
2022-10-18 22:45 ` Thinh Nguyen
2022-10-19 6:46 ` Michael Grzeschik
2024-02-22 0:02 ` Michael Grzeschik
2024-02-22 1:20 ` Thinh Nguyen
2024-02-27 21:01 ` Michael Grzeschik
2024-03-07 1:57 ` Thinh Nguyen
2024-03-07 16:15 ` Michael Grzeschik
2024-03-08 2:47 ` Thinh Nguyen
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=20221020205308.GA6319@qjv001-XeonWs \
--to=jdv1029@gmail.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=W36195@motorola.com \
--cc=balbi@kernel.org \
--cc=corbet@lwn.net \
--cc=dan.scally@ideasonboard.com \
--cc=gregkh@linuxfoundation.org \
--cc=jvanhoof@motorola.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.grzeschik@pengutronix.de \
--cc=paul.elder@ideasonboard.com \
--cc=stable@vger.kernel.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