From: Andrew Lunn <andrew@lunn.ch>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: "vivien.didelot@gmail.com" <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
netdev <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: dsa: mv88e6xxx: serdes link without phy
Date: Thu, 1 Oct 2020 03:24:10 +0200 [thread overview]
Message-ID: <20201001012410.GA4050473@lunn.ch> (raw)
In-Reply-To: <72e8e25a-db0d-275f-e80e-0b74bf112832@alliedtelesis.co.nz>
> port@8 {
> reg = <8>;
> label = "internal8";
> phy-mode = "rgmii-id";
> fixed-link {
> speed = <1000>;
> full-duplex;
> };
> };
> port@9 {
> reg = <9>;
> label = "internal9";
> phy-mode = "rgmii-id";
> fixed-link {
> speed = <1000>;
> full-duplex;
> };
> };
>
> The problem is that by declaring ports 8 & 9 as fixed link the driver
> sets the ForcedLink in the PCS control register. Which mostly works.
> Except if I add a chassis controller while the system is running (or one
> is rebooted) then the newly added controller doesn't see a link on the
> serdes.
Hi Chris
You say SERDES here, but in DT you have rgmii-id?
Can you run 1000Base-X over these links? If you can, it is probably
worth chatting to Russell King about using inband-signalling, and what
is needed to make it work without having back to back SFPs. If i
remember correctly, Russell has said not much is actually needed.
Andrew
next prev parent reply other threads:[~2020-10-01 1:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 0:45 Chris Packham
2020-10-01 1:24 ` Andrew Lunn [this message]
2020-10-01 2:27 ` Chris Packham
2020-10-01 12:36 ` Andrew Lunn
2020-10-02 4:13 ` Chris Packham
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=20201001012410.GA4050473@lunn.ch \
--to=andrew@lunn.ch \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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
all inboxes | Powered by JetHome®