From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Paul Zimmerman <Paul.Zimmerman@synopsys.com>,
Felipe Balbi <balbi@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nick Hudson <skrll@netbsd.org>,
linux-usb@vger.kernel.org
Cc: linux@roeck-us.net, dianders@chromium.org, hminas@synopsys.com,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] usb: dwc2: Fixes and improvements
Date: Wed, 13 Jan 2021 12:20:48 +0100 [thread overview]
Message-ID: <20210113112052.17063-1-nsaenzjulienne@suse.de> (raw)
I'm picking up this series by Guenter Roeck as he stated he has no time
for it ATM. It was found to solve some unaligned DMA access issues on
Raspberry Pi 3. You can find the original discussion here:
https://lore.kernel.org/linux-usb/20200226210414.28133-1-linux@roeck-us.net/
I removed the fist patch from the original series as it turned out to be
contententious and needs more in-depth testing. Following is the edited
origin series description. Note that extra testing was performed on
RPi3:
"This series addresses the following problems:
- Fix receive transfers with 0 byte transfer length
- Abort transactions after unknown receive errors
if the receive buffer is full
- Reduce "trimming xfer length" logging noise
The problems fixed with this series were observed when connecting
a DM9600 Ethernet adapter to Veyron Chromebooks such as the ASUS
Chromebook C201PA. The series was tested extensively with this and
other adapters.
The observed problems are also reported when tethering various
phones, so test coverage with such phones would be very appreciated."
---
Guenter Roeck (3):
usb: dwc2: Do not update data length if it is 0 on inbound transfers
usb: dwc2: Abort transaction after errors with unknown reason
usb: dwc2: Make "trimming xfer length" a debug message
drivers/usb/dwc2/hcd.c | 15 ++++++++-------
drivers/usb/dwc2/hcd_intr.c | 14 +++++++++++++-
2 files changed, 21 insertions(+), 8 deletions(-)
--
2.29.2
next reply other threads:[~2021-01-13 11:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 11:20 Nicolas Saenz Julienne [this message]
2021-01-13 11:20 ` [PATCH 1/3] usb: dwc2: Do not update data length if it is 0 on inbound transfers Nicolas Saenz Julienne
2021-01-13 11:20 ` [PATCH 2/3] usb: dwc2: Abort transaction after errors with unknown reason Nicolas Saenz Julienne
2021-01-13 11:20 ` [PATCH 3/3] usb: dwc2: Make "trimming xfer length" a debug message Nicolas Saenz Julienne
2021-01-13 23:20 ` [PATCH 0/3] usb: dwc2: Fixes and improvements Doug Anderson
2021-01-14 3:07 ` Guenter Roeck
2021-01-14 9:26 ` Nicolas Saenz Julienne
2021-01-14 16:29 ` Guenter Roeck
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=20210113112052.17063-1-nsaenzjulienne@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=Paul.Zimmerman@synopsys.com \
--cc=balbi@ti.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=hminas@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=skrll@netbsd.org \
/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;
as well as URLs for NNTP newsgroup(s).