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: Mon, 25 Apr 2022 08:05:20 +0300 [thread overview]
Message-ID: <YmYsEARNTc99uwLt@lahna> (raw)
In-Reply-To: <76629b1698c129864b9853348f69520f19bd6b4c.camel@gmail.com>
On Fri, Apr 22, 2022 at 10:38:29PM +0200, Tomasz Moń wrote:
> On Fri, 2022-04-22 at 18:05 +0300, Mika Westerberg wrote:
> > On Fri, Apr 22, 2022 at 03:54:16PM +0200, Tomasz Moń wrote:
> > > On Fri, 2022-04-22 at 09:30 +0300, Mika Westerberg wrote:
> > > > 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.
> > >
> > > Passing "thunderbolt.start_icm=1" in the kernel command line made
> > > things worse. The system does not wake from suspend at all. It does not
> > > wake from USB keyboard connected directly to the host. And it does not
> > > wake after opening the lid nor after pressing power button (Touch ID).
> > >
> > > The only way to get system back running seemed to be pressing and
> > > holding power button long enough until the Apple bootloader starts.
> >
> > OK. The start_icm=1 starts the connection manager firmware which is one
> > thing that Windows relies too. However, all the PM stuff is still not
> > there unfortunately.
>
> Is the connection manager firmware interface (from Linux perspective)
> implementation specific or is it standarized?
Implementation specific. Apple does not use it on macOS at all and this
is the behaviour you get when you boot Linux there too (on bare metal).
However, with boot camp the firmware is started and the whole
environment (PM stuff) is made more standardized so that Windows can run
on it.
>
> > > > That should do the same than what the boot camp does and start the TBT firmware connection manager.
> > >
> > > I have no idea what boot camp does on the low level, but atleast
> > > Windows can wakeup successfully.
> >
> > please try the same in Linux if that's possible. Running Linux natively
> > will likely have issues because all the non-standard stuff in those
> > systems.
>
> What do you mean by trying the same in Linux? I would like to, but I
> simply don't know how.
I'm suggesting to boot linux on the boot camp too. I have no idea if
that is even posible but if it is then that would be the closest to get
similar behaviour between Windows on Apple and Linux.
prev parent reply other threads:[~2022-04-25 5:09 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
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 [this message]
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=YmYsEARNTc99uwLt@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;
as well as URLs for NNTP newsgroup(s).