From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Tomasz Moń" <desowin@gmail.com>
Cc: linux-usb@vger.kernel.org,
Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>
Subject: Re: Wake from Thunderbolt dock doesn't work
Date: Fri, 22 Apr 2022 09:30:27 +0300 [thread overview]
Message-ID: <YmJLg3maiAY6cwDp@lahna> (raw)
In-Reply-To: <CAOHtt38-+tnyrUX5u0McHyutofEwZLeLF7siZab7XgLYXVdm9Q@mail.gmail.com>
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@linux.intel.com> 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 :(
next prev parent reply other threads:[~2022-04-22 6:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 19:52 Wake from Thunderbolt dock doesn't work Tomasz Moń
2022-04-22 5:26 ` Mika Westerberg
2022-04-22 6:09 ` Tomasz Moń
2022-04-22 6:30 ` Mika Westerberg [this message]
2022-04-22 13:54 ` Tomasz Moń
2022-04-22 15:05 ` Mika Westerberg
2022-04-22 20:38 ` Tomasz Moń
2022-04-25 5:05 ` 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=YmJLg3maiAY6cwDp@lahna \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=desowin@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
/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