From: <Mario.Limonciello@dell.com>
To: <yehezkel.bernat@intel.com>, <dvhart@infradead.org>
Cc: <mika.westerberg@linux.intel.com>, <linux-kernel@vger.kernel.org>,
<platform-driver-x86@vger.kernel.org>, <hughsient@gmail.com>
Subject: RE: Fwd: [PATCH] Add driver to force WMI Thunderbolt controller power status
Date: Wed, 6 Sep 2017 21:40:02 +0000 [thread overview]
Message-ID: <7edd73cbe3ba4d7b80a6614e93f4d538@ausx13mpc120.AMER.DELL.COM> (raw)
In-Reply-To: <1504729603.2677.167.camel@intel.com>
> -----Original Message-----
> From: Bernat, Yehezkel [mailto:yehezkel.bernat@intel.com]
> Sent: Wednesday, September 6, 2017 3:27 PM
> To: dvhart@infradead.org; Limonciello, Mario <Mario_Limonciello@Dell.com>
> Cc: mika.westerberg@linux.intel.com; linux-kernel@vger.kernel.org; platform-
> driver-x86@vger.kernel.org; hughsient@gmail.com
> Subject: Re: Fwd: [PATCH] Add driver to force WMI Thunderbolt controller power
> status
>
> On Wed, 2017-09-06 at 13:09 -0700, Darren Hart wrote:
> > The other question I had about this was if the typical use case
> > involves the OS,
> > or if the firmware update (for example) would be performed as part of
> > the
> > general platform firmware update (from the UEFI update utility).
>
> First, there is the use-case of add-in card, where it's impossible to
> use UEFI-based update, as much as I understand, as the BIOS isn't
> expected to expose an ESRT entry for it.
>
> Even for built-in controller, my impression is that most OEMs use a FW
> update application (running on Windows) and are not publishing a UEFI-
> based solution.
Yeah I'd agree with that impression.
Even if an OEM does choose to publish a UEFI based solution, it's still
useful to present FW information for the TBT controller in fwupd however too.
Similar to how fwupd displays the information for the ME even though
the ME is typically updated via UEFI.
next prev parent reply other threads:[~2017-09-06 21:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 17:54 [PATCH] Add driver to force WMI Thunderbolt controller power status Mario Limonciello
[not found] ` <CA+CmpXt9EtzObijHT3gmm=xUwFDF3Ec=SFbNnPAk+oRdzAUADQ@mail.gmail.com>
2017-09-06 19:40 ` Fwd: " Bernat, Yehezkel
2017-09-06 19:46 ` Bernat, Yehezkel
2017-09-06 19:49 ` Fwd: " Mario.Limonciello
2017-09-06 20:09 ` Darren Hart
2017-09-06 20:26 ` Bernat, Yehezkel
2017-09-06 21:40 ` Mario.Limonciello [this message]
2017-09-06 22:27 ` Darren Hart
2017-09-06 22:34 ` Bernat, Yehezkel
2017-09-07 1:38 ` Mario.Limonciello
2017-09-06 21:43 ` Mario.Limonciello
2017-09-07 6:36 ` Mika Westerberg
2017-09-07 6:50 ` Mika Westerberg
2017-09-07 18:47 ` 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=7edd73cbe3ba4d7b80a6614e93f4d538@ausx13mpc120.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=dvhart@infradead.org \
--cc=hughsient@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=yehezkel.bernat@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).