From: "Chunfeng Yun (云春峰)" <Chunfeng.Yun@mediatek.com>
To: "mika.westerberg@linux.intel.com" <mika.westerberg@linux.intel.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"westeri@kernel.org" <westeri@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"YehezkelShB@gmail.com" <YehezkelShB@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"andreas.noever@gmail.com" <andreas.noever@gmail.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH 3/4] thunderbolt: improve usb3 adapter link up timeout value
Date: Tue, 3 Nov 2026 08:13:29 +0000 [thread overview]
Message-ID: <1a0454774660f90e1b6b475baa3931ebedb020e4.camel@mediatek.com> (raw)
In-Reply-To: <20261030085045.GR158991@black.igk.intel.com>
On Fri, 2026-10-30 at 09:50 +0100, Mika Westerberg wrote:
> On Fri, Oct 30, 2026 at 04:25:38PM +0800, Chunfeng Yun wrote:
> > when plug into a usb3 device into usb4 hub's DFP to trigger usb4
>
> USB 3 device into USB4 hub's downstream facing port to ...
Ok
>
> > driver wakeup, encounter usb3 link up timeout issue, then cause
> > usb3 hub disconnect:
> >
> > usb4_hi NVDA8100:00: 0:1: failed to reach state TB_PORT_UP.
> > Ignoring port...
> > usb4_hi NVDA8100:00: 0:1: lost during suspend, disconnecting
> > usb4_hi NVDA8100:00: 0:4 <-> 1:20 (USB3): deactivating
> > usb4_hi NVDA8100:00: deactivating USB3 Down path from 0:4 to 1:20
> > usb4_hi NVDA8100:00: deactivating USB3 Up path from 1:20 to 0:4
> > ...
> > thunderbolt 0-1: device disconnected
> > usb 2-1: USB disconnect, device number 10
> >
> > Completes link training at ~1.48s and transitions to TB_PORT_UP
> > after
> > change the timeout to 2.5s:
> >
> > In the USB4 spec, Phase 5 (Link Equalization) alone is allowed up
> > to
> > 1000 ms. When add tPhase3 (100 ms), tPhase4 (100 ms), and retimer
> > transaction delays (tCmdResponse = 50 ms), the physical link is
> > allowed by spec to take 1200 ms to 1500 ms+ to complete
> > initialization.
> >
> > here are two retimers in the link, if more retimers add it, need
> > more
> > time
> >
> > Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> > ---
> > drivers/thunderbolt/switch.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/thunderbolt/switch.c
> > b/drivers/thunderbolt/switch.c
> > index d22d8db8f890..e7ee9639c54c 100644
> > --- a/drivers/thunderbolt/switch.c
> > +++ b/drivers/thunderbolt/switch.c
> > @@ -500,8 +500,9 @@ int tb_port_state(struct tb_port *port)
> > */
> > int tb_wait_for_port(struct tb_port *port, bool wait_if_unplugged)
> > {
> > - int retries = 10;
> > + int retries = 25;
> > int state;
> > +
>
> This is unrelated change.
will remove it.
Thanks
>
> > if (!port->cap_phy) {
> > tb_port_WARN(port, "does not have PHY\n");
> > return -EINVAL;
> > --
> > 2.43.0
next prev parent reply other threads:[~2026-11-03 8:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 8:25 [PATCH 0/4] add support platform nhi driver Chunfeng Yun
2026-10-30 8:25 ` [PATCH 1/4] thunderbolt: add " Chunfeng Yun
2026-10-30 8:47 ` Mika Westerberg
2026-10-31 3:41 ` kernel test robot
2026-10-31 20:03 ` kernel test robot
2026-10-30 8:25 ` [PATCH 2/4] thunderbolt: add support optional dedicated wakeup irq Chunfeng Yun
2026-10-30 8:48 ` Mika Westerberg
2026-11-03 9:05 ` Chunfeng Yun (云春峰)
2026-11-03 11:59 ` mika.westerberg
2026-10-30 8:25 ` [PATCH 3/4] thunderbolt: improve usb3 adapter link up timeout value Chunfeng Yun
2026-10-30 8:50 ` Mika Westerberg
2026-11-03 8:13 ` Chunfeng Yun (云春峰) [this message]
2026-10-30 8:25 ` [PATCH 4/4] thunderbolt: prevent pcie tunnel activation/teardown warnings Chunfeng Yun
2026-10-30 8:56 ` Mika Westerberg
2026-11-03 8:33 ` Chunfeng Yun (云春峰)
2026-11-03 12:48 ` mika.westerberg
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=1a0454774660f90e1b6b475baa3931ebedb020e4.camel@mediatek.com \
--to=chunfeng.yun@mediatek.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=mika.westerberg@linux.intel.com \
--cc=westeri@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
all inboxes | Powered by JetHome®