All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net] Revert "net: stmmac: Specify hardware capability value when FIFO size isn't specified"
Date: Thu, 6 Feb 2025 10:47:37 +0000	[thread overview]
Message-ID: <Z6STSb0ZSKN1e1rX@shell.armlinux.org.uk> (raw)
In-Reply-To: <2cff81d8-9bda-4aa0-80b6-2ef92cd960a6@redhat.com>

On Thu, Feb 06, 2025 at 09:08:10AM +0100, Paolo Abeni wrote:
> On 2/5/25 1:57 PM, Russell King (Oracle) wrote:
> > This reverts commit 8865d22656b4, which caused breakage for platforms
> > which are not using xgmac2 or gmac4. Only these two cores have the
> > capability of providing the FIFO sizes from hardware capability fields
> > (which are provided in priv->dma_cap.[tr]x_fifo_size.)
> > 
> > All other cores can not, which results in these two fields containing
> > zero. We also have platforms that do not provide a value in
> > priv->plat->[tr]x_fifo_size, resulting in these also being zero.
> > 
> > This causes the new tests introduced by the reverted commit to fail,
> > and produce e.g.:
> > 
> > 	stmmaceth f0804000.eth: Can't specify Rx FIFO size
> > 
> > An example of such a platform which fails is QEMU's npcm750-evb.
> > This uses dwmac1000 which, as noted above, does not have the capability
> > to provide the FIFO sizes from hardware.
> > 
> > Therefore, revert the commit to maintain compatibility with the way
> > the driver used to work.
> > 
> > Reported-by: Guenter Roeck <linux@roeck-us.net>
> > Link: https://lore.kernel.org/r/4e98f967-f636-46fb-9eca-d383b9495b86@roeck-us.net
> > Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
> 
> Given the fallout caused by the blamed commit, the imminent net PR, and
> the substantial agreement about the patch already shared by many persons
> on the ML, unless someone raises very serious concerns very soon, I'm
> going to apply this patch (a little) earlier than the 24h grace period,
> to fit the mentioned PR.

Thanks. Here's the missing Fixes tag that I missed:

Fixes: 8865d22656b4 ("net: stmmac: Specify hardware capability value when
FIFO size isn't specified")

Not sure if patchwork will pick that up.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!


  reply	other threads:[~2025-02-06 10:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 12:57 [PATCH net] Revert "net: stmmac: Specify hardware capability value when FIFO size isn't specified" Russell King (Oracle)
2025-02-06  8:08 ` Paolo Abeni
2025-02-06 10:47   ` Russell King (Oracle) [this message]
2025-02-06 10:57     ` Paolo Abeni
2025-02-06  9:25 ` Steven Price
2025-02-06 11:00 ` patchwork-bot+netdevbpf

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=Z6STSb0ZSKN1e1rX@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.