All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hayes Wang <hayeswang@realtek.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Neukum <oneukum@suse.com>,
	Jason-ch Chen <jason-ch.chen@mediatek.com>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-mediatek@lists.infradead.org" 
	<linux-mediatek@lists.infradead.org>,
	"Project_Global_Chrome_Upstream_Group@mediatek.com" 
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"hsinyi@google.com" <hsinyi@google.com>,
	nic_swsd <nic_swsd@realtek.com>
Subject: RE: [PATCH] r8152: stop submitting rx for -EPROTO
Date: Mon, 4 Oct 2021 02:15:44 +0000	[thread overview]
Message-ID: <21b97638ece04b4fbd81d29143b72137@realtek.com> (raw)
In-Reply-To: <20211001152226.GA505557@rowland.harvard.edu>

Alan Stern <stern@rowland.harvard.edu>
> Sent: Friday, October 1, 2021 11:22 PM
[...]
> That's right.  If the device and cable are working properly, this
> should never happen.  Or only extremely rarely (for example, caused
> by external electromagnetic interference).
> 
> > It seems to be reasonable why resubmission sometimes works.
> 
> Did you ever track down the reason why you got the -EPROTO error
> while debugging that other issue?  Can you reproduce it?

I didn't follow it, because it was not relative to the driver. Besides, we
didn't focus on -EPROTO at that time, because it was not the major issue.
And the -EPROTO occurred rarely indeed during a lot of transmission.
The hw engineer confirmed that the device completed the transfer
normally, but the driver still got an error from the host. I don't sure if
there was a USB HUB between the device and the USB host controller.
That are all what I know.

Best Regards,
Hayes


WARNING: multiple messages have this Message-ID (diff)
From: Hayes Wang <hayeswang@realtek.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Neukum <oneukum@suse.com>,
	Jason-ch Chen <jason-ch.chen@mediatek.com>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"Project_Global_Chrome_Upstream_Group@mediatek.com"
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"hsinyi@google.com" <hsinyi@google.com>,
	nic_swsd <nic_swsd@realtek.com>
Subject: RE: [PATCH] r8152: stop submitting rx for -EPROTO
Date: Mon, 4 Oct 2021 02:15:44 +0000	[thread overview]
Message-ID: <21b97638ece04b4fbd81d29143b72137@realtek.com> (raw)
In-Reply-To: <20211001152226.GA505557@rowland.harvard.edu>

Alan Stern <stern@rowland.harvard.edu>
> Sent: Friday, October 1, 2021 11:22 PM
[...]
> That's right.  If the device and cable are working properly, this
> should never happen.  Or only extremely rarely (for example, caused
> by external electromagnetic interference).
> 
> > It seems to be reasonable why resubmission sometimes works.
> 
> Did you ever track down the reason why you got the -EPROTO error
> while debugging that other issue?  Can you reproduce it?

I didn't follow it, because it was not relative to the driver. Besides, we
didn't focus on -EPROTO at that time, because it was not the major issue.
And the -EPROTO occurred rarely indeed during a lot of transmission.
The hw engineer confirmed that the device completed the transfer
normally, but the driver still got an error from the host. I don't sure if
there was a USB HUB between the device and the USB host controller.
That are all what I know.

Best Regards,
Hayes


_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Hayes Wang <hayeswang@realtek.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Neukum <oneukum@suse.com>,
	Jason-ch Chen <jason-ch.chen@mediatek.com>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"Project_Global_Chrome_Upstream_Group@mediatek.com"
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"hsinyi@google.com" <hsinyi@google.com>,
	nic_swsd <nic_swsd@realtek.com>
Subject: RE: [PATCH] r8152: stop submitting rx for -EPROTO
Date: Mon, 4 Oct 2021 02:15:44 +0000	[thread overview]
Message-ID: <21b97638ece04b4fbd81d29143b72137@realtek.com> (raw)
In-Reply-To: <20211001152226.GA505557@rowland.harvard.edu>

Alan Stern <stern@rowland.harvard.edu>
> Sent: Friday, October 1, 2021 11:22 PM
[...]
> That's right.  If the device and cable are working properly, this
> should never happen.  Or only extremely rarely (for example, caused
> by external electromagnetic interference).
> 
> > It seems to be reasonable why resubmission sometimes works.
> 
> Did you ever track down the reason why you got the -EPROTO error
> while debugging that other issue?  Can you reproduce it?

I didn't follow it, because it was not relative to the driver. Besides, we
didn't focus on -EPROTO at that time, because it was not the major issue.
And the -EPROTO occurred rarely indeed during a lot of transmission.
The hw engineer confirmed that the device completed the transfer
normally, but the driver still got an error from the host. I don't sure if
there was a USB HUB between the device and the USB host controller.
That are all what I know.

Best Regards,
Hayes


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-10-04  2:16 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29  5:18 [PATCH] r8152: stop submitting rx for -EPROTO Jason-ch Chen
2021-09-29  5:18 ` Jason-ch Chen
2021-09-29  5:18 ` Jason-ch Chen
2021-09-29  8:14 ` Hayes Wang
2021-09-29  8:14   ` Hayes Wang
2021-09-29  8:14   ` Hayes Wang
2021-09-29  9:52   ` Jason-ch Chen
2021-09-29  9:52     ` Jason-ch Chen
2021-09-29  9:52     ` Jason-ch Chen
2021-09-30  2:41     ` Hayes Wang
2021-09-30  2:41       ` Hayes Wang
2021-09-30  2:41       ` Hayes Wang
2021-10-01  1:36       ` Jason-ch Chen
2021-10-01  1:36         ` Jason-ch Chen
2021-10-01  1:36         ` Jason-ch Chen
2021-09-30  9:30     ` Oliver Neukum
2021-09-30  9:30       ` Oliver Neukum
2021-09-30  9:30       ` Oliver Neukum
2021-09-30 15:18       ` Alan Stern
2021-09-30 15:18         ` Alan Stern
2021-09-30 15:18         ` Alan Stern
2021-10-01  2:40         ` Hayes Wang
2021-10-01  2:40           ` Hayes Wang
2021-10-01  2:40           ` Hayes Wang
2021-10-01  3:26           ` Hayes Wang
2021-10-01  3:26             ` Hayes Wang
2021-10-01  3:26             ` Hayes Wang
2021-10-01 15:22             ` Alan Stern
2021-10-01 15:22               ` Alan Stern
2021-10-01 15:22               ` Alan Stern
2021-10-04  2:15               ` Hayes Wang [this message]
2021-10-04  2:15                 ` Hayes Wang
2021-10-04  2:15                 ` Hayes Wang
2021-10-04 11:44               ` Oliver Neukum
2021-10-04 11:44                 ` Oliver Neukum
2021-10-04 11:44                 ` Oliver Neukum
2021-10-04 14:33                 ` Alan Stern
2021-10-04 14:33                   ` Alan Stern
2021-10-04 14:33                   ` Alan Stern
2021-09-30 16:13       ` Hayes Wang
2021-09-30 16:13         ` Hayes Wang
2021-09-30 16:13         ` Hayes Wang
2021-10-04  6:28 ` [PATCH net] r8152: avoid to resubmit rx immediately Hayes Wang
2021-10-05 11:50   ` patchwork-bot+netdevbpf

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=21b97638ece04b4fbd81d29143b72137@realtek.com \
    --to=hayeswang@realtek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=hsinyi@google.com \
    --cc=jason-ch.chen@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=oneukum@suse.com \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.