From: Ladislav Michl <oss-lists@triops.cz>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Liang He <windhl@126.com>
Cc: linux-mips@vger.kernel.org, linux-usb@vger.kernel.org
Subject: [PATCH v2 0/3] Cleanup Octeon DWC3 glue code
Date: Sun, 2 Jul 2023 02:15:05 +0200 [thread overview]
Message-ID: <ZKDBiY6TKdDKIFK+@lenoch> (raw)
Hi,
primary motivation was to fix issue Id 29206 as described in
OCTEON III CN70XX/CN71XX Known Issues, version: 1.9.
Said document is marked as Marvell Proprietary and Confidential,
therefore I'm not sure if I can cite from it.
This probably does not matter too much as the root of the information
listed there is a workaround being implemented in OCTEON SDK 3.1.2
patch 7 and later in
u-boot/drivers/usb/host/xhci-octeon.c:dwc3_uphy_pll_reset()
My coleague ported that patch to linux-4.9 and I will later modify
it to work on top of current glue driver.
The glue code currently lives in arch/mips/cavium-octeon/octeon-usb.c
and loops for each "cavium,octeon-7130-usb-uctl" compatible.
However there is no bond with dwc3 core code, so if anything goes
wrong in glue code, the loop breaks, leaving dwc3 in reset.
Later on when dwc3 core tries to read any device register, bus error
is emited, leading to kernel panic.
Therefore move it to drivers/usb/dwc3 while making it glue driver.
This is a second attempt, see changelog appended to patches.
Ladislav Michl (3):
usb: dwc3: dwc3-octeon: Convert to glue driver
usb: dwc3: dwc3-octeon: Move node parsing into driver probe
usb: dwc3: Add SPDX header and copyright
arch/mips/cavium-octeon/Makefile | 1 -
arch/mips/cavium-octeon/octeon-platform.c | 1 -
drivers/usb/dwc3/Kconfig | 10 +
drivers/usb/dwc3/Makefile | 1 +
.../usb/dwc3/dwc3-octeon.c | 262 +++++++++---------
drivers/usb/dwc3/dwc3-of-simple.c | 1 -
6 files changed, 142 insertions(+), 134 deletions(-)
rename arch/mips/cavium-octeon/octeon-usb.c => drivers/usb/dwc3/dwc3-octeon.c (80%)
--
2.39.2
next reply other threads:[~2023-07-02 0:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 0:15 Ladislav Michl [this message]
2023-07-02 0:16 ` [PATCH v2 1/3] usb: dwc3: dwc3-octeon: Convert to glue driver Ladislav Michl
2023-07-05 23:25 ` Thinh Nguyen
2023-07-13 21:33 ` Ladislav Michl
2023-07-14 0:37 ` Thinh Nguyen
2023-07-02 0:16 ` [PATCH v2 2/3] usb: dwc3: dwc3-octeon: Move node parsing into driver probe Ladislav Michl
2023-07-05 23:08 ` Thinh Nguyen
2023-07-13 21:37 ` Ladislav Michl
2023-07-14 0:42 ` Thinh Nguyen
2023-07-02 0:17 ` [PATCH v2 3/3] usb: dwc3: Add SPDX header and copyright Ladislav Michl
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=ZKDBiY6TKdDKIFK+@lenoch \
--to=oss-lists@triops.cz \
--cc=Thinh.Nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=windhl@126.com \
/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).