From: "Marek Behún" <kabel@kernel.org>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: andrew@lunn.ch, netdev@vger.kernel.org, olteanv@gmail.com,
pavana.sharma@digi.com
Subject: Re: mv88e6xxx: 2500base-x inband AN is broken on Amethyst? what to do?
Date: Wed, 13 Jan 2021 18:03:31 +0100 [thread overview]
Message-ID: <20210113180331.5e79ee08@kernel.org> (raw)
In-Reply-To: <20210113102849.GG1551@shell.armlinux.org.uk>
On Wed, 13 Jan 2021 10:28:49 +0000
Russell King - ARM Linux admin <linux@armlinux.org.uk> wrote:
> I don't know whether the 88x3310 on the host side uses AN or not for
> 2500base-X - that detail isn't mentioned in the datasheet, and I don't
> have a setup that I could test that with.
It does not. I have been poking the registers on 88x3310, and also on
Peridot and Amethyst SERDES PHYs when cmode on the switch is set to
2500base-x, and by default the inband AN is disabled.
Enabling it on the PHY in Amethyst does not work at all. On Peridot
your code in mv88e6xxx enables it, but when 88x3310 is connected to
Peridot SERDES, it does not work until the AN is disabled on Peridot.
Enabling the AN on 2500base-x mode on 88x3310 does not seem to work.
I will do some more tests by poking the registers and report this.
Marek
next prev parent reply other threads:[~2021-01-13 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 0:18 mv88e6xxx: 2500base-x inband AN is broken on Amethyst? what to do? Marek Behún
2021-01-13 4:22 ` Marek Behun
2021-01-13 10:28 ` Russell King - ARM Linux admin
2021-01-13 17:03 ` Marek Behún [this message]
2021-01-13 20:08 ` Marek Behún
2021-01-13 21:21 ` Russell King - ARM Linux admin
2021-01-13 21:37 ` Marek Behún
2021-01-13 21:48 ` 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=20210113180331.5e79ee08@kernel.org \
--to=kabel@kernel.org \
--cc=andrew@lunn.ch \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pavana.sharma@digi.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).