Re: [PATCH 00/21] net: phy: add X-Powers AC200/AC300 EPHY support
Andrew Lunn <[email protected]> Mon, 3 Aug 2026 15:01:31 +0200
| Newsgroups | org.infradead.lists.linux-rockchip,dev.linux.lists.linux-sunxi,dev.linux.lists.mfd,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel,org.kernel.vger.netdev |
|---|---|
| Message-ID | <[email protected]> |
On Sun, Aug 02, 2026 at 11:14:10PM -0600, James Hilliard wrote: > The Allwinner H616/H618 secondary EMAC is commonly connected to a Fast > Ethernet PHY in an X-Powers AC200 or AC300 companion package. The two > packages expose the same link PHY ID and largely compatible link-side > registers, but require different control paths before those registers can > be accessed: AC200 is initialized through its I2C MFD, while AC300 uses a > non-PHY Clause 22 control endpoint. > > Some H616-family products were shipped with either package under the same > board identity. For those systems, this series uses a SID NVMEM field to > select the control provider at run time. With CONFIG_OF_DYNAMIC, the link > PHY enables only the selected fail-needs-probe provider, so an AC300 board > does not probe the unused AC200 I2C controller or claim its pins. The same > drivers also support fixed descriptions without CONFIG_OF_DYNAMIC: a board > can reference one enabled provider, or enable both candidates when runtime > selection is still required. > > The series adds: > > - the H616 EMAC1 binding, stmmac variant and controller node; > - generic MDIO OF reconfiguration support for PHYs, packages, scanned > addresses and generic MDIO devices; > - the AC200 MFD and AC200/AC300 EPHY control providers; > - the shared AC200/AC300 link-PHY driver, including calibration, power and > reset sequencing, MDI/MDI-X, statistics, EDPD, PHY-managed EEE, package > LEDs, interrupts and Wake-on-LAN; and > - H6 and H616-family device-tree descriptions and arm64 defconfig support. > > The AC200 and AC300 control and link paths were exercised on H616-family > hardware during development, including link traffic, address handling, > ethtool EDPD/EEE controls, statistics and LEDs. The H6 interrupt and > Wake-on-LAN description still needs validation by an H6 hardware user. > > This series depends on Richard Genoud's v7 H616 PWM controller series, > which provides the bypass clock used by the companion EPHY: > > https://lore.kernel.org/all/[email protected]/ > > The PWM patches are an external prerequisite and are intentionally not > included in this 21-patch series. 21 patches is on the big side. Now you have shown the big picture, can you break this up into a couple of series? Andrew _______________________________________________ Linux-rockchip mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-rockchip