From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 208891] Thunderbolt hotplug fails on HP x360 13t-aw000/86FA with HP Thunderbolt 3 Dock
Date: Mon, 17 Aug 2020 10:43:44 +0000 [thread overview]
Message-ID: <bug-208891-208809-XxvmdBW11o@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208891-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208891
--- Comment #23 from Mika Westerberg (mika.westerberg@linux.intel.com) ---
When you boot the system with device connected it is the BIOS that configures
the PCIe devices. When you hot-plug the device to the running system it is the
kernel PCI stack that does the configuration (no Thunderbolt driver is even
involved here, it is just plain PCIe).
The Linux PCI stack should be able to do this but for some reason on your
particular system it does not work as expected - it succeeds to configure
everything just fine but immediately after the two downstream PCIe ports lose
what is configured to their bridge window registers so I kind of suspected that
the runtime PM kicks in here but apparently that is not the case.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-08-17 10:43 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 22:17 [Bug 208891] New: Thunderbolt hotplug fails on HP x360 13t-aw000/86FA with HP Thunderbolt 3 Dock bugzilla-daemon
2020-08-12 22:18 ` [Bug 208891] " bugzilla-daemon
2020-08-12 22:18 ` bugzilla-daemon
2020-08-12 22:18 ` bugzilla-daemon
2020-08-12 22:19 ` bugzilla-daemon
2020-08-12 22:19 ` bugzilla-daemon
2020-08-12 22:19 ` bugzilla-daemon
2020-08-12 22:20 ` bugzilla-daemon
2020-08-12 22:20 ` bugzilla-daemon
2020-08-12 22:20 ` bugzilla-daemon
2020-08-12 22:34 ` bugzilla-daemon
2020-08-12 22:34 ` bugzilla-daemon
2020-08-12 22:39 ` bugzilla-daemon
2020-08-13 8:18 ` bugzilla-daemon
2020-08-13 17:32 ` bugzilla-daemon
2020-08-14 6:54 ` bugzilla-daemon
2020-08-14 6:56 ` bugzilla-daemon
2020-08-14 7:09 ` bugzilla-daemon
2020-08-14 7:09 ` bugzilla-daemon
2020-08-14 7:15 ` bugzilla-daemon
2020-08-14 7:15 ` bugzilla-daemon
2020-08-14 12:51 ` bugzilla-daemon
2020-08-14 21:36 ` bugzilla-daemon
2020-08-17 10:43 ` bugzilla-daemon [this message]
2020-08-19 14:00 ` bugzilla-daemon
2020-08-23 19:02 ` bugzilla-daemon
2020-08-27 19:57 ` bugzilla-daemon
2020-08-27 19:58 ` bugzilla-daemon
2020-08-27 19:59 ` bugzilla-daemon
2020-08-27 20:00 ` bugzilla-daemon
2020-08-27 20:06 ` bugzilla-daemon
2020-08-31 13:24 ` bugzilla-daemon
2020-08-31 19:30 ` bugzilla-daemon
2020-08-31 19:30 ` bugzilla-daemon
2020-08-31 19:37 ` bugzilla-daemon
2020-08-31 19:40 ` bugzilla-daemon
2020-09-04 20:28 ` bugzilla-daemon
2020-09-29 19:32 ` bugzilla-daemon
2020-09-29 19:33 ` bugzilla-daemon
2020-10-12 18:30 ` bugzilla-daemon
2020-10-20 7:33 ` bugzilla-daemon
2020-11-01 16:20 ` bugzilla-daemon
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=bug-208891-208809-XxvmdBW11o@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@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).