From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751348AbdIPEtP (ORCPT ); Sat, 16 Sep 2017 00:49:15 -0400 Received: from youngberry.canonical.com ([91.189.89.112]:40662 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751066AbdIPEtN (ORCPT ); Sat, 16 Sep 2017 00:49:13 -0400 X-Google-Smtp-Source: AOwi7QDV48m6sPgxU/ZObI4ecxz5IY2ZRTmD/VwSJ/DESJGy/KLUudeirBbmEz/GbMTI1I6JuJFrtf0kQJGrBx4LNYc= MIME-Version: 1.0 In-Reply-To: References: <20170822091447.19126-1-kai.heng.feng@canonical.com> <20170828092959.GA24193@kroah.com> <59A3ECF2.8050406@linux.intel.com> From: Kai-Heng Feng Date: Fri, 15 Sep 2017 21:49:11 -0700 Message-ID: Subject: Re: [PATCH] Revert "xhci: Limit USB2 port wake support for AMD Promontory hosts" To: Mathias Nyman Cc: Greg KH , mathias.nyman@intel.com, Lars_Chang@asmedia.com.tw, USB list , LKML , "Tsai, Nicholas" , Nehal Shah , Ramkumar Subramaniyan Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? > >> >> Thanks >> -Mathias >>