On Fri, Apr 22, 2022 at 08:09:23AM +0200, Tomasz Moń wrote: > On Fri, Apr 22, 2022 at 7:27 AM Mika Westerberg > <mika.westerberg@xxxxxxxxxxxxxxx> wrote: > > On Thu, Apr 21, 2022 at 09:52:18PM +0200, Tomasz Moń wrote: > > > I have observed that when I suspend to RAM, I cannot wakeup the host > > > (MacBook Pro 2019) with my low-speed USB keyboard (Microsoft Comfort > > > Curve Keyboard 2000) connected to Thunderbolt 3 dock (CalDigit USB-C > > > Pro Dock). > > > > > > The host runs on Intel Core i9-9980HK and lspci shows Intel Corporation > > > JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] and Intel Corporation > > > DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]. > > > > > > On Windows and Mac OS the system can be successfully woken up by > > > pressing key on keyboard connected via the dock. > > > > Is the system that has the problem an Apple system or a regular PC? > > It is an Apple system (MacBook Pro 2019) as noted in in first > paragraph. All tests were performed on the same host with the same > equipment. OK, I see. I was bit confused because you mention that it works in Windows. I guess you run the Windows on boot camp or so? If that's the case then you should be getting same kind of "support" by passing "thunderbolt.start_icm=1" in the kernel command line. That should do the same than what the boot camp does and start the TBT firmware connection manager. Apple systems by default have the firmware connection manager disabled so the OS does all the tunneling and in Linux we do not support Thunderbolt 3 hosts fully in the software connection manager side (we do support devices, though). Mostly it's the power management that is missing and I don't see it being fully supported in the future either because the Apple systems are not like the most standardized systems in the market so there are lots of "magic" things happening that are completely undocumented :(
