Hi All,
What causes windows to set CM_DEVCAP_REMOVABLE on a PCIe device connected inside a thunderbolt device?
Details:
I’m working on a Thunderbolt 3 dock that has two USB xHCI host controllers with various USB devices inside it. Several of the captive USB devices are showing up in “Devices & Printers” instead of one nice dock device. I know for USB devices the solution to this is to mark the hub ports they are connected to as non-removable. That causes Windows to assign them the same ContainerID as their parents and lets the system know they are all in one physical box. I have already done that for the USB devices and they are grouped properly into two devices, one for each host controller, in Devices & Printers.
When I examined the device tree I found that the xHCI host controllers are marked as removable.
I examined the PCIe capability structures, specifically looking for an equivalent of non-removable port for PCIe. The closest I’ve found are the hot plug related bits in the Sloct Capabilities Register but when I examined the PCI-to-PCI Bridge that is the parent of the xHCI host controller, the hot plug bits aren’t set.
Any information would be much appreciated.
Eric