From: martin.blumenstingl@googlemail.com (Martin Blumenstingl)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v2 0/2] Meson GXL USB3 PHY driver
Date: Sun, 28 Jan 2018 21:15:52 +0100 [thread overview]
Message-ID: <20180128201554.23889-1-martin.blumenstingl@googlemail.com> (raw)
Amlogic Meson GXL SoCs use a dwc3 controller with two USB2 ports,
Meson GXM SoCs use the same dwc3 controller but with three USB3
ports enabled. Neither of these SoCs has any USB3 port enabled in
the dwc3 registers.
The second USB2 port on both SoCs supports host and peripheral
(also called "device") mode.
The dwc3 controller supports host mode only. Peripheral mode is
implemented through an additional dwc2 controller (which only enables
device mode). The USB3 PHY has register bits which allow a driver to
detect the current mode - however this is currently not implemented
as the dwc2 controller seems to hang during reset (and I do not have
a use-case where I need peripheral/device mode).
While the dwc3 controller has no USB3 port enabled we still need the
USB3 PHY to be initialized, otherwise some boards (probably those where
the bootloader does not initialize the USB3 PHY) show errors with
high-speed USB devices connected to any of the USB2 ports. Configuring
the USB_R1_U3H_FLADJ_30MHZ_REG_MASK register as it's done by Amlogic's
vendor GPL kernel sources makes these error go away.
Thanks to Jerome Brunet for reporting the errors and Neil Armstrong
for discovering that initializing the USB3 PHY fixes these USB errors!
changes since v1 at [0]:
- document the interrupt in the dt-bindings patch (we don't use it in
the driver yet, but this interrupt is there so it should be
documented)
- added the clock and reset lines, thank to Yixun Lan who gave me the
hints that these are needed (it's not clear when reading the Amlogic
GPL kernel sources, because the clock for example is always enabled
by hardware default, bootrom, etc..)
- implemented the .set_mode callback
- NOTE: I chose *NOT* to add Jerome's and Neil's Tested-by's as well as
Rob's Acked-by on the dt-bindings patch since I made changes that I
want to have reviewed again
[0] http://lists.infradead.org/pipermail/linux-amlogic/2017-September/004780.html
Martin Blumenstingl (2):
dt-bindings: phy: Add support for the USB3 PHY on Amlogic Meson GXL
SoCs
phy: amlogic: add USB3 PHY support for Meson GXL and GXM
.../devicetree/bindings/phy/meson-gxl-usb3-phy.txt | 31 +++
drivers/phy/amlogic/Kconfig | 12 +
drivers/phy/amlogic/Makefile | 1 +
drivers/phy/amlogic/phy-meson-gxl-usb3.c | 288 +++++++++++++++++++++
4 files changed, 332 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/meson-gxl-usb3-phy.txt
create mode 100644 drivers/phy/amlogic/phy-meson-gxl-usb3.c
--
2.16.1
next reply other threads:[~2018-01-28 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 20:15 Martin Blumenstingl [this message]
2018-01-28 20:15 ` [PATCH v2 1/2] dt-bindings: phy: Add support for the USB3 PHY on Amlogic Meson GXL SoCs Martin Blumenstingl
2018-01-29 16:08 ` Rob Herring
2018-01-28 20:15 ` [PATCH v2 2/2] phy: amlogic: add USB3 PHY support for Meson GXL and GXM Martin Blumenstingl
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=20180128201554.23889-1-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=linus-amlogic@lists.infradead.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
all inboxes | Powered by JetHome®