From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Martin Rowe <martin.p.rowe@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
netdev@vger.kernel.org, davem@davemloft.net,
vivien.didelot@gmail.com
Subject: Re: bug: net: dsa: mv88e6xxx: unable to tx or rx with Clearfog GT 8K (with git bisect)
Date: Sat, 18 Jul 2020 11:12:59 +0100 [thread overview]
Message-ID: <20200718101259.GO1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAOAjy5SewXHQVnywzin-2LiqWyPcjTvG9zzaiVRtwfCG=jU1Kw@mail.gmail.com>
On Sat, Jul 18, 2020 at 09:43:47AM +0000, Martin Rowe wrote:
> On Sat, 18 Jul 2020 at 08:50, Russell King - ARM Linux admin
> <linux@armlinux.org.uk> wrote:
> > Sorry, it should have been ``managed = "in-band-status";'' rather than
> > just "in-band".
>
> Below are the outputs with "in-band-status". It functions the same as
> not reverting the patch; interface comes up, when bridged the two
> physical machines connected can ping each other, but nothing can tx or
> rx from the GT 8K.
Okay, on top of those changes, please also add this:
diff --git a/drivers/net/dsa/mv88e6xxx/chip.c b/drivers/net/dsa/mv88e6xxx/chip.c
index 17883e8712e0..2e361bbf3b4f 100644
--- a/drivers/net/dsa/mv88e6xxx/chip.c
+++ b/drivers/net/dsa/mv88e6xxx/chip.c
@@ -676,6 +676,9 @@ static void mv88e6xxx_mac_config(struct dsa_switch *ds, int port,
return;
mv88e6xxx_reg_lock(chip);
+ if (mode == MLO_AN_INBAND && chip->info->ops->port_set_link)
+ chip->info->ops->port_set_link(chip, port, LINK_FORCED_DOWN);
+
/* FIXME: should we force the link down here - but if we do, how
* do we restore the link force/unforce state? The driver layering
* gets in the way.
@@ -692,6 +695,9 @@ static void mv88e6xxx_mac_config(struct dsa_switch *ds, int port,
if (err > 0)
err = 0;
+ if (mode == MLO_AN_INBAND && chip->info->ops->port_set_link)
+ chip->info->ops->port_set_link(chip, port, LINK_UNFORCED);
+
err_unlock:
mv88e6xxx_reg_unlock(chip);
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2020-07-18 10:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 13:50 bug: net: dsa: mv88e6xxx: unable to tx or rx with Clearfog GT 8K (with git bisect) Martin Rowe
2020-07-11 16:23 ` Andrew Lunn
2020-07-11 19:22 ` Russell King - ARM Linux admin
2020-07-12 13:00 ` Martin Rowe
2020-07-12 13:25 ` Russell King - ARM Linux admin
2020-07-17 5:56 ` Martin Rowe
2020-07-17 9:21 ` Russell King - ARM Linux admin
2020-07-17 12:50 ` Martin Rowe
2020-07-17 18:51 ` Russell King - ARM Linux admin
2020-07-17 19:42 ` Andrew Lunn
2020-07-17 21:26 ` Russell King - ARM Linux admin
2020-07-18 2:37 ` Martin Rowe
2020-07-18 8:50 ` Russell King - ARM Linux admin
2020-07-18 9:43 ` Martin Rowe
2020-07-18 10:12 ` Russell King - ARM Linux admin [this message]
2020-07-18 11:21 ` Martin Rowe
2020-07-18 11:26 ` 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=20200718101259.GO1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=martin.p.rowe@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).