linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Christian Schaubschläger" <christian.schaubschlaeger@gmx.at>
Cc: linux-usb@vger.kernel.org,
	"michael.simon@cpsd.at" <michael.simon@cpsd.at>
Subject: Re: Possible problem with thunderbolt 4
Date: Fri, 27 Jan 2023 14:27:49 +0200	[thread overview]
Message-ID: <Y9PDRYHHYNSJWwGe@black.fi.intel.com> (raw)
In-Reply-To: <0c9e644e-a07d-e9bb-f8d6-692d2412fd30@gmx.at>

Hi,

On Fri, Jan 27, 2023 at 01:07:43PM +0100, Christian Schaubschläger wrote:
> Hi Mika,
> 
> >>> Previously you said you'd talk with your Windows folks about this; any
> >>> news from there?
> >> I've talked to them and still in talks with the UEFI folks but the
> >> current undestanding is that Windows does not do anything special when
> >> the system is rebooted (so equal to what Linux does). There is one
> >> "development" system in Israel lab that should be pretty similar to what
> >> the HP system of yours is but the person who was going to try to
> >> reproduce is in sick leave now.
> > Ok...
> I was just wondering if there are already any news from your lab in
> Israel with the similar HP system. And if the issue can be reproduced
> there...

Yeah, I just got report from the folks and unfortunately we were not
able to reproduce the issue in the lab. The PCIe tunnel stays up (or
gets re-created) after reboot from Linux and is visible in the UEFI
shell (so in the BIOS).

So at the moment I'm out of ideas why this happens since Windows flows
should be the same. And we have no means to repro it locally to
investigate further :/

> Another thought of mine was, if it wouldn't it be useful to have a kernel commandline switch (or thunderbolt module option) that allows the user to select whether the software connection manager should be used, or the firmware connection manager (if avialable)? I understand that in general using the sw connection manager is favorable because the OS then has control over the connection, but maybe there are use cases where letting the firmware doing the job is just fine (like in my case ;-)

Right, we may add one but I think it should be part of the USB4 _OSC
negotiation like the below patch (acpi.native_usb4_disable=1 in the
command line should switch to FW CM). We could also make it "automatic"
by adding a DMI quirks table that then sets this.

diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
index 0c05ccde1f7a..7da4d56fb936 100644
--- a/drivers/acpi/bus.c
+++ b/drivers/acpi/bus.c
@@ -296,6 +296,9 @@ EXPORT_SYMBOL_GPL(osc_cpc_flexible_adr_space_confirmed);
 /*
  * ACPI 6.4 Operating System Capabilities for USB.
  */
+bool native_usb4_disable;
+module_param(native_usb4_disable, bool, 0644);
+
 bool osc_sb_native_usb4_support_confirmed;
 EXPORT_SYMBOL_GPL(osc_sb_native_usb4_support_confirmed);
 
@@ -344,7 +347,7 @@ static void acpi_bus_osc_negotiate_platform_control(void)
 	if (IS_ENABLED(CONFIG_SCHED_MC_PRIO))
 		capbuf[OSC_SUPPORT_DWORD] |= OSC_SB_CPC_DIVERSE_HIGH_SUPPORT;
 
-	if (IS_ENABLED(CONFIG_USB4))
+	if (IS_ENABLED(CONFIG_USB4) && !native_usb4_disable)
 		capbuf[OSC_SUPPORT_DWORD] |= OSC_SB_NATIVE_USB4_SUPPORT;
 
 	if (!ghes_disable)

  reply	other threads:[~2023-01-27 12:28 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-23 11:24 Possible problem with thunderbolt 4 Christian Schaubschläger
2022-12-27 14:28 ` Mika Westerberg
2022-12-30  7:57   ` Christian Schaubschläger
2022-12-30  9:28     ` Mika Westerberg
2022-12-30 11:38       ` Christian Schaubschläger
2022-12-30 11:55         ` Mika Westerberg
2022-12-30 12:08           ` Christian Schaubschläger
2022-12-30 12:21             ` Mika Westerberg
2023-01-02  8:56               ` Christian Schaubschläger
2023-01-02 11:11                 ` Mika Westerberg
2023-01-02 11:45                   ` Christian Schaubschläger
2023-01-02 16:23                     ` Mika Westerberg
2023-01-03  9:08                       ` Christian Schaubschläger
2023-01-03 11:08                         ` Mika Westerberg
2023-01-03 12:14                           ` Christian Schaubschläger
2023-01-03 16:07                             ` Mika Westerberg
2023-01-03 17:50                               ` Christian Schaubschläger
2023-01-04  8:04                                 ` Mika Westerberg
2023-01-09 12:17                                   ` Christian Schaubschläger
2023-01-09 12:50                                     ` Mika Westerberg
2023-01-09 14:21                                       ` Christian Schaubschläger
2023-01-10 15:12                                         ` Mika Westerberg
2023-01-11 10:38                                           ` Christian Schaubschläger
2023-01-11 10:45                                             ` Mika Westerberg
2023-01-19  9:41                                               ` Christian Schaubschläger
2023-01-19 10:10                                                 ` Mika Westerberg
2023-01-19 14:37                                                   ` Christian Schaubschläger
2023-01-20 10:14                                                     ` Mika Westerberg
2023-01-20 11:19                                                       ` Christian Schaubschläger
2023-01-20 11:36                                                         ` Mika Westerberg
2023-01-27 12:07                                                     ` Christian Schaubschläger
2023-01-27 12:27                                                       ` Mika Westerberg [this message]
2023-01-30 10:52                                                         ` Christian Schaubschläger
2023-01-30 14:10                                                           ` Mika Westerberg
2023-03-06 11:52                                                             ` Mika Westerberg
2023-03-06 12:27                                                               ` Christian Schaubschläger
2023-05-23  8:22                                                                 ` Christian Schaubschläger
2023-05-23  8:55                                                                   ` 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=Y9PDRYHHYNSJWwGe@black.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=christian.schaubschlaeger@gmx.at \
    --cc=linux-usb@vger.kernel.org \
    --cc=michael.simon@cpsd.at \
    /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).