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, 30 Dec 2022 13:55:13 +0200 [thread overview]
Message-ID: <Y67RoYvbRC6OgfOq@black.fi.intel.com> (raw)
In-Reply-To: <c334eb1f-1130-04d7-e7a6-cce9a90fd2e8@gmx.at>
On Fri, Dec 30, 2022 at 12:38:27PM +0100, Christian Schaubschläger wrote:
> Ok, setting CONFIG_USB4=n makes everything work as expected! Even
> hotplugging the dock works fine.
Yes but things like power management does not.
> Now I've tried this: CONFIG_USB4=m and blacklist the thunderbolt
> module (because disabling CONFIG_USB4 in general is not an option for
> me (I guess?) There's probably hardware out there where the firmware
> doesn't set up the PCIe tunnels. Then I need the linux thunderbolt
> driver to do this I suppose).
You must have CONFIG_USB4=n because that makes the Linux ACPI core not
to negotiate software connection manager support. Blaclisting the
Thunderbolt driver does not do that as that code is always built-in.
> So with CONFIG_USB=m and blacklisting the thunderbolt module this
> happens: the tunnel is there before and after linux (PXE works), but
> in linux none of the devices that sit behind the PCIe tunnel (network,
> external display) are there... that's strange, because I would have
> expected that CONFIG_USB4=m + blacklist thunderbolt would be the same
> as CONFIG_USB4=n. Which obviously isn't the case. I've attached lspci
> output from either case.
See above.
> Is there any other option to decide at boottime whether or not to use
> the USB4 driver (besides using two different kernels)?
No but this is not the "final" solution - just an experiment.
Okay so we have this:
- When both Linux and Windows uses the same firmware connection manager
all work.
- If you install Windows 11 (or whatever the fresh one is that actually
supports USB4 and software connection manager) you end up in the
exact same situation.
Can you try following:
1. Go back to CONFIG_USB4=m
2. Boot the system up
3. Check that the PCIe tunneling is up and things work as expected
4. Unplug the dock
5. Unload the Thunderbolt driver
# rmmod thunderbolt
6. Plug the dock back
7. Soft reboot the system
Does this make the PXE boot see the connected device?
next prev parent reply other threads:[~2022-12-30 11:54 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 [this message]
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
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=Y67RoYvbRC6OgfOq@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 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.