public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Dejean <dam.dejean@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: andrew@lunn.ch, krzk+dt@kernel.org, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	edumazet@google.com, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, hkallweit1@gmail.com
Subject: Re: [PATCH v2 3/4] dt-bindings: net: realtek,rtl82xx: add a property to set MDI polarity
Date: Thu, 22 Jan 2026 21:47:23 +0100	[thread overview]
Message-ID: <916AA508-4097-42DF-8087-4C82ABB87D76@gmail.com> (raw)
In-Reply-To: <20260122165102.GA2564919-robh@kernel.org>


> Le 22 janv. 2026 à 17:51, Rob Herring <robh@kernel.org> a écrit :
> 
> However, are these properties something that should be common?

If by common you mean « not Realtek specific » I have no idea if this kind of mapping is possible on other chips. Marvell Aquantia phys have an « order » (marvell,mdi-cfg-order) property like the one I introduced in the patch before this one (thanks Andrew), but that’s all I know.



  reply	other threads:[~2026-01-22 20:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21 15:15 [PATCH v2 1/4] dt-bindings: net: realtek,rtl82xx: add a property to set MDI order Damien Dejean
2026-01-21 15:15 ` [PATCH v2 2/4] net: phy: realtek: add RTL8224 pair order support Damien Dejean
2026-01-22 15:15   ` kernel test robot
2026-01-22 17:39   ` kernel test robot
2026-01-21 15:15 ` [PATCH v2 3/4] dt-bindings: net: realtek,rtl82xx: add a property to set MDI polarity Damien Dejean
2026-01-22 16:51   ` Rob Herring
2026-01-22 20:47     ` Damien Dejean [this message]
2026-01-22 23:06       ` Rob Herring
2026-01-21 15:15 ` [PATCH v2 4/4] net: phy: realtek: add RTL8224 polarity support Damien Dejean
2026-01-22 18:41   ` kernel test robot
2026-01-22 22:12   ` kernel test robot

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=916AA508-4097-42DF-8087-4C82ABB87D76@gmail.com \
    --to=dam.dejean@gmail.com \
    --cc=andrew@lunn.ch \
    --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