From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: weishangjuan@eswincomputing.com
Cc: devicetree@vger.kernel.org, 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, linux-arm-kernel@lists.infradead.org,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
yong.liang.choong@linux.intel.com, vladimir.oltean@nxp.com,
faizal.abdul.rahim@linux.intel.com,
prabhakar.mahadev-lad.rj@bp.renesas.com, inochiama@gmail.com,
jan.petrous@oss.nxp.com, jszhang@kernel.org,
p.zabel@pengutronix.de, boon.khai.ng@altera.com,
0x1207@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
emil.renner.berthing@canonical.com, ningyu@eswincomputing.com,
linmin@eswincomputing.com, lizhi2@eswincomputing.com,
pinkesh.vaghela@einfochips.com
Subject: Re: [PATCH v5 2/2] ethernet: eswin: Add eic7700 ethernet driver
Date: Thu, 4 Sep 2025 11:26:24 +0100 [thread overview]
Message-ID: <aLlpUOr3IJzTuV1g@shell.armlinux.org.uk> (raw)
In-Reply-To: <20250904090125.2598-1-weishangjuan@eswincomputing.com>
On Thu, Sep 04, 2025 at 05:01:25PM +0800, weishangjuan@eswincomputing.com wrote:
> +struct eic7700_qos_priv {
> + struct plat_stmmacenet_data *plat_dat;
> + struct device *dev;
> + struct regmap *hsp_regmap;
> + u32 tx_delay_ps;
> + u32 rx_delay_ps;
> +};
> +
> +/**
> + * eic7700_apply_delay - Apply TX or RX delay to a register value.
> + * @delay_ps: Delay in picoseconds, converted to 0.1ns units.
> + * @reg: Pointer to register value to update in-place.
> + * @is_rx: True for RX delay (bits 30:24), false for TX delay (bits 14:8).
> + *
> + * Converts delay from ps to 0.1ns units, capped by EIC7700_MAX_DELAY_UNIT.
> + * Updates only the RX or TX delay field (using FIELD_PREP), leaving all
> + * other bits in *@reg unchanged.
> + */
> +static void eic7700_apply_delay(u32 delay_ps, u32 *reg, bool is_rx)
> +{
> + u32 val = min(delay_ps / 100, EIC7700_MAX_DELAY_UNIT);
> +
> + if (is_rx) {
> + *reg &= ~EIC7700_ETH_RX_ADJ_DELAY;
> + *reg |= FIELD_PREP(EIC7700_ETH_RX_ADJ_DELAY, val);
> + } else {
> + *reg &= ~EIC7700_ETH_TX_ADJ_DELAY;
> + *reg |= FIELD_PREP(EIC7700_ETH_TX_ADJ_DELAY, val);
> + }
> +}
...
> + /* Read rx-internal-delay-ps and update rx_clk delay */
> + if (!of_property_read_u32(pdev->dev.of_node,
> + "rx-internal-delay-ps",
> + &dwc_priv->rx_delay_ps)) {
> + eic7700_apply_delay(dwc_priv->rx_delay_ps,
> + ð_dly_param, true);
I've been trying to figure out the reasoning behind the following:
1. the presence of dwc_priv->rx_delay_ps and dwc_priv->tx_delay_ps
rather than just using a local variable ("delay" ?)
2. the presence of eic7700_apply_delay() when we have to do something
different to get the delay value anyway
It seems to me that this should either be:
static void eic7700_parse_delay(u32 *reg, struct device *dev,
const char *name, bool is_rx)
{
u32 delay;
if (of_property_read_u32(dev->of_node, name, &delay)) {
dev_warn(dev, "can't get %s\n", name);
return
}
if (is_rx) {
*reg &= ~EIC7700_ETH_RX_ADJ_DELAY;
*reg |= FIELD_PREP(EIC7700_ETH_RX_ADJ_DELAY, delay);
} else {
*reg &= ~EIC7700_ETH_TX_ADJ_DELAY;
*reg |= FIELD_PREP(EIC7700_ETH_TX_ADJ_DELAY, delay);
}
}
or just not bother with the function at all and just write it out
fully in the probe function.
Thanks.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
prev parent reply other threads:[~2025-09-04 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 8:59 [PATCH v5 0/2] Add driver support for Eswin eic7700 SoC ethernet controller weishangjuan
2025-09-04 9:00 ` [PATCH v5 1/2] dt-bindings: ethernet: eswin: Document for EIC7700 SoC weishangjuan
2025-09-05 7:53 ` Krzysztof Kozlowski
2025-09-04 9:01 ` [PATCH v5 2/2] ethernet: eswin: Add eic7700 ethernet driver weishangjuan
2025-09-04 10:26 ` Russell King (Oracle) [this message]
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=aLlpUOr3IJzTuV1g@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=0x1207@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=boon.khai.ng@altera.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=emil.renner.berthing@canonical.com \
--cc=faizal.abdul.rahim@linux.intel.com \
--cc=inochiama@gmail.com \
--cc=jan.petrous@oss.nxp.com \
--cc=jszhang@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linmin@eswincomputing.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lizhi2@eswincomputing.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ningyu@eswincomputing.com \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=pinkesh.vaghela@einfochips.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=vladimir.oltean@nxp.com \
--cc=weishangjuan@eswincomputing.com \
--cc=yong.liang.choong@linux.intel.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).