From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Jakub Kicinski <kuba@kernel.org>,
Oleksij Rempel <o.rempel@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew@lunn.ch>, Eric Dumazet <edumazet@google.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
Vladimir Oltean <olteanv@gmail.com>,
Woojung Huh <woojung.huh@microchip.com>,
Arun Ramadoss <arun.ramadoss@microchip.com>,
kernel@pengutronix.de, UNGLinuxDriver@microchip.com,
netdev@vger.kernel.org
Subject: Re: FWD: Re: [PATCH net-next v1 1/1] net: dsa: microchip: ksz8: Make flow control, speed, and duplex on CPU port configurable
Date: Fri, 7 Apr 2023 18:44:20 +0100 [thread overview]
Message-ID: <ZDBWdFGN7zmF2A3N@shell.armlinux.org.uk> (raw)
In-Reply-To: <7055f8c2-3dba-49cd-b639-b4b507bc1249@lunn.ch>
On Fri, Apr 07, 2023 at 04:25:57PM +0200, Andrew Lunn wrote:
> Hi Russell
>
> It looks like you were not Cc:ed.
Thanks Andrew.
It really would help if people Cc'd the right folk! Because they failed
to, sorry, this isn't going to be a reply that's threaded properly...
> > diff --git a/drivers/net/dsa/microchip/ksz8795.c b/drivers/net/dsa/microchip/ksz8795.c
> > index d0e3f6e2db1d..8917f22f90d2 100644
> > --- a/drivers/net/dsa/microchip/ksz8795.c
> > +++ b/drivers/net/dsa/microchip/ksz8795.c
> > @@ -1321,12 +1321,52 @@ void ksz8_config_cpu_port(struct dsa_switch *ds)
> > if (remote & KSZ8_PORT_FIBER_MODE)
> > p->fiber = 1;
> > }
> > - if (p->fiber)
> > - ksz_port_cfg(dev, i, regs[P_STP_CTRL],
> > - PORT_FORCE_FLOW_CTRL, true);
> > - else
> > - ksz_port_cfg(dev, i, regs[P_STP_CTRL],
> > - PORT_FORCE_FLOW_CTRL, false);
> > + }
> > +}
> > +
> > +void ksz8_phylink_mac_link_up(struct ksz_device *dev, int port,
> > + unsigned int mode, phy_interface_t interface,
> > + struct phy_device *phydev, int speed, int duplex,
> > + bool tx_pause, bool rx_pause)
> > +{
> > + struct dsa_switch *ds = dev->ds;
> > + struct ksz_port *p;
> > + u8 ctrl = 0;
> > +
> > + p = &dev->ports[port];
> > +
> > + if (dsa_upstream_port(ds, port)) {
> > + u8 mask = SW_HALF_DUPLEX_FLOW_CTRL | SW_HALF_DUPLEX |
> > + SW_FLOW_CTRL | SW_10_MBIT;
> > +
> > + if (duplex) {
> > + if (tx_pause && rx_pause)
> > + ctrl |= SW_FLOW_CTRL;
> > + } else {
> > + ctrl |= SW_HALF_DUPLEX;
> > + if (tx_pause && rx_pause)
> > + ctrl |= SW_HALF_DUPLEX_FLOW_CTRL;
> > + }
> > +
> > + if (speed == SPEED_10)
> > + ctrl |= SW_10_MBIT;
> > +
> > + ksz_rmw8(dev, REG_SW_CTRL_4, mask, ctrl);
> > +
> > + p->phydev.speed = speed;
> > + } else {
> > + const u16 *regs = dev->info->regs;
> > +
> > + if (duplex) {
> > + if (tx_pause && rx_pause)
> > + ctrl |= PORT_FORCE_FLOW_CTRL;
> > + } else {
> > + if (tx_pause && rx_pause)
> > + ctrl |= PORT_BACK_PRESSURE;
> > + }
> > +
> > + ksz_rmw8(dev, regs[P_STP_CTRL], PORT_FORCE_FLOW_CTRL |
> > + PORT_BACK_PRESSURE, ctrl);
So, I guess the idea here is to enable some form of flow control when
both tx and rx pause are enabled.
Here's a bunch of questions I would like answered before I give a tag:
1) It looks like the device only supports symmetric pause?
2) If yes, are you *not* providing MAC_ASYM_PAUSE in the MAC
capabilities? If not, why not?
3) If yes, then please do as others do and use tx_pause || rx_pause
here.
Lastly, a more general question for ethtool/network folk - as for half
duplex and back pressure, is that a recognised facility for the MAC
to control via the ethtool pause parameter API?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next parent reply other threads:[~2023-04-07 17:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7055f8c2-3dba-49cd-b639-b4b507bc1249@lunn.ch>
2023-04-07 17:44 ` Russell King (Oracle) [this message]
2023-04-11 8:56 ` FWD: Re: [PATCH net-next v1 1/1] net: dsa: microchip: ksz8: Make flow control, speed, and duplex on CPU port configurable Oleksij Rempel
2023-04-11 9:17 ` Russell King (Oracle)
2023-04-11 9:55 ` Oleksij Rempel
2023-04-11 11:16 ` Vladimir Oltean
2023-04-11 11:35 ` Vladimir Oltean
2023-04-11 12:00 ` Russell King (Oracle)
2023-04-11 12:16 ` Andrew Lunn
2023-04-11 13:26 ` Vladimir Oltean
2023-04-11 13:33 ` Russell King (Oracle)
2023-04-11 14:28 ` Vladimir Oltean
2023-04-11 11:50 ` Russell King (Oracle)
2023-04-11 13:12 ` Vladimir Oltean
2023-04-11 13:26 ` Russell King (Oracle)
2023-04-11 14:33 ` Vladimir Oltean
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=ZDBWdFGN7zmF2A3N@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=woojung.huh@microchip.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).