From: Andrew Lunn <andrew@lunn.ch>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Vivien Didelot <vivien.didelot@gmail.com>
Subject: Re: [PATCH net-next 2/2] net: dsa: mv88e6xxx: Set link down when changing speed
Date: Fri, 27 Mar 2020 22:26:08 +0100 [thread overview]
Message-ID: <20200327212608.GU3819@lunn.ch> (raw)
In-Reply-To: <20200327111316.GF25745@shell.armlinux.org.uk>
> > Hi Russell
> >
> > So the problem here is that CPU and DSA ports should default to up and
> > at their fastest speed. During setup, the driver is setting the CPU
> > port to 1G and up. Later on, phylink finds the fixed-link node in DT,
> > and then sets the port to 100Mbps as requested.
> >
> > How do you suggest fixing this? If we find a fixed-link, configure it
> > first down and then up?
>
> I think this is another example of DSA fighting phylink in terms of
> what's expected.
>
> The only suggestion I've come up so far with is to avoid calling
> mv88e6xxx_port_setup_mac() with forced-link-up in
> mv88e6xxx_setup_port() if we have phylink attached.
Hi Russell
Yes, that might work. But it is a solution specific to mv88e6xxx. I
guess other switches could have a similar issue.
Is it really that bad to add the link down as i proposed? Do we even
have a guarantee the port is down before phylink starts configuring
it, for all switch drivers?
Andrew
next prev parent reply other threads:[~2020-03-27 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 21:48 [PATCH net-next 0/2] mv88e6xxx fixed link fixes Andrew Lunn
2020-03-23 21:48 ` [PATCH net-next 1/2] net: dsa: mv88e6xxx: Configure MAC when using fixed link Andrew Lunn
2020-03-23 21:49 ` [PATCH net-next 2/2] net: dsa: mv88e6xxx: Set link down when changing speed Andrew Lunn
2020-03-23 22:01 ` Russell King - ARM Linux admin
2020-03-23 22:39 ` Andrew Lunn
2020-03-27 11:13 ` Russell King - ARM Linux admin
2020-03-27 21:26 ` Andrew Lunn [this message]
2020-03-27 21:48 ` Russell King - ARM Linux admin
2020-03-27 2:57 ` [PATCH net-next 0/2] mv88e6xxx fixed link fixes David Miller
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=20200327212608.GU3819@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=linux@armlinux.org.uk \
--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).