From: Andrew Lunn <andrew@lunn.ch>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
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 16:07:26 +0100 [thread overview]
Message-ID: <Ya94roatTK0y7t70@lunn.ch> (raw)
In-Reply-To: <Ya92klnTqoUpFvpo@shell.armlinux.org.uk>
On Tue, Dec 07, 2021 at 02:58:26PM +0000, Russell King (Oracle) wrote:
> 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.
This all seems to be part of:
b98043f66e8c6f1fd75d11af7b28c55018c58d79.camel@collabora.com
It looks like 5.15-rc3 has issues, but i suspect it goes back further.
I'm also assuming it is a regression, not that it never worked in the
first place. Maybe i'm wrong?
Andrew
next prev parent reply other threads:[~2021-12-07 15:07 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)
2021-12-07 15:07 ` Andrew Lunn [this message]
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=Ya94roatTK0y7t70@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--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 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).