Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752533AbdIRICv (ORCPT ); Mon, 18 Sep 2017 04:02:51 -0400 Received: from mga04.intel.com ([192.55.52.120]:33357 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752468AbdIRICt (ORCPT ); Mon, 18 Sep 2017 04:02:49 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,411,1500966000"; d="scan'208";a="1220197650" Subject: Re: [PATCH] Revert "xhci: Limit USB2 port wake support for AMD Promontory hosts" To: Kai-Heng Feng , Mathias Nyman References: <20170822091447.19126-1-kai.heng.feng@canonical.com> <20170828092959.GA24193@kroah.com> <59A3ECF2.8050406@linux.intel.com> Cc: Greg KH , Lars_Chang@asmedia.com.tw, USB list , LKML , "Tsai, Nicholas" , Nehal Shah , Ramkumar Subramaniyan From: Mathias Nyman Message-ID: <59BF7E85.7050001@intel.com> Date: Mon, 18 Sep 2017 11:06:29 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1329 Lines: 37 On 16.09.2017 07:49, Kai-Heng Feng wrote: > On Mon, Aug 28, 2017 at 9:56 PM, Kai-Heng Feng > wrote: >> On Mon, Aug 28, 2017 at 6:14 PM, Mathias Nyman >> wrote: >>> On 28.08.2017 12:29, Greg KH wrote: >>> >>> Adding more people who were involved in the original patch. >>> >>> Users are now seeing the unresponsive USB2 ports with Promontory hosts. >>> Is there any update on a better way to solve the original issue. >>> >>> To me a "dead" USB2 port seems like a much worse issue for a user >>> than a BIOS disabled port waking up on plug/unplug (wake on >>> connect/disconnect), >>> so I'm myself in favor of doing this revert. >> >> At least I can't find "Disable USB2" on my ASUS PRIME B350M-A, so the >> new behavior is quite surprising. >> >>> >>> But there was a strong push from Promontory developers to get the original >>> fix in, >>> and I would like to get some comment from them before I do anything about >>> it. >> >> You looped them to the mail thread which I reported the regression two >> weeks ago, and there is no response since then... > > Still no response from AMD and ASMedia guys. > > I don't like to use out-of-tree patches for myself, but probably it's > the only way here? I'll revert it and send it forward now since rc1 is out -Mathias