From: Andrew Lunn <andrew@lunn.ch>
To: Xiaolei Wang <xiaolei.wang@windriver.com>
Cc: linux@armlinux.org.uk, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [net v2 PATCH] net: stmmac: Update CBS parameters when speed changes after linking up
Date: Thu, 30 May 2024 14:50:52 +0200 [thread overview]
Message-ID: <f8b0843f-7900-4ad0-9e70-c16175e893d9@lunn.ch> (raw)
In-Reply-To: <20240530061453.561708-1-xiaolei.wang@windriver.com>
> static void stmmac_configure_cbs(struct stmmac_priv *priv)
> {
> u32 tx_queues_count = priv->plat->tx_queues_to_use;
> u32 mode_to_use;
> u32 queue;
> + u32 ptr, speed_div;
> + u64 value;
> +
> + /* Port Transmit Rate and Speed Divider */
> + switch (priv->speed) {
> + case SPEED_10000:
> + ptr = 32;
> + speed_div = 10000000;
> + break;
> + case SPEED_5000:
> + ptr = 32;
> + speed_div = 5000000;
> + break;
> + case SPEED_2500:
> + ptr = 8;
> + speed_div = 2500000;
> + break;
> + case SPEED_1000:
> + ptr = 8;
> + speed_div = 1000000;
> + break;
> + case SPEED_100:
> + ptr = 4;
> + speed_div = 100000;
> + break;
> + default:
No SPEED_10 ?
> + netdev_dbg(priv->dev, "link speed is not known\n");
> + }
>
> /* queue 0 is reserved for legacy traffic */
> for (queue = 1; queue < tx_queues_count; queue++) {
> @@ -3196,6 +3231,12 @@ static void stmmac_configure_cbs(struct stmmac_priv *priv)
> if (mode_to_use == MTL_QUEUE_DCB)
> continue;
>
> + value = div_s64(priv->old_idleslope[queue] * 1024ll * ptr, speed_div);
> + priv->plat->tx_queues_cfg[queue].idle_slope = value & GENMASK(31, 0);
Rather than masking off the top bits, shouldn't you be looking for
overflow? that indicates the configuration is not possible. You don't
have a good way to report the problem, since there is no user action
on link up, so you cannot return -EINVAL or -EOPNOTSUPP. So you
probably want to set the hardware as close as possible.
Also, what happens if the result of the div is 0? Does 0 have a
special meaning?
> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_tc.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_tc.c
> index 222540b55480..d3526ad91aff 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_tc.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_tc.c
> @@ -355,6 +355,9 @@ static int tc_setup_cbs(struct stmmac_priv *priv,
> if (!priv->dma_cap.av)
> return -EOPNOTSUPP;
>
> + if (!netif_carrier_ok(priv->dev))
> + return -ENETDOWN;
> +
Now that you are configuring the hardware on link up, does that
matter?
Andrew
next prev parent reply other threads:[~2024-05-30 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 6:14 Xiaolei Wang
2024-05-30 12:50 ` Andrew Lunn [this message]
2024-05-30 13:28 ` Vladimir Oltean
2024-05-30 13:40 ` Russell King (Oracle)
2024-05-30 13:53 ` Vladimir Oltean
2024-05-30 14:14 ` Russell King (Oracle)
2024-05-30 14:35 ` Vladimir Oltean
2024-05-31 8:23 ` xiaolei wang
2024-05-30 16:13 ` Jakub Kicinski
2024-06-05 5:26 ` Dan Carpenter
2024-06-05 5:30 ` xiaolei wang
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=f8b0843f-7900-4ad0-9e70-c16175e893d9@lunn.ch \
--to=andrew@lunn.ch \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xiaolei.wang@windriver.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
all inboxes | Powered by JetHome®