From: "Hawkins, Nick" <nick.hawkins@hpe.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Verdun, Jean-Marie" <verdun@hpe.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v1 3/5] dt-bindings: net: Add HPE GXP UMAC
Date: Tue, 25 Jul 2023 13:44:30 +0000 [thread overview]
Message-ID: <DM4PR84MB192785EC6F2B8A76FF9E5E3F8803A@DM4PR84MB1927.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <57d882ed-82e5-4584-8126-ca2007064126@lunn.ch>
Hi Andrew,
Thank you for the feedback.
> > +examples:
> > + - |
> > + ethernet@4000 {
> > + compatible = "hpe,gxp-umac";
> > + reg = <0x4000 0x80>;
> > + interrupts = <22>;
> > + mac-address = [00 00 00 00 00 00]; /* Filled in by U-Boot */
> Do both ports get the sane MAC address?
No they do not. The first one will get the MAC address, the second
will be an external phy we are managing via the MDIO path.
> > + ethernet-ports {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + port@0 {
> > + reg = <0>;
> > + phy-handle = <ð_phy0>;
> > + };
> > +
> > + port@1 {
> > + reg = <1>;
> > + phy-handle = <ð_phy1>;
> > + };
> > + };
> > +
> > + mdio {
> This seems to be wrong. You have a standalone MDIO bus driver, not
> part of the MAC address space?
I based this from other yaml examples I found. Is there a better way to
represent it?
Here is what I plan on having the dts/dtsi
look like:
mdio0: mdio@4080 {
compatible = "hpe,gxp-umac-mdio";
reg = <0x4080 0x10>;
#address-cells = <1>;
#size-cells = <0>;
ext_phy0: ethernt-phy@0 {
compatible = "marvell,88e1415","ethernet-phy-ieee802.3-c22";
phy-mode = "sgmii";
reg = <0>;
};
};
mdio1: mdio@5080 {
compatible = "hpe,gxp-umac-mdio";
reg = <0x5080 0x10>;
#address-cells = <1>;
#size-cells = <0>;
int_phy0: ethernt-phy@0 {
compatible = "ethernet-phy-ieee802.3-c22";
phy-mode = "gmii";
reg = <0>;
};
int_phy1: ethernt-phy@1 {
compatible = "ethernet-phy-ieee802.3-c22";
phy-mode = "gmii";
reg = <1>;
};
};
umac0: ethernet@4000 {
compatible = "hpe,gxp-umac";
reg = <0x4000 0x80>;
interrupts = <10>;
interrupt-parent = <&vic0>;
mac-address = [00 00 00 00 00 00];
ethernet-ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
phy-handle = <&int_phy0>;
};
port@1 {
reg = <1>;
phy-handle = <&ext_phy0>;
};
};
};
Thank you for the help and assistance.
-Nick Hawkins
next prev parent reply other threads:[~2023-07-25 13:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 21:20 [PATCH v1 0/5] ARM: Add GXP UMAC Support nick.hawkins
2023-07-21 21:20 ` [PATCH v1 1/5] dt-bindings: net: Add HPE GXP UMAC MDIO nick.hawkins
2023-07-24 17:33 ` Conor Dooley
2023-07-21 21:20 ` [PATCH v1 2/5] net: hpe: Add " nick.hawkins
2023-07-21 21:39 ` Christophe JAILLET
2023-07-21 21:57 ` Andrew Lunn
2023-07-24 14:41 ` Simon Horman
2023-07-21 21:20 ` [PATCH v1 3/5] dt-bindings: net: Add HPE GXP UMAC nick.hawkins
2023-07-21 22:01 ` Andrew Lunn
2023-07-25 13:44 ` Hawkins, Nick [this message]
2023-07-25 17:51 ` Andrew Lunn
[not found] ` <DM4PR84MB19274F3AA411D4CAE7EE84D88803A@DM4PR84MB1927.NAMPRD84.PROD.OUTLOOK.COM>
2023-07-26 14:43 ` Hawkins, Nick
2023-07-26 15:56 ` Andrew Lunn
2023-07-24 16:20 ` Rob Herring
2023-07-21 21:20 ` [PATCH v1 4/5] net: hpe: Add GXP UMAC Driver nick.hawkins
2023-07-21 22:00 ` Christophe JAILLET
2023-07-21 22:29 ` Andrew Lunn
2023-07-24 15:01 ` Simon Horman
2023-07-21 21:20 ` [PATCH v1 5/5] MAINTAINERS: HPE: Add GXP UMAC Networking Files nick.hawkins
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=DM4PR84MB192785EC6F2B8A76FF9E5E3F8803A@DM4PR84MB1927.NAMPRD84.PROD.OUTLOOK.COM \
--to=nick.hawkins@hpe.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=verdun@hpe.com \
/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®