public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Dejean <dam.dejean@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>, krzk@kernel.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] net: phy: realtek: add RTL8224 pair swap support
Date: Mon, 19 Jan 2026 18:54:21 +0100	[thread overview]
Message-ID: <0EE90427-54F7-40BF-81FF-B7DA76544338@gmail.com> (raw)
In-Reply-To: <bde1d3a9-6378-49a9-bcc2-00f4038f5558@lunn.ch>

Hi Andrew, Krzysztof,

Thanks for your feedbacks.

On 16 Jan 2026, at 19:10, Andrew Lunn <andrew@lunn.ch> wrote:
> 
> Does the PHY support auto MDI-X, where it figures out a working
> combination at link up time? That allows you to use crossed or not
> crossed cables.

It does support auto MDI-X, it’s possible to read the status of it after a cable is connected. However this is different from the swap mechanism I’m introducing here.

> 
> Anyway, the DT property you are adding seems to be the same as
> marvell,mdi-cfg-order. See commit:
> 
> 1432965bf5ce ("dt-bindings: net: marvell,aquantia: add property to override MDI_CFG")
> 
>> +  realtek,mdi-pair-swap:
> 
> Maybe call this realtek,mdi-cfg-order and use the same binding?

It looks like the same mechanism, thanks for the reference. The aquantia implementation looks more straightforward, let me rework the patchs to have a similar implementation.


> Changes to DT bindings should be in a patch of its own.

Thanks for the notice, I missed that when I ran checkpatch.

Damien


  reply	other threads:[~2026-01-19 17:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 17:39 [PATCH 1/2] net: phy: realtek: add RTL8224 pair swap support Damien Dejean
2026-01-16 17:39 ` [PATCH 2/2] net: phy: realtek: add RTL8224 polarity " Damien Dejean
2026-01-17 10:47   ` Krzysztof Kozlowski
2026-01-16 18:10 ` [PATCH 1/2] net: phy: realtek: add RTL8224 pair " Andrew Lunn
2026-01-19 17:54   ` Damien Dejean [this message]
2026-01-17 10:47 ` Krzysztof Kozlowski

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=0EE90427-54F7-40BF-81FF-B7DA76544338@gmail.com \
    --to=dam.dejean@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=krzk@kernel.org \
    --cc=netdev@vger.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