[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230816215220.114118-4-nick.hawkins@hpe.com>
Date: Wed, 16 Aug 2023 16:52:18 -0500
From: nick.hawkins@....com
To: christophe.jaillet@...adoo.fr, simon.horman@...igine.com,
andrew@...n.ch, verdun@....com, nick.hawkins@....com,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
netdev@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH v3 3/5] dt-bindings: net: Add HPE GXP UMAC
From: Nick Hawkins <nick.hawkins@....com>
Provide access to the register regions and interrupt for Universal
MAC(UMAC). The driver under the hpe,gxp-umac binding will provide an
interface for sending and receiving networking data from both of the
UMACs on the system.
Signed-off-by: Nick Hawkins <nick.hawkins@....com>
---
v3:
*Remove MDIO references
*Modify description for use-ncsi
v2:
*Move mac-addresses into ports
*Remove | where not needed
---
.../devicetree/bindings/net/hpe,gxp-umac.yaml | 97 +++++++++++++++++++
1 file changed, 97 insertions(+)
create mode 100644 Documentation/devicetree/bindings/net/hpe,gxp-umac.yaml
diff --git a/Documentation/devicetree/bindings/net/hpe,gxp-umac.yaml b/Documentation/devicetree/bindings/net/hpe,gxp-umac.yaml
new file mode 100644
index 000000000000..d3f72694c814
--- /dev/null
+++ b/Documentation/devicetree/bindings/net/hpe,gxp-umac.yaml
@@ -0,0 +1,97 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/net/hpe,gxp-umac.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: HPE GXP Unified MAC Controller
+
+maintainers:
+ - Nick Hawkins <nick.hawkins@....com>
+
+description:
+ HPE GXP 802.3 10/100/1000T Ethernet Unifed MAC controller.
+ Device node of the controller has following properties.
+
+properties:
+ compatible:
+ const: hpe,gxp-umac
+
+ use-ncsi:
+ type: boolean
+ description:
+ Indicates if the device should use NCSI (Network Controlled
+ Sideband Interface). Only one of the two MACs can support
+ NCSI and it requires there to be a physical connection on
+ the board to be present. This property indicates that
+ physical connection is present and should be used.
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ maxItems: 1
+
+ ethernet-ports:
+ type: object
+ additionalProperties: false
+ description: Ethernet ports to PHY
+
+ properties:
+ "#address-cells":
+ const: 1
+
+ "#size-cells":
+ const: 0
+
+ patternProperties:
+ "^port@[0-1]$":
+ type: object
+ additionalProperties: false
+ description: Port to PHY
+
+ properties:
+ reg:
+ minimum: 0
+ maximum: 1
+
+ phy-handle:
+ maxItems: 1
+
+ mac-address: true
+
+ required:
+ - reg
+ - phy-handle
+
+additionalProperties: false
+
+required:
+ - compatible
+ - reg
+ - interrupts
+ - ethernet-ports
+
+examples:
+ - |
+ ethernet@...0 {
+ compatible = "hpe,gxp-umac";
+ reg = <0x4000 0x80>;
+ interrupts = <22>;
+ ethernet-ports {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ port@0 {
+ reg = <0>;
+ phy-handle = <&int_phy0>;
+ mac-address = [00 00 00 00 00 00];
+ };
+
+ port@1 {
+ reg = <1>;
+ phy-handle = <&ext_phy1>;
+ mac-address = [00 00 00 00 00 00];
+ };
+ };
+ };
--
2.17.1
Powered by blists - more mailing lists