From: Ran Wang <ran.wang_1@nxp.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Felipe Balbi <balbi@kernel.org>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ran Wang <ran.wang_1@nxp.com>
Subject: [PATCH 0/2] usb: dwc3: Add avoiding vbus glitch happen during xhci reset
Date: Wed, 16 Jan 2019 06:48:03 +0000 [thread overview]
Message-ID: <20190116064820.20007-1-ran.wang_1@nxp.com> (raw)
This to fix USB enumeration compatibility issue found on DWC3 (host mode)
IP only.
Some pre-discussion mails can be referred from:
https://lkml.org/lkml/2018/11/23/387
https://lkml.org/lkml/2018/11/22/683
As to the workaround, I know programming xhci register in DWC3 dirver
(probe function) is not good from perspective of SW stack, but it seems
to be the only place to fix this real existing problem (test result show
that doing this in xhci-plat.c or xhci.c would not hlep on this kind of
failure). If who have better idea, please let me know, thanks in advanced.
Ran Wang (2):
dt-bindings: Add workaround for host mode VBUS glitch when boot
dwc3 core driver: Add avoiding vbus glitch happen during xhci reset
Documentation/devicetree/bindings/usb/dwc3.txt | 3 +++
drivers/usb/dwc3/core.c | 47 +++++++++++++++++++++++++++++++++++++++++++++++
drivers/usb/dwc3/core.h | 10 +++++++++-
3 files changed, 60 insertions(+), 0 deletions(-)
--
1.7.1
next reply other threads:[~2019-01-16 6:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 6:48 Ran Wang [this message]
2019-01-16 6:48 ` [PATCH 1/2] usb: dwc3: Add avoiding vbus glitch happen during xhci reset Ran Wang
2019-01-16 7:05 ` Ran Wang
2019-01-22 1:03 ` Rob Herring
2019-01-22 2:38 ` Ran Wang
2019-01-22 13:45 ` Rob Herring
2019-01-16 6:48 ` [PATCH 2/2] usb: dwc3: Add workaround for host mode VBUS glitch when boot Ran Wang
2019-01-16 8:21 ` Felipe Balbi
2019-01-16 13:11 ` kbuild test robot
2019-02-15 8:39 ` Ran Wang
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=20190116064820.20007-1-ran.wang_1@nxp.com \
--to=ran.wang_1@nxp.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).