From: Thinh Nguyen <thinh.nguyen@synopsys.com>
To: Felipe Balbi <balbi@kernel.org>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: John Youn <john.youn@synopsys.com>
Subject: [PATCH v6 0/3] usb: dwc3: Workaround isoc start_transfer failure
Date: Thu, 8 Nov 2018 12:06:41 -0800 [thread overview]
Message-ID: <cover.1541707248.git.thinhn@synopsys.com> (raw)
DWC_usb31 peripheral v1.70a-ea06 and prior needs a SW workaround for isoc START
TRANSFER command failure. This patch series implements that workaround
Change in v6:
- Defined more version types in "usb: dwc3: Track DWC_usb31 VERSIONTYPE"
- Minor cleanup/fix in "usb: dwc3: Add workaround for isoc start transfer failure"
Change in v5:
- Splitted and resent from an old patch series
- Cleanup and fixed review issues
Change in v4:
- None
Change in v3:
- None
Change in v2:
- None
Thinh Nguyen (3):
usb: dwc3: Track DWC_usb31 VERSIONTYPE
usb: dwc3: Add disabling of start_transfer failure quirk
usb: dwc3: Add workaround for isoc start transfer failure
Documentation/devicetree/bindings/usb/dwc3.txt | 3 +
drivers/usb/dwc3/core.c | 3 +
drivers/usb/dwc3/core.h | 23 +++++
drivers/usb/dwc3/gadget.c | 131 +++++++++++++++++++++++++
4 files changed, 160 insertions(+)
--
2.11.0
next reply other threads:[~2018-11-08 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 20:06 Thinh Nguyen [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-08 20:06 [v6,2/3] usb: dwc3: Add disabling of start_transfer failure quirk Thinh Nguyen
2018-11-08 20:06 ` [PATCH v6 2/3] " Thinh Nguyen
2018-11-11 22:32 [v6,2/3] " Rob Herring
2018-11-11 22:32 ` [PATCH v6 2/3] " Rob Herring
2018-11-14 11:41 [v6,2/3] " Felipe Balbi
2018-11-14 11:41 ` [PATCH v6 2/3] " Felipe Balbi
2018-11-15 7:00 [v6,2/3] " Thinh Nguyen
2018-11-15 7:00 ` [PATCH v6 2/3] " Thinh Nguyen
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=cover.1541707248.git.thinhn@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=john.youn@synopsys.com \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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 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.