From: Christian Marangi <ansuelsmth@gmail.com>
To: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Philipp Zabel <p.zabel@pengutronix.de>,
Christian Marangi <ansuelsmth@gmail.com>,
Daniel Golle <daniel@makrotopia.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: [net-next PATCH v3 07/11] dt-bindings: net: ethernet-controller: permit to define multiple PCS
Date: Sat, 10 May 2025 12:23:27 +0200 [thread overview]
Message-ID: <20250510102348.14134-8-ansuelsmth@gmail.com> (raw)
In-Reply-To: <20250510102348.14134-1-ansuelsmth@gmail.com>
Drop the limitation of a single PCS in pcs-handle property. Multiple PCS
can be defined for an ethrnet-controller node to support various PHY
interface mode type.
It's very common for SoCs to have a 2 or more dedicated PCS for Base-X
(for example SGMII, 1000base-x, 2500base-x, ...) and Base-R (for example
USXGMII,10base-r, ...) with the MAC selecting one of the other based on
the attached PHY.
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
---
Documentation/devicetree/bindings/net/ethernet-controller.yaml | 2 --
1 file changed, 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/net/ethernet-controller.yaml b/Documentation/devicetree/bindings/net/ethernet-controller.yaml
index 7cbf11bbe99c..60605b34d242 100644
--- a/Documentation/devicetree/bindings/net/ethernet-controller.yaml
+++ b/Documentation/devicetree/bindings/net/ethernet-controller.yaml
@@ -84,8 +84,6 @@ properties:
pcs-handle:
$ref: /schemas/types.yaml#/definitions/phandle-array
- items:
- maxItems: 1
description:
Specifies a reference to a node representing a PCS PHY device on a MDIO
bus to link with an external PHY (phy-handle) if exists.
--
2.48.1
next prev parent reply other threads:[~2025-05-10 10:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-10 10:23 [net-next PATCH v3 00/11] net: pcs: Introduce support for fwnode PCS Christian Marangi
2025-05-10 10:23 ` [net-next PATCH v3 01/11] net: phylink: keep and use MAC supported_interfaces in phylink struct Christian Marangi
2025-05-10 10:23 ` [net-next PATCH v3 02/11] net: phy: introduce phy_interface_copy helper Christian Marangi
2025-05-10 10:23 ` [net-next PATCH v3 03/11] net: phylink: introduce internal phylink PCS handling Christian Marangi
2025-05-10 10:23 ` [net-next PATCH v3 04/11] net: phylink: add phylink_release_pcs() to externally release a PCS Christian Marangi
2025-05-10 10:23 ` [net-next PATCH v3 05/11] net: pcs: implement Firmware node support for PCS driver Christian Marangi
2025-05-10 10:23 ` [net-next PATCH v3 06/11] net: phylink: support late PCS provider attach Christian Marangi
2025-05-10 10:23 ` Christian Marangi [this message]
2025-05-10 10:23 ` [net-next PATCH v3 08/11] net: phylink: add .pcs_link_down PCS OP Christian Marangi
2025-05-10 10:23 ` [net-next PATCH v3 09/11] net: pcs: airoha: add PCS driver for Airoha SoC Christian Marangi
2025-05-10 10:23 ` [net-next PATCH v3 10/11] dt-bindings: net: pcs: Document support for Airoha Ethernet PCS Christian Marangi
2025-05-10 10:23 ` [net-next PATCH v3 11/11] net: airoha: add phylink support for GDM2/3/4 Christian Marangi
2025-05-10 12:23 ` Lorenzo Bianconi
2025-05-10 17:26 ` 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=20250510102348.14134-8-ansuelsmth@gmail.com \
--to=ansuelsmth@gmail.com \
--cc=andrew+netdev@lunn.ch \
--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=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).