From: Marek Behun <marek.behun@nic.cz>
To: Chris Healy <cphealy@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>, netdev <netdev@vger.kernel.org>
Subject: Re: bug: net: dsa: mv88e6xxx: serdes Unable to communicate on fiber with vf610-zii-dev-rev-c
Date: Sun, 19 Jul 2020 23:52:02 +0200 [thread overview]
Message-ID: <20200719235202.6ee120b9@nic.cz> (raw)
In-Reply-To: <CAFXsbZrHRexg5zAsR1cah4p8HAZVc3tjKdMGKWO6Ha4jXux3QA@mail.gmail.com>
On Sun, 19 Jul 2020 14:43:49 -0700
Chris Healy <cphealy@gmail.com> wrote:
> > Hmm.
> >
> > What about the errata setup?
> > It says:
> > /* The 6390 copper ports have an errata which require poking magic
> > * values into undocumented hidden registers and then performing a
> > * software reset.
> > */
> > But then the port_hidden_write function is called for every port in the
> > function mv88e6390_setup_errata, not just for copper ports. Maybe Chris
> > should try to not write this hidden register for SerDes ports.
>
> I just disabled the mv88e6390_setup_errata all together and this did
> not result in any different behaviour on this broken fiber port.
:-( In that case I really have no idea what could be the problem.
Another thing you could try is resoldering resistors on the board so
that the switches configure themselves into NOCPU mode and the port you
are talking about configures itself into the cmode you need
(was it 1000base-x or sgmii?). Disable DSA, write yourself sysfs API
via which you can read/write switch registers by yourself. Then you can
chech if the problem on the RX path occurs. If no, read all the
registers and compare their values with the ones the mv88e6xxx driver
configures. If yes, then we know that the problem is there even if the
switch is NOCPU mode and you can inform Marvell about the bug.
Marek
next prev parent reply other threads:[~2020-07-19 21:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 14:27 bug: net: dsa: mv88e6xxx: serdes Unable to communicate on fiber with vf610-zii-dev-rev-c Chris Healy
2020-07-18 14:42 ` Marek Behun
2020-07-18 14:49 ` Chris Healy
2020-07-18 15:05 ` Andrew Lunn
2020-07-18 15:22 ` Marek Behun
2020-07-19 21:43 ` Chris Healy
2020-07-19 21:52 ` Marek Behun [this message]
2021-01-18 17:31 ` Tobias Waldekranz
2021-01-18 17:41 ` Andrew Lunn
2021-01-18 17:47 ` Tobias Waldekranz
2021-01-18 19:26 ` 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=20200719235202.6ee120b9@nic.cz \
--to=marek.behun@nic.cz \
--cc=andrew@lunn.ch \
--cc=cphealy@gmail.com \
--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).