Re: Fwd: [PATCH] Add driver to force WMI Thunderbolt controller power status

From: "Bernat, Yehezkel" <yehezkel.bernat@intel.com>
To: "dvhart@infradead.org" <dvhart@infradead.org>,
	"Mario.Limonciello@dell.com" <Mario.Limonciello@dell.com>
Cc: "mika.westerberg@linux.intel.com"
	<mika.westerberg@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>,
	"hughsient@gmail.com" <hughsient@gmail.com>
Subject: Re: Fwd: [PATCH] Add driver to force WMI Thunderbolt controller power status
Date: Wed, 6 Sep 2017 20:26:39 +0000	[thread overview]
Message-ID: <1504729603.2677.167.camel@intel.com> (raw)
In-Reply-To: <20170906200953.GA8298@fury>

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.