Linux USB
 help / color / mirror / Atom feed
From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Xu Rao <raoxu@uniontech.com>
Cc: linux-usb@vger.kernel.org, michal.pecio@gmail.com
Subject: Re: [RFT PATCH 0/3] xhci: avoid futile stop endpoint command and host teardown
Date: Tue, 30 Jun 2026 15:19:23 +0300	[thread overview]
Message-ID: <0a2db9bd-027a-4810-9750-8e2041fbe32f@linux.intel.com> (raw)
In-Reply-To: <31BE5DC88420567E+20260630070611.3186010-1-raoxu@uniontech.com>

On 6/30/26 10:06, Xu Rao wrote:
> Hi Mathias,
> 
> I tested this series on the Renesas uPD720201 xHCI controller with the
> GenesysLogic hub and RTL8153 device behind it.
> 
> The original failure is no longer reproduced. After unplugging the hub,
> the xHCI driver no longer tears down the host, and I no longer see:
> 
>    xHCI host not responding to stop endpoint command
>    xHCI host controller not responding, assume dead
> 
> The log also shows the new EP_DROP_PENDING path is used during disconnect,
> for example cancelled TDs are invalidated directly instead of queuing a
> futile Stop Endpoint command.
> 
> 
> Tested-by: Xu Rao <raoxu@uniontech.com>

Thanks for testing.

Do you think this series is enough for the Renesas uPD720201 controller issue
and we can skip the 'Disable soft retry' patch?

Thanks
Mathias


  reply	other threads:[~2026-06-30 12:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29 12:30 [RFT PATCH 0/3] xhci: avoid futile stop endpoint command and host teardown Mathias Nyman
2026-06-29 12:30 ` [RFT PATCH 1/3] xhci: include all root port children in recovery prevention on link error Mathias Nyman
2026-06-29 12:30 ` [RFT PATCH 2/3] xhci: prevent endpoint recovery after roothub disconnect Mathias Nyman
2026-06-29 12:30 ` [RFT PATCH 3/3] xhci: avoid xHC endpoint changes after disconnect or link error Mathias Nyman
2026-06-30  7:06 ` [RFT PATCH 0/3] xhci: avoid futile stop endpoint command and host teardown Xu Rao
2026-06-30 12:19   ` Mathias Nyman [this message]
2026-07-01  8:05     ` raoxu

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=0a2db9bd-027a-4810-9750-8e2041fbe32f@linux.intel.com \
    --to=mathias.nyman@linux.intel.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=michal.pecio@gmail.com \
    --cc=raoxu@uniontech.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