[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130703184434.GA29587@srcf.ucam.org>
Date: Wed, 3 Jul 2013 19:44:34 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Yinghai Lu <yinghai@...nel.org>, john.ronciak@...el.com,
miles.j.penner@...el.com, bruce.w.allan@...el.com,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
linux-pci@...r.kernel.org, x86@...nel.org
Subject: Re: [PATCH v2 0/8] Thunderbolt workarounds
On Wed, Jul 03, 2013 at 11:33:11AM -0700, Greg Kroah-Hartman wrote:
> On Wed, Jul 03, 2013 at 07:29:00PM +0100, Matthew Garrett wrote:
> > Are there any plans to provide native support for the Thunderbolt
> > controller, rather than relying on system management mode?
>
> For what specific hardware platform? For the ones that this patchset
> controls, the OS doesn't have access to the Thunderbolt controller as
> far as I can tell, it all happens through the ACPI and PCI hotplug
> interface.
Given that there exist platforms without the SMM implementation, there's
presumably either a controller or chipset register that controls whether
SMIs are generated in response to Thunderbolt events.
--
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists