From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org,
"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
Antoine Tenart <antoine.tenart@bootlin.com>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: dsa: using multi-gbps speeds on CPU port
Date: Wed, 15 May 2019 14:39:36 +0200 [thread overview]
Message-ID: <20190515143936.524acd4e@bootlin.com> (raw)
Hello everyone,
I'm working on a setup where I have a 88e6390X DSA switch connected to
a CPU (an armada 8040) with 2500BaseX and RXAUI interfaces (we only use
one at a time).
I'm facing a limitation with the current way to represent that link,
where we use a fixed-link description in the CPU port, like this :
...
switch0: switch0@1 {
...
port@0 {
reg = <0>;
label = "cpu";
ethernet = <ð0>;
phy-mode = "2500base-x";
fixed-link {
speed = <2500>;
full-duplex;
};
};
};
...
In this scenario, the dsa core will try to create a PHY emulating the
fixed-link on the DSA port side. This can't work with link speeds above
1Gbps, since we don't have any emulation for these PHYs, which would be
using C45 MMDs.
We could add support to emulate these modes, but I think there were some
discussions about using phylink to support these higher speed fixed-link
modes, instead of using PHY emulation.
However using phylink in master DSA ports seems to be a bit tricky,
since master ports don't have a dedicated net_device, and instead
reference the CPU-side netdevice (if I understood correctly).
I'll be happy to help on that, but before prototyping anything, I wanted
to have your thougts on this, and see if you had any plans.
Thanks,
Maxime
next reply other threads:[~2019-05-15 12:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 12:39 Maxime Chevallier [this message]
2019-05-15 13:27 ` dsa: using multi-gbps speeds on CPU port Andrew Lunn
2019-05-15 14:02 ` Maxime Chevallier
2019-05-15 16:09 ` Florian Fainelli
2019-05-15 16:19 ` Russell King - ARM Linux admin
2019-05-16 6:56 ` Vladimir Oltean
2019-05-16 12:58 ` Andrew Lunn
2019-05-17 15:10 ` Maxime Chevallier
2019-05-17 17:37 ` Ioana Ciornei
2019-05-17 18:03 ` Russell King - ARM Linux admin
2019-05-17 18:10 ` Florian Fainelli
2019-05-17 18:23 ` Russell King - ARM Linux admin
2019-05-15 16:12 ` Russell King - ARM Linux admin
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=20190515143936.524acd4e@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=andrew@lunn.ch \
--cc=antoine.tenart@bootlin.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vivien.didelot@gmail.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;
as well as URLs for NNTP newsgroup(s).