From: Krzysztof Kozlowski <krzk@kernel.org>
To: 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>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>
Cc: mfd@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v5 1/5] dt-bindings: mfd: x-powers: Add AC200
Date: Tue, 11 Aug 2026 09:07:13 +0200 [thread overview]
Message-ID: <ec826a71-bf33-44cc-80e0-dfc7e92ceb61@kernel.org> (raw)
In-Reply-To: <20260809-submit-acx00-of-dynamic-v1-v5-1-bfa1f8518b28@gmail.com>
On 09/08/2026 22:28, 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.
>
> The input clock must run at 24 or 27 MHz when the Ethernet PHY is used,
> matching the rates encoded by its documented clock selector.
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
I do not understand why MFD and net are combined. And nothing in top
part of cover letter explains me that (which I asked already - any
dependency or merging is THE MOST important information. Where do you
put the most important information which maintainers should see
immediately?)
Bundling it together suggests this is somehow incomplete and later will
be finished, which is wrong by itself. How to fix it - decouple
dependencies.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-11 7:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 20:28 [PATCH net-next v5 0/5] net: phy: add X-Powers AC200/AC300 EPHY support James Hilliard
2026-08-09 20:28 ` [PATCH net-next v5 1/5] dt-bindings: mfd: x-powers: Add AC200 James Hilliard
2026-08-11 7:07 ` Krzysztof Kozlowski [this message]
2026-08-11 7:23 ` James Hilliard
2026-08-11 7:27 ` Krzysztof Kozlowski
2026-08-11 16:50 ` Andrew Lunn
2026-08-09 20:28 ` [PATCH net-next v5 2/5] mfd: syscon: Add managed registration for external regmaps James Hilliard
2026-08-09 20:28 ` [PATCH net-next v5 3/5] mfd: ac200: Add X-Powers AC200 support James Hilliard
2026-08-09 20:28 ` [PATCH net-next v5 4/5] dt-bindings: net: x-powers: add AC200/AC300 EPHY packages James Hilliard
2026-08-11 7:15 ` Krzysztof Kozlowski
2026-08-09 20:28 ` [PATCH net-next v5 5/5] net: phy: add X-Powers AC200/AC300 EPHY driver James Hilliard
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=ec826a71-bf33-44cc-80e0-dfc7e92ceb61@kernel.org \
--to=krzk@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=james.hilliard1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mfd@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@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