From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Felipe Balbi <balbi@kernel.org>
Cc: linuxarm@huawei.com, mauro.chehab@huawei.com,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
John Stultz <john.stultz@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org
Subject: [PATCH 0/2] Add a quirk for dwc3 driver, requred for Hikey 970 USB to work
Date: Tue, 8 Sep 2020 09:20:55 +0200 [thread overview]
Message-ID: <cover.1599549364.git.mchehab+huawei@kernel.org> (raw)
This small patch series add a new quirk for the dwc3 driver. The first patch
was submitted previously to the USB mailing list:
https://patchwork.kernel.org/patch/10909965/
This quirk is also present at the official Linaro's tree for Hikey 970.
Without that, the URBs produced by the USB HID driver returns -EPROTO
errors, causing an endless reset loop, on every 0.5 seconds.
Please notice that I don't have any documentation about Synopsys
dwc3 driver. So, I tried my best to document this quirk at patch 2,
but I can't add anything more specifics, as I don't have any datasheets
from such IP.
Mauro Carvalho Chehab (1):
dt-bindings: document a new quirk for dwc3
Yu Chen (1):
usb: dwc3: Add splitdisable quirk for Hisilicon Kirin Soc
.../devicetree/bindings/usb/dwc3.txt | 3 +++
drivers/usb/dwc3/core.c | 25 +++++++++++++++++++
drivers/usb/dwc3/core.h | 7 ++++++
3 files changed, 35 insertions(+)
--
2.26.2
next reply other threads:[~2020-09-08 7:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 7:20 Mauro Carvalho Chehab [this message]
2020-09-08 7:20 ` [PATCH 2/2] dt-bindings: document a new quirk for dwc3 Mauro Carvalho Chehab
2020-09-15 16:38 ` Rob Herring
2020-09-17 7:18 ` Mauro Carvalho Chehab
2020-09-17 14:47 ` Rob Herring
2020-09-18 9:40 ` Mauro Carvalho Chehab
2020-09-29 6:09 ` Mauro Carvalho Chehab
2020-09-29 6:21 ` Felipe Balbi
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.1599549364.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mani@kernel.org \
--cc=mauro.chehab@huawei.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 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).