From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Matt Eaton <linux@divinehawk.com>
Cc: Michal Pecio <michal.pecio@gmail.com>,
Matt Eaton via B4 Relay <devnull+linux.divinehawk.com@kernel.org>,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] usb: xhci-plat: add xhci-no-soft-retry-quirk device property
Date: Wed, 2 Sep 2026 02:42:40 +0000 [thread overview]
Message-ID: <apeKnh72CUPjwMkQ@vbox> (raw)
In-Reply-To: <CABUBpLf_mA8GmjAn8+-xgz8H5XOvBCr9DRWU8Eqc9=BW9m00Bg@mail.gmail.com>
On Mon, Aug 31, 2026, Matt Eaton wrote:
> On Sun, Aug 30, 2026 at 5:02 PM Michal Pecio <michal.pecio@gmail.com> wrote:
> >
> > On Sat, 29 Aug 2026 22:04:10 +0200, Matt Eaton via B4 Relay wrote:
> > > From: Matt Eaton <linux@divinehawk.com>
> > >
> > >
> > > xhci-hcd xhci-hcd.1.auto: xHCI host not responding to stop endpoint command
> > > xhci-hcd xhci-hcd.1.auto: xHCI host controller not responding, assume dead
> > > xhci-hcd xhci-hcd.1.auto: HC died; cleaning up
> >
> > Hi,
> >
> > Does it still happen in current Linus tree aka upcoming v7.3-rc1?
> >
> > Similar problem, limited to the specific case of disconnection from the
> > root hub, was found on Renesas PCIe controllers (it looked like some
> > internal power management interfering with operation). It seems to be
> > solved by avoiding Soft Retry on known-disconnected root hub ports.
>
> I applied these (from 7.3-rc1) to my 6.18 kernel and appears to fix the issue:
>
> commit e3d757dc9257
> commit 042aad8d0db6
> commit 7e0ef4332ed9
>
> There does not appear to be a need to apply this patchset now. Thanks!
>
Good to hear the upstream fix resolves it. Separate question though, are
you still planning to carry the IPQ4019 migration to the new flattened
dwc3-qcom glue (patch 3/3 + the DT compatible change)? It may be worth
keeping regardless of the quirk, since it fixes the legacy glue's race
conditions and gives you a way to pass custom dwc3 properties from the
glue to the core if you need to in the future.
Thanks,
Thinh
next prev parent reply other threads:[~2026-09-02 2:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 20:04 [PATCH v2 0/3] usb: xhci: add xhci-no-soft-retry-quirk Matt Eaton
2026-08-29 20:04 ` Matt Eaton via B4 Relay
2026-08-29 20:04 ` [PATCH v2 1/3] usb: xhci-plat: add xhci-no-soft-retry-quirk device property Matt Eaton
2026-08-29 20:04 ` Matt Eaton via B4 Relay
2026-08-30 15:02 ` Michal Pecio
2026-08-31 0:58 ` Matt Eaton
2026-08-31 3:38 ` Michal Pecio
2026-08-31 17:00 ` Matt Eaton
2026-09-02 2:42 ` Thinh Nguyen [this message]
2026-08-29 20:04 ` [PATCH v2 2/3] usb: dwc3: add xhci_no_soft_retry software property Matt Eaton
2026-08-29 20:04 ` Matt Eaton via B4 Relay
2026-08-30 9:33 ` Matt Eaton
2026-08-29 20:04 ` [PATCH v2 3/3] usb: dwc3: qcom: set xhci_no_soft_retry for IPQ4019 Matt Eaton
2026-08-29 20:04 ` Matt Eaton via B4 Relay
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=apeKnh72CUPjwMkQ@vbox \
--to=thinh.nguyen@synopsys.com \
--cc=devnull+linux.divinehawk.com@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@divinehawk.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.