[PATCH 0/6] ZTE zx297520v3 USB support
From: Stefan Dösinger
Date: Fri Nov 20 2026 - 14:21:18 EST
Hi,
This series expands the device tree and drivers for the zx297520v3 board
enough to enable the DWC2 USB controller found on this board. This
series depends on the zx29clk MFD driver that has been accepted into the
MFD tree, but not yet merged into linux-next.
The individual patches contain a description of what they do and the
rationale for design decisions. Here is a quick overview:
Patch 1: DT bindings for the node containing the necessary power controls
Patch 2: Add the socsys node to the MFD driver
Patch 3: The power domain driver
Patch 4: A minimal USB PHY driver
Patch 5, 6: Link it together in the DTS
Dependencies: 1-4-5 depend on each other at build / DTS validation time.
2, 3, 4 are build time independent but need their previous patches to be
enabled at runtime.
The MAINTAINERS additions are going to cause issues though. Once the
patches have been reviewed I can either take them out or create an
immutable branch.
The open questions:
1) How much documentation is appropriate in the binding .yaml?
I want to document the identified registers *somewhere*, and since the
yaml lives in Documentation/ I put it there. I do understand though if
the Linux kernel doesn't want to be a backup SoC datasheet.
2) Power domain vs reset:
The pm domain controller has a reset, isolation and power register for
each of the 5 (maybe more) devices it controls. My binding links them
together into #power-domain-cells.
To start up the GSM controller, its driver will have to assert and
deassert the reset. The GSM controller (Derived from an Infineon
PMB8877) has a self-arming watchdog and after 2.5 ms it stops
responding. With the power domain it is somewhat awkward:
devm_pm_runtime_set_active_enabled()
pm_runtime_get_noresume()
pm_runtime_put_sync_suspend()
pm_runtime_resume_and_get()
And hope nothing else is holding the device and that runtime PM is
actually compiled into the kernel.
Life would be easier if I expose the GSM reset bits as #reset-cells.
Otoh, I'd prefer not to do that for USB, as USB already has 3 different
reset controls already and adding another is awkward. I could of course
also hide the USB reset and expose the GSM resets.
For now I postponed the issue and don't add GSM related controls to the
bindings at all.
---
Stefan Dösinger (6):
dt-bindings: soc: zte: Document zx297520v3 socsys controller
mfd: zx297520v3: Add socsys to the mfd host driver
pmdomain: zte: Add a zx297520v3 power domain driver
phy: zte: Add a zx29 USB PHY driver.
ARM: dts: zte: Declare nodes to enable the board's dwc2 controller
ARM: dts: zte: Declare the HSIC controller node
.../bindings/soc/zte/zte,zx297520v3-socsys.yaml | 100 +++++++
MAINTAINERS | 3 +
arch/arm/boot/dts/zte/zx297520v3.dtsi | 42 +++
drivers/mfd/zte-zx297520v3-crm.c | 12 +
drivers/phy/Kconfig | 11 +
drivers/phy/Makefile | 1 +
drivers/phy/phy-zx29-usb.c | 183 +++++++++++++
drivers/pmdomain/Kconfig | 1 +
drivers/pmdomain/Makefile | 1 +
drivers/pmdomain/zte/Kconfig | 15 ++
drivers/pmdomain/zte/Makefile | 2 +
drivers/pmdomain/zte/zx297520v3-pm-domain.c | 286 +++++++++++++++++++++
include/dt-bindings/power/zte,zx297520v3-socsys.h | 11 +
include/dt-bindings/reset/zte,zx297520v3-reset.h | 2 +
14 files changed, 670 insertions(+)
---
base-commit: d785d132202e8e8e93335ebf74ad5b29fca0951f
change-id: 20261117-zx29usb-c3a90ab59354
prerequisite-change-id: 20261108-zx29clk-3b073b9d22d6:v14
prerequisite-patch-id: 3ea4ed11578625d6aadf59c5b542e788882eab2f
Best regards,
--
Stefan Dösinger <stefandoesinger@xxxxxxxxx>