public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Chia-Lin Kao (AceLan)" <acelan.kao@canonical.com>,
	Mario Limonciello <mario.limonciello@amd.com>,
	Andreas Noever <andreas.noever@gmail.com>,
	Mika Westerberg <westeri@kernel.org>,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sanath.S@amd.com, "Lin, Wayne" <Wayne.Lin@amd.com>
Subject: Re: [PATCH] [RFC] thunderbolt: Add delay for Dell U2725QE link width
Date: Mon, 5 Jan 2026 12:19:35 +0100	[thread overview]
Message-ID: <20260105111935.GM2275908@black.igk.intel.com> (raw)
In-Reply-To: <xgreoxrfzdgeupv4q7ge7ivjwz7dll7khohm4wetjjm3waztwo@lrr2kjdjpdba>

On Fri, Jan 02, 2026 at 10:03:12AM +0800, Chia-Lin Kao (AceLan) wrote:
> > You only have one of those monitors? It would be good to check with another
> > if it has the same issue. I have GR reference device here which is what
> > this monitor is based on but I don't see any unplugs or link issues. I will
> > ask around if we have somewhere this monitor.
>
> Here is another BenQ 5k thunderbolt 4 monitor, and I can't reproduce
> the issue with this monitor, even with the AMD machine.
> 
> https://people.canonical.com/~acelan/bugs/tbt_call_trace/intel/merged_6.18.0-d358e5254674+.benq.out

Okay thanks! We have one Dell GR based monitor here (not the same as yours)
and a Lenovo GR based one. I asked the folks to try to repro the issue and
will share the results once I get them.

      reply	other threads:[~2026-01-05 11:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-09  5:41 [PATCH] [RFC] thunderbolt: Add delay for Dell U2725QE link width Chia-Lin Kao (AceLan)
2025-12-09  7:06 ` Mika Westerberg
2025-12-09 16:49   ` Mario Limonciello
2025-12-10  5:33     ` Chia-Lin Kao (AceLan)
2025-12-10  3:15   ` Chia-Lin Kao (AceLan)
2025-12-10  7:41     ` Mika Westerberg
2025-12-10 21:42       ` Mario Limonciello
     [not found]         ` <coxrm5gishdztghznuvzafg2pbdk4qk3ttbkbq7t5whsfv2lk5@3gqepcs6h4uc>
2025-12-12 12:39           ` Mika Westerberg
2025-12-12 14:40             ` Mario Limonciello
2025-12-17  3:06               ` AceLan Kao
2025-12-17 12:55                 ` Mika Westerberg
2025-12-17 15:53                   ` Mario Limonciello
2025-12-18  1:38                     ` AceLan Kao
2025-12-18  7:21                       ` Mika Westerberg
     [not found]                         ` <6inne3luvw4ot3wqnsaw3gzhlxtd4756i465oto6so5ox3syxp@kibuv4vhvexx>
2025-12-18 10:20                           ` Mika Westerberg
2025-12-22  1:33                             ` Chia-Lin Kao (AceLan)
2025-12-30  7:30                               ` Mika Westerberg
2025-12-31  1:33                                 ` Chia-Lin Kao (AceLan)
2025-12-31  6:03                                   ` Mika Westerberg
2026-01-02  2:03                                     ` Chia-Lin Kao (AceLan)
2026-01-05 11:19                                       ` Mika Westerberg [this message]

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=20260105111935.GM2275908@black.igk.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=Sanath.S@amd.com \
    --cc=Wayne.Lin@amd.com \
    --cc=YehezkelShB@gmail.com \
    --cc=acelan.kao@canonical.com \
    --cc=andreas.noever@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mario.limonciello@amd.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