[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5f56b21575dd4f64a3b46aac21151667@realtek.com>
Date: Fri, 1 Oct 2021 03:26:48 +0000
From: Hayes Wang <hayeswang@...ltek.com>
To: Alan Stern <stern@...land.harvard.edu>,
Oliver Neukum <oneukum@...e.com>
CC: Jason-ch Chen <jason-ch.chen@...iatek.com>,
"matthias.bgg@...il.com" <matthias.bgg@...il.com>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-mediatek@...ts.infradead.org"
<linux-mediatek@...ts.infradead.org>,
"Project_Global_Chrome_Upstream_Group@...iatek.com"
<Project_Global_Chrome_Upstream_Group@...iatek.com>,
"hsinyi@...gle.com" <hsinyi@...gle.com>,
nic_swsd <nic_swsd@...ltek.com>
Subject: RE: [PATCH] r8152: stop submitting rx for -EPROTO
> Alan Stern <stern@...land.harvard.edu>
> [...]
> > There has been some discussion about this in the past.
> >
> > In general, -EPROTO is almost always a non-recoverable error.
>
> Excuse me. I am confused about the above description.
> I got -EPROTO before, when I debugged another issue.
> However, the bulk transfer still worked after I resubmitted
> the transfer. I didn't do anything to recover it. That is why
> I do resubmission for -EPROTO.
I check the Linux driver and the xHCI spec.
The driver gets -EPROTO for bulk transfer, when the host
returns COMP_USB_TRANSACTION_ERROR.
According to the spec of xHCI, USB TRANSACTION ERROR
means the host did not receive a valid response from the
device (Timeout, CRC, Bad PID, unexpected NYET, etc.).
It seems to be reasonable why resubmission sometimes works.
Best Regards,
Hayes
Powered by blists - more mailing lists