From: sashiko-bot@kernel.org
To: "James Hilliard" <james.hilliard1@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
mfd@lists.linux.dev, lee@kernel.org
Subject: Re: [PATCH net-next v4 3/4] dt-bindings: net: x-powers: add AC200/AC300 EPHY packages
Date: Sat, 08 Aug 2026 04:52:05 +0000 [thread overview]
Message-ID: <20260808045206.3B7EC1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260806-submit-acx00-of-dynamic-v1-v4-3-9bf2f7441632@gmail.com>
> The AC200 and AC300 contain compatible Fast Ethernet link PHYs which
> report the same Clause 22 identifier and use the same link-side register
> layout. Their package control paths differ: AC200 uses registers in its
> I2C MFD, while the AC300 control range is at a second Clause 22 address
> fixed at 16 plus the link address.
>
> Describe both variants as Ethernet PHY packages. The package reg value is
> the link PHY base address and the child supplies the documented PHY ID,
> because the identification registers cannot be read until package setup
> has completed. The AC300 driver reaches its control range with the PHY
> package offset helpers. The AC200 package instead references its MFD.
>
> Give fixed hardware variant-specific compatibles. Also provide an ACx00
> compatible for systems which can contain either package, with one packed
> NVMEM field containing calibration in bits 3 through 0, the AC300 selector
> in bit 8 and its low-calibration selector in bit 9. Such a description
> contains the potential resources for both backends; the driver consumes
> only those selected by the configuration field.
>
> Describe the package clock, supply and optional xMII receive-clock
> inversion needed by some integrations. A fixed AC200 package may omit the
> NVMEM field and use its internal calibration copy. Limit AC300-capable link
> addresses to 0 through 7 so the control address remains in the documented
> range 16 through 23.
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260806-submit-acx00-of-dynamic-v1-v4-0-9bf2f7441632@gmail.com?part=3
next prev parent reply other threads:[~2026-08-08 4:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 4:51 [PATCH net-next v4 0/4] net: phy: add X-Powers AC200/AC300 EPHY support James Hilliard
2026-08-07 4:51 ` [PATCH net-next v4 1/4] dt-bindings: mfd: x-powers: Add AC200 James Hilliard
2026-08-08 4:52 ` sashiko-bot
2026-08-09 15:34 ` Andrew Lunn
2026-08-09 19:33 ` James Hilliard
2026-08-09 20:48 ` Andrew Lunn
2026-08-07 4:51 ` [PATCH net-next v4 2/4] mfd: ac200: Add X-Powers AC200 support James Hilliard
2026-08-08 4:52 ` sashiko-bot
2026-08-07 4:51 ` [PATCH net-next v4 3/4] dt-bindings: net: x-powers: add AC200/AC300 EPHY packages James Hilliard
2026-08-08 4:52 ` sashiko-bot [this message]
2026-08-07 4:51 ` [PATCH net-next v4 4/4] net: phy: add X-Powers AC200/AC300 EPHY driver James Hilliard
2026-08-08 4:52 ` sashiko-bot
2026-08-09 15:50 ` Andrew Lunn
2026-08-09 20:29 ` 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=20260808045206.3B7EC1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=james.hilliard1@gmail.com \
--cc=lee@kernel.org \
--cc=mfd@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.