linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Rick <rick@581238.xyz>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
	Sanath.S@amd.com, christian@heusel.eu, fabian@fstab.de,
	gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
	regressions@lists.linux.dev, stable@vger.kernel.org
Subject: Re: Dell WD19TB Thunderbolt Dock not working with kernel > 6.6.28-1
Date: Mon, 4 Nov 2024 08:36:56 +0200	[thread overview]
Message-ID: <20241104063656.GZ275077@black.fi.intel.com> (raw)
In-Reply-To: <70d8b6b2-04b4-48a6-964d-a957b2766617@581238.xyz>

Hi Rick,

On Fri, Nov 01, 2024 at 01:57:50PM +0100, Rick wrote:
> I compiled 6.12.0-rc5-00181-g6c52d4da1c74-dirty resulting in docking station
> not working.
> 
> Then I compiled 6.12.0-rc5-00181-g6c52d4da1c74-dirty without commit
> c6ca1ac9f472 (reverted), and now the docking station works correctly (as in
> screen output + USBs + Ethernet)
> 
> So it seems c6ca1ac9f472 is causing issues for my setup.

Okay, thanks for testing!

It indeed looks like there is no any kind of link issues anymore with
that one reverted. So my suspect is that we are taking too long before
we enumerate the device router which makes it to reset the link.

Can you try the below patch too on top of v6.12-rcX (without the revert)
and see if that still keeps it working? This one cuts down the delay to
1ms which I'm hoping is sufficient for the device. Can you share
dmesg+trace from that test as well?

diff --git a/drivers/thunderbolt/usb4.c b/drivers/thunderbolt/usb4.c
index c6dcc23e8c16..1b740d7fc7da 100644
--- a/drivers/thunderbolt/usb4.c
+++ b/drivers/thunderbolt/usb4.c
@@ -48,7 +48,7 @@ enum usb4_ba_index {
 
 /* Delays in us used with usb4_port_wait_for_bit() */
 #define USB4_PORT_DELAY			50
-#define USB4_PORT_SB_DELAY		5000
+#define USB4_PORT_SB_DELAY		1000
 
 static int usb4_native_switch_op(struct tb_switch *sw, u16 opcode,
 				 u32 *metadata, u8 *status,

  reply	other threads:[~2024-11-04  6:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 12:13 Dell WD19TB Thunderbolt Dock not working with kernel > 6.6.28-1 rick
2024-10-22 12:55 ` Mario Limonciello
2024-10-22 15:44   ` Rick
2024-10-22 16:10     ` Mika Westerberg
2024-10-22 16:25       ` Mario Limonciello
2024-10-22 17:06       ` Rick
2024-10-23  6:10         ` Mika Westerberg
2024-10-25 10:20           ` Rick
2024-10-28  8:18             ` Mika Westerberg
2024-10-30  7:11               ` Rick
2024-10-30  9:06                 ` Mika Westerberg
2024-11-01 12:57                   ` Rick
2024-11-04  6:36                     ` Mika Westerberg [this message]
2024-11-04 18:04                       ` Rick
2024-11-05  6:31                         ` Mika Westerberg
2024-11-05  8:12                           ` Rick
     [not found] <CAPX310gmJeYhE2C6-==rKSDh6wAmoR8R5-pjEOgYD3AP+Si+0w@mail.gmail.com>
2024-09-23  6:45 ` Greg KH
2024-09-24  6:58   ` Fabian Stäber
2024-10-07 16:49     ` Fabian Stäber
2024-10-07 17:13       ` Linux regression tracking (Thorsten Leemhuis)
2024-10-07 17:21       ` Christian Heusel
2024-10-07 17:33         ` Mario Limonciello
2024-10-08 16:56           ` 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=20241104063656.GZ275077@black.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=Sanath.S@amd.com \
    --cc=christian@heusel.eu \
    --cc=fabian@fstab.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=regressions@lists.linux.dev \
    --cc=rick@581238.xyz \
    --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;
as well as URLs for NNTP newsgroup(s).