Re: [PATCH v7 1/2] dt-bindings: mfd: x-powers: Add AC200

Andrew Lunn <[email protected]>
Newsgroups dev.linux.lists.mfd,dev.linux.lists.linux-sunxi,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
On Thu, Aug 13, 2026 at 08:49:33AM +0200, Krzysztof Kozlowski wrote:
> On Tue, Aug 11, 2026 at 05:11:30PM -0600, James Hilliard wrote:
> > The AC200 is an I2C-controlled mixed-signal companion IC containing
> > audio, video, RTC and Fast Ethernet PHY functions.
> > 
> > Describe the parent device and its shared input clock. The Ethernet PHY
> > is represented by a PHY package on its MDIO bus, with a phandle back to
> > this device for access to the package control registers, so it does not
> > require an MFD child node. Function-specific supplies belong to their
> > consumer bindings rather than the shared parent.
> 
> Other way to represent it is to put ethernet phy here - either as a
> child or folded into MFD device node - and provide phandle to MDIO bus.

That would be odd. IEEE 802.3 specified that the PHY should be on an
MDIO bus. And this PHY is on an MDIO bus, that is its primary
management interface. I2C is just for ancillary configuration.

The only kind of sort of an exception we have in the current MDIO
subsystem is for SFP modules. They only have an I2C bus, not
MDIO. However, SFP vendors have various protocols for MDIO over
I2C. So the SFP does appear in the I2C tree, but we then instantiate
an MDIO bus as an I2C client, and then the PHY is then just a normal
PHY on an emulated MDIO bus.

	Andrew
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.