From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mario Limonciello <mario.limonciello@dell.com>
Cc: dvhart@infradead.org, LKML <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org,
Richard Hughes <hughsient@gmail.com>,
Yehezkel Bernat <yehezkelshb@gmail.com>
Subject: Re: [PATCH v3] Add driver to force WMI Thunderbolt controller power status
Date: Sat, 9 Sep 2017 10:09:29 +0300 [thread overview]
Message-ID: <20170909070929.GH2477@lahna.fi.intel.com> (raw)
In-Reply-To: <1504884191-16528-1-git-send-email-mario.limonciello@dell.com>
On Fri, Sep 08, 2017 at 10:23:11AM -0500, Mario Limonciello wrote:
> Current implementations of Intel Thunderbolt controllers will go
> into a low power mode when not in use.
>
> Many machines containing these controllers also have a GPIO wired up
> that can force the controller awake. This is offered via a ACPI-WMI
> interface intended to be manipulated by a userspace utility.
>
> This mechanism is provided by Intel to OEMs to include in BIOS.
> It uses an industry wide GUID that is populated in a separate _WDG
> entry with no binary MOF.
>
> This interface allows software such as fwupd to wake up thunderbolt
> controllers to query the firmware version or flash new firmware.
>
> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2017-09-09 7:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 15:23 [PATCH v3] Add driver to force WMI Thunderbolt controller power status Mario Limonciello
2017-09-09 7:09 ` Mika Westerberg [this message]
2017-09-09 18:39 ` Yehezkel Bernat
2017-09-11 21:44 ` Darren Hart
2017-09-12 19:19 ` Mario.Limonciello
2017-09-13 17:20 ` Lukas Wunner
2017-09-14 6:42 ` Mario.Limonciello
2017-09-14 9:14 ` Lukas Wunner
2017-09-14 14:52 ` Mario.Limonciello
2017-09-14 14:59 ` Mika Westerberg
2017-09-14 15:05 ` Mika Westerberg
2017-09-15 7:44 ` Lukas Wunner
2017-09-15 16:34 ` Mario.Limonciello
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=20170909070929.GH2477@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=hughsient@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=yehezkelshb@gmail.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