From: Mathias Nyman <mathias.nyman@intel.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Lars_Chang@asmedia.com.tw, USB list <linux-usb@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Tsai, Nicholas" <nicholas.tsai@amd.com>,
Nehal Shah <Nehal-bakulchandra.Shah@amd.com>,
Ramkumar Subramaniyan <ramkumar.ks@amd.com>
Subject: Re: [PATCH] Revert "xhci: Limit USB2 port wake support for AMD Promontory hosts"
Date: Mon, 18 Sep 2017 11:06:29 +0300 [thread overview]
Message-ID: <59BF7E85.7050001@intel.com> (raw)
In-Reply-To: <CAAd53p52VOAso5oYLL85gi5EBLR6eZsG3tYHH4Yrza8-CmsaDg@mail.gmail.com>
On 16.09.2017 07:49, Kai-Heng Feng wrote:
> On Mon, Aug 28, 2017 at 9:56 PM, Kai-Heng Feng
> <kai.heng.feng@canonical.com> wrote:
>> On Mon, Aug 28, 2017 at 6:14 PM, Mathias Nyman
>> <mathias.nyman@linux.intel.com> 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
prev parent reply other threads:[~2017-09-18 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 9:14 Kai-Heng Feng
2017-08-28 9:29 ` Greg KH
2017-08-28 10:14 ` Mathias Nyman
2017-08-29 4:56 ` Kai-Heng Feng
2017-09-16 4:49 ` Kai-Heng Feng
2017-09-18 8:06 ` Mathias Nyman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59BF7E85.7050001@intel.com \
--to=mathias.nyman@intel.com \
--cc=Lars_Chang@asmedia.com.tw \
--cc=Nehal-bakulchandra.Shah@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=nicholas.tsai@amd.com \
--cc=ramkumar.ks@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome