From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>,
Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: phylink / mv8e6xxx and SGMII aneg not working, link doesn't come up
Date: Thu, 28 Feb 2019 00:51:54 +0100 [thread overview]
Message-ID: <116d8984-8845-cd2b-8a41-1cc80be9b12c@gmail.com> (raw)
In-Reply-To: <20190227231940.GN3809@lunn.ch>
On 28.02.2019 00:19, Andrew Lunn wrote:
>> >From what you've described, it sounds like what you actually have is:
>>
>> MAC <---> Serdes PHY <---> PHY
>>
>> The Serdes PHY receives the SGMII in-band negotiation from the external
>> PHY, but there is no propagation of the status from the serdes PHY to
>> the MAC.
>
> Yes, that is a good description. So far, we have not yet got the MAC
> to read the speed and duplex from the SERDES to configure itself. In
> theory it should be able to, it is all in the same device.
>
> It might be that once the SERDES interrupts saying it has link we need
> to program the MAC with the result of the in-band signalling. in-band
> then seems a bit pointless. Or we are missing some configuration
> somewhere to tell the MAC to use the in-band signalling result from
> the SERDES.
>
I'll play a little with it and see whether I get it working.
As a fallback we have the option to go with out-of-band.
> Andrew
>
>
Heiner
next prev parent reply other threads:[~2019-02-27 23:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 21:25 phylink / mv8e6xxx and SGMII aneg not working, link doesn't come up Heiner Kallweit
2019-02-27 22:52 ` Russell King - ARM Linux admin
2019-02-27 23:19 ` Andrew Lunn
2019-02-27 23:27 ` Russell King - ARM Linux admin
2019-02-27 23:51 ` Heiner Kallweit [this message]
2019-02-28 14:04 ` Andrew Lunn
2019-02-28 23:22 ` Heiner Kallweit
2019-02-27 23:25 ` Heiner Kallweit
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=116d8984-8845-cd2b-8a41-1cc80be9b12c@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
/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).