From: "Neronin, Niklas" <niklas.neronin@linux.intel.com>
To: Michal Pecio <michal.pecio@gmail.com>,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] usb: xhci: Clean up the TD skipping loop
Date: Sat, 22 Feb 2025 14:37:58 +0200 [thread overview]
Message-ID: <be026374-91d2-4b1d-9eb7-568b376f6e72@linux.intel.com> (raw)
In-Reply-To: <20250210083940.626c02d9@foxbook>
On 10/02/2025 9.39, Michal Pecio wrote:
> Half of this loop is code which only executes once to deal with cases
> where no TD matches the event and then immediately returns. This code
> has no need to be in any kind of loop, so get it out.
>
> Shuffle the remaining conditionals a little to improve readability.
>
> No functional change.
>
> Signed-off-by: Michal Pecio <michal.pecio@gmail.com>
> ---
>
> - if (!ep_seg) {
> + if (ep->skip) {
>
> - if (ep->skip && usb_endpoint_xfer_isoc(&td->urb->ep->desc)) {
> + if (!ep_seg && usb_endpoint_xfer_isoc(&td->urb->ep->desc)) {
> skip_isoc_td(xhci, td, ep, status);
> if (!list_empty(&ep_ring->td_list))
> continue;
> @@ -2880,38 +2880,6 @@ static int handle_tx_event(struct xhci_hcd *xhci,
> goto check_endpoint_halted;
> }
>
> - /*
> - * Skip the Force Stopped Event. The 'ep_trb' of FSE is not in the current
> - * TD pointed by 'ep_ring->dequeue' because that the hardware dequeue
> - * pointer still at the previous TRB of the current TD. The previous TRB
> - * maybe a Link TD or the last TRB of the previous TD. The command
> - * completion handle will take care the rest.
> - */
> - if (trb_comp_code == COMP_STOPPED ||
> - trb_comp_code == COMP_STOPPED_LENGTH_INVALID) {
> - return 0;
> - }
> -
> - /*
> - * Some hosts give a spurious success event after a short
> - * transfer. Ignore it.
> - */
> - if ((xhci->quirks & XHCI_SPURIOUS_SUCCESS) &&
> - ep_ring->last_td_was_short) {
> - ep_ring->last_td_was_short = false;
> - return 0;
> - }
> -
> - /* HC is busted, give up! */
> - xhci_err(xhci,
> - "ERROR Transfer event TRB DMA ptr not part of current TD ep_index %d comp_code %u\n",
> - ep_index, trb_comp_code);
> - trb_in_td(xhci, td, ep_trb_dma, true);
> -
> - return -ESHUTDOWN;
> - }
> -
> - if (ep->skip) {
> xhci_dbg(xhci,
> "Found td. Clear skip flag for slot %u ep %u.\n",
> slot_id, ep_index);
This debug message is now misleading, the TD way or may not be found on non-isochronous.
Before:
if (ep_seg && ep->skip)
xhci_dbg(xhci, "Found td. ...
After:
if (ep->skip && (ep_seg || !isoc))
xhci_dbg(xhci, "Found td. ...
With Best Regards,
Niklas
next prev parent reply other threads:[~2025-02-22 12:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 7:37 [PATCH 0/5] xHCI: Isochronous error handling fixes and improvements Michal Pecio
2025-02-10 7:38 ` [PATCH 1/5] usb: xhci: Complete 'error mid TD' transfers when handling Missed Service Michal Pecio
2025-02-10 7:39 ` [PATCH 2/5] usb: xhci: Clean up the TD skipping loop Michal Pecio
2025-02-22 12:37 ` Neronin, Niklas [this message]
2025-02-24 0:02 ` Michał Pecio
2025-02-10 7:40 ` [PATCH 3/5] usb: xhci: Fix isochronous Ring Underrun/Overrun event handling Michal Pecio
2025-02-10 7:41 ` [PATCH 4/5] usb: xhci: Expedite skipping missed isoch TDs on modern HCs Michal Pecio
2025-02-10 7:42 ` [PATCH 5/5] usb: xhci: Skip only one TD on Ring Underrun/Overrun Michal Pecio
2025-02-11 15:41 ` Mathias Nyman
2025-02-12 7:30 ` Michał Pecio
2025-02-21 1:17 ` Michał Pecio
2025-02-21 1:18 ` [PATCH v2 3/5] usb: xhci: Fix isochronous Ring Underrun/Overrun event handling Michal Pecio
2025-02-21 1:20 ` [PATCH v2 5/5] usb: xhci: Skip only one TD on Ring Underrun/Overrun Michal Pecio
2025-02-21 13:17 ` [PATCH " Mathias Nyman
-- strict thread matches above, loose matches on Subject: below --
2024-09-10 11:12 [PATCH 0/5] Quick and effective handle_tx_event() cleanup Michal Pecio
2024-09-10 11:14 ` [PATCH 2/5] usb: xhci: Clean up the TD skipping loop Michal Pecio
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=be026374-91d2-4b1d-9eb7-568b376f6e72@linux.intel.com \
--to=niklas.neronin@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=michal.pecio@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