From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Joey Lu <a0987203069@gmail.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
mcoquelin.stm32@gmail.com, richardcochran@gmail.com,
alexandre.torgue@foss.st.com, joabreu@synopsys.com,
ychuang3@nuvoton.com, schung@nuvoton.com, yclu4@nuvoton.com,
peppe.cavallaro@st.com, linux-arm-kernel@lists.infradead.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org,
linux-stm32@st-md-mailman.stormreply.com,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH net-next v11 3/3] net: stmmac: dwmac-nuvoton: Add dwmac glue for Nuvoton MA35 family
Date: Thu, 5 Feb 2026 09:38:50 +0000 [thread overview]
Message-ID: <aYRlKk-cCIhqGWX7@shell.armlinux.org.uk> (raw)
In-Reply-To: <20260205014006.735408-4-a0987203069@gmail.com>
Hi,
On Thu, Feb 05, 2026 at 09:40:05AM +0800, Joey Lu wrote:
> +
> +struct nvt_priv_data {
> + struct platform_device *pdev;
This looks to me like it's write-only, does it serve a useful purpose?
> + struct regmap *regmap;
This doesn't seem to be used outside of nvt_gmac_setup().
> +};
Given the above two comments, do you actually need struct nvt_priv_data ?
> +
> +static struct nvt_priv_data *
> +nvt_gmac_setup(struct platform_device *pdev, struct plat_stmmacenet_data *plat)
> +{
> + struct device *dev = &pdev->dev;
> + struct nvt_priv_data *bsp_priv;
> + phy_interface_t phy_mode;
> + u32 macid, arg, reg;
> + u32 tx_delay_step;
> + u32 rx_delay_step;
> + u32 miscr;
> +
> + bsp_priv = devm_kzalloc(dev, sizeof(*bsp_priv), GFP_KERNEL);
> + if (!bsp_priv)
> + return ERR_PTR(-ENOMEM);
> +
> + bsp_priv->regmap =
> + syscon_regmap_lookup_by_phandle_args(dev->of_node, "nuvoton,sys", 1, &macid);
> + if (IS_ERR(bsp_priv->regmap))
> + return ERR_PTR(dev_err_probe(dev, PTR_ERR(bsp_priv->regmap),
> + "Failed to get sys register\n"));
> + if (macid > 1) {
> + dev_err(dev, "Invalid sys arguments\n");
> + return ERR_PTR(-EINVAL);
> + }
> +
> + if (of_property_read_u32(dev->of_node, "tx-internal-delay-ps", &arg)) {
> + tx_delay_step = 0;
> + } else {
> + if (arg <= 2000) {
> + tx_delay_step = (arg == 2000) ? 0xf : (arg / NVT_PATH_DELAY_STEP);
> + dev_dbg(dev, "Set Tx path delay to 0x%x\n", tx_delay_step);
> + } else {
> + dev_err(dev, "Invalid Tx path delay argument.\n");
> + return ERR_PTR(-EINVAL);
> + }
> + }
> + if (of_property_read_u32(dev->of_node, "rx-internal-delay-ps", &arg)) {
> + rx_delay_step = 0;
> + } else {
> + if (arg <= 2000) {
> + rx_delay_step = (arg == 2000) ? 0xf : (arg / NVT_PATH_DELAY_STEP);
> + dev_dbg(dev, "Set Rx path delay to 0x%x\n", rx_delay_step);
> + } else {
> + dev_err(dev, "Invalid Rx path delay argument.\n");
> + return ERR_PTR(-EINVAL);
> + }
> + }
Each of these could be moved into a separate function:
static int nvt_gmac_get_delay(struct device *dev, const char *property)
{
u32 arg;
if (of_property_read_u32(dev->of_node, property, &arg))
return 0;
if (arg > 2000) {
dev_err(dev, "Invalid %s argument.\n", property);
return -EINVAL;
}
if (arg == 2000)
return 15;
return arg / NVT_PATH_DELAY_STEP;
}
then:
int ret;
ret = nvt_gmac_get_delay(dev, "tx-internal-delay-ps");
if (ret < 0)
return ERR_PTR(ret);
tx_delay = ret;
ret = nvt_gmac_get_delay(dev, "rx-internal-delay-ps");
if (ret < 0)
return ERR_PTR(ret);
rx_delay = ret;
> +
> + miscr = (macid == 0) ? NVT_REG_SYS_GMAC0MISCR : NVT_REG_SYS_GMAC1MISCR;
> + regmap_read(bsp_priv->regmap, miscr, ®);
> + reg &= ~(NVT_TX_DELAY_MASK | NVT_RX_DELAY_MASK);
> +
> + if (of_get_phy_mode(pdev->dev.of_node, &phy_mode)) {
> + dev_err(dev, "missing phy mode property\n");
> + return ERR_PTR(-EINVAL);
> + }
> +
> + switch (phy_mode) {
> + case PHY_INTERFACE_MODE_RGMII:
> + case PHY_INTERFACE_MODE_RGMII_ID:
> + case PHY_INTERFACE_MODE_RGMII_RXID:
> + case PHY_INTERFACE_MODE_RGMII_TXID:
> + reg &= ~NVT_MISCR_RMII;
> + break;
> + case PHY_INTERFACE_MODE_RMII:
> + reg |= NVT_MISCR_RMII;
> + break;
> + default:
> + dev_err(dev, "Unsupported phy-mode (%d)\n", phy_mode);
> + return ERR_PTR(-EINVAL);
> + }
> +
> + if (!(reg & NVT_MISCR_RMII)) {
> + reg |= FIELD_PREP(NVT_TX_DELAY_MASK, tx_delay_step);
> + reg |= FIELD_PREP(NVT_RX_DELAY_MASK, rx_delay_step);
You can move this inside the switch above under the RGMII case. Theses
delays are, after all, only for RGMII.
> + }
> +
> + regmap_write(bsp_priv->regmap, miscr, reg);
Consider:
regmap_update_bits(bsp_priv->regmap, miscr,
NVT_TX_DELAY_MASK | NVT_RX_DELAY_MASK |
NVT_MISCR_RMII, reg);
> + plat_dat = devm_stmmac_probe_config_dt(pdev, stmmac_res.mac);
> + if (IS_ERR(plat_dat))
> + return PTR_ERR(plat_dat);
> +
> + /* Nuvoton DWMAC configs */
> + plat_dat->core_type = DWMAC_CORE_GMAC;
Is the hardware not compatible with any of the compatible types that
devm_stmmac_probe_config_dt() will automatically set this for you?
Which version of the core do you have?
> + plat_dat->tx_fifo_size = 2048;
> + plat_dat->rx_fifo_size = 4096;
There are tx-fifo-depth / rx-fifo-depth properties that can be used to
describe these in DT.
> + plat_dat->multicast_filter_bins = 0;
> + plat_dat->unicast_filter_entries = 8;
If this core is v3.50, v3.70 or v3.72, then there are
snps,multicast-filter-bins and snps,perfect-filter-entries which
can be used to describe both of these.
Thanks.
--
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:[~2026-02-05 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 1:40 [PATCH net-next v11 0/3] Add support for Nuvoton MA35D1 GMAC Joey Lu
2026-02-05 1:40 ` [PATCH net-next v11 1/3] dt-bindings: net: nuvoton: Add schema for Nuvoton MA35 family GMAC Joey Lu
2026-02-05 1:40 ` [PATCH net-next v11 2/3] arm64: dts: nuvoton: Add Ethernet nodes Joey Lu
2026-02-05 1:40 ` [PATCH net-next v11 3/3] net: stmmac: dwmac-nuvoton: Add dwmac glue for Nuvoton MA35 family Joey Lu
2026-02-05 9:38 ` Russell King (Oracle) [this message]
2026-02-06 9:53 ` Joey Lu
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=aYRlKk-cCIhqGWX7@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=a0987203069@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=krzk+dt@kernel.org \
--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=openbmc@lists.ozlabs.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=schung@nuvoton.com \
--cc=ychuang3@nuvoton.com \
--cc=yclu4@nuvoton.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