Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752788AbcD1Sth (ORCPT ); Thu, 28 Apr 2016 14:49:37 -0400 Received: from ausxipps301.us.dell.com ([143.166.148.223]:49431 "EHLO ausxipps301.us.dell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751824AbcD1Stf (ORCPT ); Thu, 28 Apr 2016 14:49:35 -0400 DomainKey-Signature: s=smtpout; d=dell.com; c=nofws; q=dns; h=X-LoopCount0:X-IronPort-AV:From:To:CC:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader:x-originating-ip: Content-Type:Content-Transfer-Encoding:MIME-Version: Return-Path; b=aHLqwPI5XncK/HFG1Z1ADqLOoTSdNf2L1i9HK5PCTbN3bNFO6ssUiwTK 4QHVG0m/Ro8eQRlRmsD8kdWWxROQvYEEBoQvn3RjKv14YXGuHZmUl3hrG DMh9HxuKsOK7/uaP2VNdvPW/WmXdBFrknnuSp9VQc3dF+EJmg3DqvENt8 Y=; X-LoopCount0: from 10.175.216.249 X-IronPort-AV: E=Sophos;i="5.24,547,1454997600"; d="scan'208";a="787561006" From: To: CC: , , , , , , , , , Subject: RE: [PATCH] ACPI: fix Thunderbolt hotplug Thread-Topic: [PATCH] ACPI: fix Thunderbolt hotplug Thread-Index: AQHRoIAcY8zYiJa73E+qWv+AEDyDd5+gDTWA//+sdaCAAFXDAP//rFww Date: Thu, 28 Apr 2016 18:49:20 +0000 Message-ID: <8f963a18fb384f0e89e0d069d8416abf@ausx13mpc120.AMER.DELL.COM> References: <1461760019-12930-1-git-send-email-prarit@redhat.com> <0502496faa2f494a8d81e4789fa2a77e@ausx13mpc120.AMER.DELL.COM> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.208.89.195] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id u3SIngSW029952 Content-Length: 2855 Lines: 69 > -----Original Message----- > From: Andy Lutomirski [mailto:luto@amacapital.net] > Sent: Thursday, April 28, 2016 1:47 PM > To: Limonciello, Mario > Cc: Andrew Lutomirski ; Prarit Bhargava > ; linux-kernel@vger.kernel.org; Robert Moore > ; Lv Zheng ; Rafael J. > Wysocki ; Len Brown ; Linux > ACPI ; stable ; > devel@acpica.org > Subject: Re: [PATCH] ACPI: fix Thunderbolt hotplug > > On Thu, Apr 28, 2016 at 11:44 AM, wrote: > > > > > >> -----Original Message----- > >> From: Andy Lutomirski [mailto:luto@kernel.org] > >> Sent: Thursday, April 28, 2016 1:39 PM > >> To: Prarit Bhargava ; linux-kernel@vger.kernel.org > >> Cc: Robert Moore ; Lv Zheng > >> ; Rafael J. Wysocki ; > >> Len Brown ; linux-acpi@vger.kernel.org; Limonciello, > >> Mario ; stable@vger.kernel.org; > >> devel@acpica.org > >> Subject: Re: [PATCH] ACPI: fix Thunderbolt hotplug > >> > >> On 04/27/2016 05:26 AM, Prarit Bhargava wrote: > >> > Rafael, this patch is in the acpica.git tree as 7a3bd2d ("Dispatcher: > >> > Update thread ID for recursive method calls"). I've had many > >> > positive testing results from hardware vendors and users with this > >> > patch and this resolves many of the problems seen here: > >> > > >> > https://bugzilla.kernel.org/show_bug.cgi?id=115121 > >> > > >> > This does not fix the problems with the TB docking station. > >> > Although this patch will also be required, the docking station > >> > issues require a FW > >> update. > >> > Updated FW should be coming soon to resolve those problems. > >> > > >> > >> No kidding!?! Will that update be installable from Linux? If so, > >> could you cc me on that? > >> > > > > > > This patch does let the dock hotplug properly after the BIOS fix is applied. > > > > For the dock devices not showing up on the other side of the thunderbolt > bridge: > > It's going to be a system firmware update for both the XPS 9350 and > Precision 5510. It will get distributed to LVFS and can be loaded up with > fwupd/fwupdate. > > I don't yet have an ETA that I can share other than "Next BIOS release" > > > > After the update, set Thunderbolt Security to "No Security" and devices > should be available. > > Great! > > Does this mean that I won't need to boot into Windows and run the little > Intel tool to update the Alpine Ridge firmware? I.e. will the LVFS / EFI > executable do that part? > Unfortunately that's a separate problem. Working towards a few different solutions on that too, but nothing to share right now.