From: Andrew Lunn <andrew@lunn.ch>
To: Dror Alon <adror@iai.co.il>
Cc: "'netdev@vger.kernel.org'" <netdev@vger.kernel.org>,
Efter Yoram <yefter@iai.co.il>,
Alayev Michael <malayev@iai.co.il>
Subject: Re: DTS for our Configuration
Date: Fri, 16 Mar 2018 16:12:06 +0100 [thread overview]
Message-ID: <20180316151206.GG17895@lunn.ch> (raw)
In-Reply-To: <3988EA6F088014488BE41D19253A7EE40152236E92@EXS10.iai.co.il>
On Thu, Mar 15, 2018 at 02:00:00PM +0000, Dror Alon wrote:
> Hello Andrew,
> Thanks for your fast responses.
> Michael and I keep trying to configure our linux Zynq7000 board.
> We can't succeed with configure our SWITCHES via the DTS file.
> Please. See the next diagram, and please Do you have any DTS Sample
> for this Setup ?
Hi Dror
I'm surprised you are doing SGMII between ports 10. They are 10G
capable.
gem0: {
fixed-link {
speed = <1000>;
full-duplex;
};
phy0: phy@0: {
reg = <0>;
};
switch0: switch@1c: {
compatible = "marvell,mv88e6190";
reg = <0x1c>;
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
label = "cpu";
fixed-link {
speed = <1000>;
full-duplex;
};
port@1 {
reg = <1>;
label = "lan0";
};
port@2 {
reg = <2>;
label = "lan1";
};
...
switch0port10: port@10 {
reg = <10>;
label = "dsa";
link = <&switch1port10>;
phy-mode = "sgmii";
fixed-link {
speed = <1000>;
full-duplex;
};
};
};
};
switch1: switch@1d: {
compatible = "marvell,mv88e6190";
reg = <0x1d>;
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
label = "lan9";
};
port@1 {
reg = <1>;
label = "lan10";
};
port@2 {
reg = <2>;
label = "lan11";
};
...
switch1port10: port@10 {
reg = <10>;
label = "dsa";
link = <&switch0port10>;
phy-mode = "sgmii";
fixed-link {
speed = <1000>;
full-duplex;
};
};
};
};
};
gem1: {
phy-handle = <phy0>;
};
It looks like you have at last one issue to solve in the macb driver.
If you have a fixed-phy, it does an mdiobus_register. This means it is
going to ignore all the other device tree properties. You need it to
do an of_mdiobus_register().
Andrew
next parent reply other threads:[~2018-03-16 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3988EA6F088014488BE41D19253A7EE40152236E92@EXS10.iai.co.il>
2018-03-16 15:12 ` Andrew Lunn [this message]
[not found] ` <3988EA6F088014488BE41D19253A7EE40152236EE1@EXS10.iai.co.il>
2018-03-19 16:23 ` DTS for our Configuration Alayev Michael
2018-03-19 16:56 ` Andrew Lunn
[not found] ` <48F7D4389F30BA4383F214EE802BA471017065554B@EXS10.iai.co.il>
2018-03-20 12:38 ` Andrew Lunn
[not found] <48F7D4389F30BA4383F214EE802BA47101706555D3@EXS10.iai.co.il>
2018-03-22 9:55 ` Alayev Michael
2018-03-22 13:55 ` Andrew Lunn
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=20180316151206.GG17895@lunn.ch \
--to=andrew@lunn.ch \
--cc=adror@iai.co.il \
--cc=malayev@iai.co.il \
--cc=netdev@vger.kernel.org \
--cc=yefter@iai.co.il \
/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).