mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: netdev@vger.kernel.org, linux-mips@vger.kernel.org,
	devicetree@vger.kernel.org, hkallweit1@gmail.com,
	kuba@kernel.org, conor+dt@kernel.org, lee@kernel.org,
	andrew+netdev@lunn.ch, davem@davemloft.net, pabeni@redhat.com,
	tsbogend@alpha.franken.de, linux@armlinux.org.uk,
	sander@svanheule.net, krzk+dt@kernel.org,
	markus.stockhausen@gmx.de, daniel@makrotopia.org,
	linux-kernel@vger.kernel.org, edumazet@google.com
Subject: Re: [PATCH net-next v6 2/6] dt-bindings: net: Add Realtek MDIO controller
Date: Tue, 4 Feb 2025 10:03:50 -0600	[thread overview]
Message-ID: <173868503036.2827831.5451264142133943992.robh@kernel.org> (raw)
In-Reply-To: <20250204030249.1965444-3-chris.packham@alliedtelesis.co.nz>


On Tue, 04 Feb 2025 16:02:45 +1300, Chris Packham wrote:
> Add dtschema for the MDIO controller found in the RTL9300 SoCs. The
> controller is slightly unusual in that direct MDIO communication is not
> possible. We model the MDIO controller with the MDIO buses as child
> nodes and the PHYs as children of the buses. The mapping of switch port
> number to MDIO bus/addr requires the ethernet-ports sibling to provide
> the mapping via the phy-handle property.
> 
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
> 
> Notes:
>     Changes in v6:
>     - Remove realtek,port property. The driver will parse the ethernet-ports
>       sibling node to figure out the mapping (do I need to mention that
>       somewhere in this binding?).
>     - Correct number of mdio buses. 4 possible buses numbered 0-3.
>     Changes in v5:
>     - Add back reg property to mdio-controller node
>     - Make unit address in the node name required
>     - Andrew suggested perhaps doing away with the realtek,port property and
>       providing the overall mapping via an array of phandles. I've explored
>       this a little, it is doable but I'm not sure it actually makes things
>       any clearer when the portmap has gaps so I haven't made this change.
>     Changes in v4:
>     - Model the MDIO controller with the buses as child nodes. We still need
>       to deal with the switch port number so this is represented with the
>       "realtek,port" property which needs to be added to the MDIO bus
>       children (i.e. the PHYs)
>     - Because the above is quite a departure from earlier I've dropped the
>       r-by
>     Changes in v3:
>     - Add r-by from Connor
>     Changes in v2:
>     - None
> 
>  .../bindings/net/realtek,rtl9301-mdio.yaml    | 86 +++++++++++++++++++
>  1 file changed, 86 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/net/realtek,rtl9301-mdio.yaml
> 

Reviewed-by: Rob Herring (Arm) <robh@kernel.org>


  reply	other threads:[~2025-02-04 16:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04  3:02 [PATCH net-next v6 0/6] RTL9300 MDIO driver Chris Packham
2025-02-04  3:02 ` [PATCH net-next v6 1/6] dt-bindings: mfd: Add switch to RTL9300 Chris Packham
2025-02-04  8:09   ` Krzysztof Kozlowski
2025-02-04 20:14     ` Chris Packham
2025-02-04 16:02   ` Rob Herring
2025-02-04  3:02 ` [PATCH net-next v6 2/6] dt-bindings: net: Add Realtek MDIO controller Chris Packham
2025-02-04 16:03   ` Rob Herring (Arm) [this message]
2025-02-04  3:02 ` [PATCH net-next v6 3/6] dt-bindings: mfd: Add MDIO interface to rtl9301-switch Chris Packham
2025-02-04  3:02 ` [PATCH net-next v6 4/6] net: mdio: Add RTL9300 MDIO driver Chris Packham
2025-02-09 14:19   ` Sander Vanheule
2025-02-11 21:06     ` Chris Packham
2025-02-04  3:02 ` [PATCH net-next v6 5/6] mips: dts: realtek: Add MDIO controller Chris Packham
2025-02-04  3:02 ` [PATCH net-next v6 6/6] mips: dts: cameo-rtl9302c: Add switch block Chris Packham

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=173868503036.2827831.5451264142133943992.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=conor+dt@kernel.org \
    --cc=daniel@makrotopia.org \
    --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=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=markus.stockhausen@gmx.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sander@svanheule.net \
    --cc=tsbogend@alpha.franken.de \
    /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

all inboxes | Powered by JetHome®