From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Martyn Welch <martyn.welch@collabora.com>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH RFC net] net: dsa: mv88e6xxx: allow use of PHYs on CPU and DSA ports
Date: Tue, 7 Dec 2021 14:58:26 +0000 [thread overview]
Message-ID: <Ya92klnTqoUpFvpo@shell.armlinux.org.uk> (raw)
In-Reply-To: <Ya91rX5acIKQk7W0@lunn.ch>
On Tue, Dec 07, 2021 at 03:54:37PM +0100, Andrew Lunn wrote:
> On Tue, Dec 07, 2021 at 10:59:19AM +0000, Russell King (Oracle) wrote:
> > Martyn Welch reports that his CPU port is unable to link where it has
> > been necessary to use one of the switch ports with an internal PHY for
> > the CPU port. The reason behind this is the port control register is
> > left forcing the link down, preventing traffic flow.
> >
> > This occurs because during initialisation, phylink expects the link to
> > be down, and DSA forces the link down by synthesising a call to the
> > DSA drivers phylink_mac_link_down() method, but we don't touch the
> > forced-link state when we later reconfigure the port.
> >
> > Resolve this by also unforcing the link state when we are operating in
> > PHY mode and the PPU is set to poll the PHY to retrieve link status
> > information.
> >
> > Reported-by: Martyn Welch <martyn.welch@collabora.com>
> > Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
>
> Hi Russell
>
> It would be good to have a Fixes: tag here, to help with back porting.
Oh, I thought this was a new development, not a regression. Do you have
a pointer to the earlier bits of the thread please, e.g. the message ID
of the original report.
Thanks.
> The concept looks good, and i see you now have a Tested-by:, so with
> the fixup applied i think you are good to go. Please add my
> Reviewed-by: to the next version.
Will do.
--
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:[~2021-12-07 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 10:59 [PATCH RFC net] net: dsa: mv88e6xxx: allow use of PHYs on CPU and DSA ports Russell King (Oracle)
2021-12-07 12:47 ` Martyn Welch
2021-12-07 12:58 ` Russell King (Oracle)
2021-12-07 14:20 ` Martyn Welch
2021-12-07 14:23 ` Russell King (Oracle)
2021-12-07 14:54 ` Andrew Lunn
2021-12-07 14:58 ` Russell King (Oracle) [this message]
2021-12-07 15:07 ` Andrew Lunn
2021-12-07 15:28 ` Russell King (Oracle)
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=Ya92klnTqoUpFvpo@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=martyn.welch@collabora.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.