From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>, Ding Hui <dinghui@sangfor.com.cn>
Cc: mathias.nyman@intel.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xhci: Always restore EP_SOFT_CLEAR_TOGGLE even if ep reset failed
Date: Fri, 21 Aug 2020 11:44:34 +0300 [thread overview]
Message-ID: <c6275105-a204-fe23-2dae-2bfa6c06a839@linux.intel.com> (raw)
In-Reply-To: <20200821073147.GA1681156@kroah.com>
On 21.8.2020 10.31, Greg KH wrote:
> On Fri, Aug 21, 2020 at 03:06:52PM +0800, Ding Hui wrote:
>> Some devices driver call libusb_clear_halt when target ep queue
>> is not empty. (eg. spice client connected to qemu for usb redir)
>>
>> Before commit f5249461b504 ("xhci: Clear the host side toggle
>> manually when endpoint is soft reset"), that works well.
>> But now, we got the error log:
>>
>> EP not empty, refuse reset
>>
>> xhch_endpoint_reset failed and left ep_state's EP_SOFT_CLEAR_TOGGLE
>> bit is still on
>>
>> So all the subsequent urb sumbit to the ep will fail with the
>> warn log:
>>
>> Can't enqueue URB while manually clearing toggle
>>
>> We need restore ep_state EP_SOFT_CLEAR_TOGGLE bit after
>> xhci_endpoint_reset, even if it is failed.
>>
>> Signed-off-by: Ding Hui <dinghui@sangfor.com.cn>
Thanks, nice catch.
>> ---
>> drivers/usb/host/xhci.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> Shouldn't this have a Fixes: tag on it and be backported to the affected
> stable trees?
It should, but I like this patch and want it in, so I'll add the tags this time.
Thanks
-Mathias
next prev parent reply other threads:[~2020-08-21 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 7:06 [PATCH] xhci: Always restore EP_SOFT_CLEAR_TOGGLE even if ep reset failed Ding Hui
2020-08-21 7:31 ` Greg KH
2020-08-21 8:44 ` Mathias Nyman [this message]
2020-08-21 23:58 ` Ding Hui
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=c6275105-a204-fe23-2dae-2bfa6c06a839@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=dinghui@sangfor.com.cn \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.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