[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <X/tBiyrJ8cJX+3u6@lunn.ch>
Date: Sun, 10 Jan 2021 19:03:55 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Stefan Chulski <stefanc@...vell.com>
Cc: Russell King - ARM Linux admin <linux@...linux.org.uk>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"thomas.petazzoni@...tlin.com" <thomas.petazzoni@...tlin.com>,
"davem@...emloft.net" <davem@...emloft.net>,
Nadav Haklai <nadavh@...vell.com>,
Yan Markman <ymarkman@...vell.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kuba@...nel.org" <kuba@...nel.org>,
"mw@...ihalf.com" <mw@...ihalf.com>,
"atenart@...nel.org" <atenart@...nel.org>
Subject: Re: [EXT] Re: [PATCH RFC net-next 03/19] net: mvpp2: add CM3 SRAM
memory map
On Sun, Jan 10, 2021 at 05:57:14PM +0000, Stefan Chulski wrote:
> > > + } else {
> > > + priv->sram_pool = of_gen_pool_get(dn, "cm3-mem", 0);
> > > + if (!priv->sram_pool) {
> > > + dev_warn(&pdev->dev, "DT is too old, TX FC
> > disabled\n");
> >
> > I don't see anything in this patch that disables TX flow control, which means
> > this warning message is misleading.
>
> OK, I would change to TX FC not supported.
And you should tell phlylink, so it knows to disable it in autoneg.
Which make me wonder, do we need a fix for stable? Has flow control
never been support in this device up until these patches get merged?
It should not be negotiated if it is not supported, which means
telling phylink.
Andrew
Powered by blists - more mailing lists