From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Furong Xu <0x1207@gmail.com>,
Joao Pinto <Joao.Pinto@synopsys.com>,
Vince Bridgers <vbridger@opensource.altera.com>,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 0/3] Limit devicetree parameters to hardware capability
Date: Thu, 23 Jan 2025 16:31:12 +0000 [thread overview]
Message-ID: <Z5Ju0DtNDwj_hO0F@shell.armlinux.org.uk> (raw)
In-Reply-To: <ea845c58-ee2a-4660-bc13-7e05003de5d0@socionext.com>
On Thu, Jan 23, 2025 at 02:25:15PM +0900, Kunihiko Hayashi wrote:
> Hi Russell,
>
> Thank you for your comment.
>
> On 2025/01/21 19:25, Russell King (Oracle) wrote:
> > On Tue, Jan 21, 2025 at 01:41:35PM +0900, Kunihiko Hayashi wrote:
> > > This series includes patches that checks the devicetree properties,
> > > the number of MTL queues and FIFO size values, and if these specified
> > > values exceed the value contained in the hardware capabilities, limit to
> > > the values from the capabilities.
> > >
> > > And this sets hardware capability values if FIFO sizes are not specified
> > > and removes redundant lines.
> >
> > I think you also indeed to explain why (and possibly understand) - if
> > there are hardware capabilities that describe these parameters - it has
> > been necessary to have them in firmware as well.
> >
> > There are two scenarios I can think of why these would be duplicated:
> >
> > 1. firmware/platform capabilities are there to correct wrong values
> > provided by the hardware.
> > 2. firmware/platform capabilities are there to reduce the parameters
> > below hardware maximums.
> >
> > Which it is affects whether your patch is correct or not, and thus needs
> > to be mentioned.
>
> I think scenario 2 applies in this case.
In light of my other reply
(https://lore.kernel.org/r/Z4_ZilVFKacuAUE8@shell.armlinux.org.uk) I
don't think either of my two above applies, and the driver is designed
to allow platform code to override the hardware value, or to provide
the value if there is no hardware value.
My suggestion, therefore, would be (e.g.):
if (priv->dma_cap.rx_fifo_size &&
priv->plat->rx_fifo_size > priv->dma_cap.rx_fifo_size) {
dev_warn(priv->device,
"Rx FIFO size exceeds dma capability (%d)\n",
priv->plat->rx_fifo_size);
priv->plat->rx_fifo_size = priv->dma_cap.rx_fifo_size;
}
if we still want to limit it to the hardware provided capability, where
that is provided.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-01-23 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 4:41 [PATCH net v2 0/3] Limit devicetree parameters to hardware capability Kunihiko Hayashi
2025-01-21 4:41 ` [PATCH net v2 1/3] net: stmmac: Limit the number of MTL queues " Kunihiko Hayashi
2025-01-21 6:25 ` Furong Xu
2025-01-21 4:41 ` [PATCH net v2 2/3] net: stmmac: Limit FIFO size by " Kunihiko Hayashi
2025-01-21 17:14 ` Yanteng Si
2025-01-21 17:29 ` Russell King (Oracle)
2025-01-23 5:25 ` Kunihiko Hayashi
2025-01-22 4:07 ` Huacai Chen
2025-01-21 4:41 ` [PATCH net v2 3/3] net: stmmac: Specify hardware capability value when FIFO size isn't specified Kunihiko Hayashi
2025-01-21 10:25 ` [PATCH net v2 0/3] Limit devicetree parameters to hardware capability Russell King (Oracle)
2025-01-23 5:25 ` Kunihiko Hayashi
2025-01-23 16:31 ` Russell King (Oracle) [this message]
2025-01-24 4:19 ` Kunihiko Hayashi
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=Z5Ju0DtNDwj_hO0F@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=0x1207@gmail.com \
--cc=Joao.Pinto@synopsys.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vbridger@opensource.altera.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).