Devicetree
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "James Hilliard" <james.hilliard1@gmail.com>,
	"Lee Jones" <lee@kernel.org>, "Arnd Bergmann" <arnd@arndb.de>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Jagielski, Jedrzej" <jedrzej.jagielski@intel.com>,
	"Andre Przywara" <andre.przywara@arm.com>,
	"Chen-Yu Tsai" <wens@kernel.org>,
	"Jernej Škrabec" <jernej.skrabec@gmail.com>,
	linux-sunxi@lists.linux.dev, mfd@lists.linux.dev,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/2] dt-bindings: mfd: x-powers: Add AC200
Date: Thu, 13 Aug 2026 15:31:16 +0200	[thread overview]
Message-ID: <a11a5072-2477-41b6-8cc3-cb9aa75266cd@lunn.ch> (raw)
In-Reply-To: <20260813-independent-ladybug-of-perfection-1afe7a@quoll>

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

  parent reply	other threads:[~2026-08-13 13:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 23:11 [PATCH v7 0/2] mfd: add X-Powers AC200 support James Hilliard
2026-08-11 23:11 ` [PATCH v7 1/2] dt-bindings: mfd: x-powers: Add AC200 James Hilliard
2026-08-11 23:22   ` sashiko-bot
2026-08-13  6:49   ` Krzysztof Kozlowski
2026-08-13  6:58     ` James Hilliard
2026-08-13 13:31     ` Andrew Lunn [this message]
2026-08-11 23:11 ` [PATCH v7 2/2] mfd: ac200: Add X-Powers AC200 support James Hilliard
2026-08-11 23:18   ` sashiko-bot
2026-09-02 14:31   ` Lee Jones
2026-09-02 19:36     ` James Hilliard
2026-09-03  8:54       ` Lee Jones

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=a11a5072-2477-41b6-8cc3-cb9aa75266cd@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=andre.przywara@arm.com \
    --cc=arnd@arndb.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=james.hilliard1@gmail.com \
    --cc=jedrzej.jagielski@intel.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=mfd@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=wens@kernel.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