From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Damien Dejean <dam.dejean@gmail.com>,
andrew@lunn.ch, krzk+dt@kernel.org, robh@kernel.org,
kuba@kernel.org
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, edumazet@google.com,
davem@davemloft.net, pabeni@redhat.com, hkallweit1@gmail.com
Subject: Re: [PATCH v5 1/4] dt-bindings: net: ethernet-phy: add property enet-phy-lane-order
Date: Tue, 3 Feb 2026 10:09:49 +0100 [thread overview]
Message-ID: <75c590f9-aa08-4b8d-8dbf-422273012c74@bootlin.com> (raw)
In-Reply-To: <20260202200411.373161-1-dam.dejean@gmail.com>
Hi,
On 02/02/2026 21:04, Damien Dejean wrote:
> Add property enet-phy-lane-order to the device tree bindings to define
> the lane order of the PHY. To simplify PCB design some manufacturers
> allow to wire the pairs in a reverse order, and change the order in
> software.
>
> The property can be set to 0 to force the normal lane order (ABCD), or 1
> to force the reverse lane order (DCBA).
>
> Signed-off-by: Damien Dejean <dam.dejean@gmail.com>
> ---
> Documentation/devicetree/bindings/net/ethernet-phy.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/ethernet-phy.yaml b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
> index 58634fee9fc4..8347d4e134d2 100644
> --- a/Documentation/devicetree/bindings/net/ethernet-phy.yaml
> +++ b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
> @@ -126,6 +126,12 @@ properties:
> e.g. wrong bootstrap configuration caused by issues in PCB
> layout design.
>
> + enet-phy-lane-order:
As this is specific to BaseT, maybe rename that "enet-phy-pair-order" ?
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [0, 1]
> + description:
> + For normal (0) or reverse (1) order of the pairs (ABCD -> DCBA).
We now have a binding in DT for ethernet-connectors, and I'd says this
is typically the kind of info I'd put in there :
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/tree/Documentation/devicetree/bindings/net/ethernet-connector.yaml
The way you'd use that is by adding a ".attach_mdi_port()" callback in your
phy driver, and in there you'd parse these properties and do the proper settings.
We're missing a few things, such as storing a ref to the of_node corresponding
to the connector into phy_port.
This is brand new though, maybe Maintainers would like for phy_port to stabilize
before building more on top of it ?
Maxime
prev parent reply other threads:[~2026-02-03 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 20:04 [PATCH v5 1/4] dt-bindings: net: ethernet-phy: add property enet-phy-lane-order Damien Dejean
2026-02-02 20:04 ` [PATCH v5 2/4] net: phy: realtek: add RTL8224 pair order support Damien Dejean
2026-02-02 20:04 ` [PATCH v5 3/4] dt-bindings: net: ethernet-phy: add property enet-phy-lane-polarity Damien Dejean
2026-02-02 20:04 ` [PATCH v5 4/4] net: phy: realtek: add RTL8224 polarity support Damien Dejean
2026-02-03 9:09 ` Maxime Chevallier [this message]
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=75c590f9-aa08-4b8d-8dbf-422273012c74@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=andrew@lunn.ch \
--cc=dam.dejean@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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