From: Simon Horman <horms@kernel.org>
To: Furong Xu <0x1207@gmail.com>
Cc: netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Vladimir Oltean <olteanv@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
"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>,
xfr@outlook.com
Subject: Re: [PATCH net-next v1 5/5] net: stmmac: xgmac: Complete FPE support
Date: Thu, 17 Oct 2024 13:29:36 +0100 [thread overview]
Message-ID: <20241017122936.GF1697@kernel.org> (raw)
In-Reply-To: <7b244a9d6550bd856298150fb4c083ca95b41f38.1728980110.git.0x1207@gmail.com>
On Tue, Oct 15, 2024 at 05:09:26PM +0800, Furong Xu wrote:
> FPE implementation for DWMAC4 and DWXGMAC differs only for:
> 1) Offset address of MAC_FPE_CTRL_STS and MTL_FPE_CTRL_STS
> 2) FPRQ(Frame Preemption Residue Queue) field in MAC_RxQ_Ctrl1
>
> Refactor stmmac_fpe_ops callback functions to avoid code duplication
> between gmac4 and xgmac.
>
> Signed-off-by: Furong Xu <0x1207@gmail.com>
Hi Furong Xu,
I think it would be best to split this patch so that the refactor of dwmac4
code is in one patch, and adding xgmac code is in another.
...
> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_fpe.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_fpe.c
> index 6060a1d702c6..80f12b6e84e6 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_fpe.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_fpe.c
> @@ -160,41 +160,54 @@ void stmmac_fpe_apply(struct stmmac_priv *priv)
> }
> }
>
> -static void dwmac5_fpe_configure(void __iomem *ioaddr,
> - struct stmmac_fpe_cfg *cfg,
> - u32 num_txq, u32 num_rxq,
> - bool tx_enable, bool pmac_enable)
> +static void common_fpe_configure(void __iomem *ioaddr,
> + struct stmmac_fpe_cfg *cfg, u32 rxq,
> + bool tx_enable, bool pmac_enable,
> + u32 rxq_addr, u32 fprq_mask, u32 fprq_shift,
> + u32 mac_fpe_addr, u32 int_en_addr,
> + u32 int_en_bit)
This function now has a lot of parameters. Could we consider another way?
One idea I had was that describes the addresses for different chips.
...
> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_tc.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_tc.c
> index 75ad2da1a37f..6a79e6a111ed 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_tc.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_tc.c
> @@ -1290,8 +1290,8 @@ const struct stmmac_tc_ops dwxgmac_tc_ops = {
> .setup_cls_u32 = tc_setup_cls_u32,
> .setup_cbs = tc_setup_cbs,
> .setup_cls = tc_setup_cls,
> - .setup_taprio = tc_setup_taprio_without_fpe,
> + .setup_taprio = tc_setup_taprio,
> .setup_etf = tc_setup_etf,
> .query_caps = tc_query_caps,
> - .setup_mqprio = tc_setup_mqprio_unimplemented,
> + .setup_mqprio = tc_setup_dwmac510_mqprio,
> };
It is not clear to me how this hunk relates to the rest of the patch.
next prev parent reply other threads:[~2024-10-17 12:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 9:09 [PATCH net-next v1 0/5] net: stmmac: Refactor FPE as a separate module Furong Xu
2024-10-15 9:09 ` [PATCH net-next v1 1/5] net: stmmac: Introduce separate files for FPE implementation Furong Xu
2024-10-17 12:39 ` Simon Horman
2024-10-15 9:09 ` [PATCH net-next v1 2/5] net: stmmac: Introduce stmmac_fpe_ops for gmac4 and xgmac Furong Xu
2024-10-17 12:39 ` Simon Horman
2024-10-15 9:09 ` [PATCH net-next v1 3/5] net: stmmac: Rework marco definitions " Furong Xu
2024-10-17 12:39 ` Simon Horman
2024-10-17 17:16 ` Vladimir Oltean
2024-10-15 9:09 ` [PATCH net-next v1 4/5] net: stmmac: xgmac: Rename XGMAC_RQ to XGMAC_FPRQ Furong Xu
2024-10-17 12:40 ` Simon Horman
2024-10-17 12:41 ` Simon Horman
2024-10-17 17:18 ` Vladimir Oltean
2024-10-18 19:16 ` Simon Horman
2024-10-15 9:09 ` [PATCH net-next v1 5/5] net: stmmac: xgmac: Complete FPE support Furong Xu
2024-10-17 12:29 ` Simon Horman [this message]
2024-10-17 17:31 ` Vladimir Oltean
2024-10-17 17:06 ` [PATCH net-next v1 0/5] net: stmmac: Refactor FPE as a separate module Vladimir Oltean
2024-10-18 1:33 ` Furong Xu
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=20241017122936.GF1697@kernel.org \
--to=horms@kernel.org \
--cc=0x1207@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--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-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=xfr@outlook.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).