From: sashiko-bot@kernel.org
To: "Artem Shimko" <a.shimko.dev@gmail.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH net-next v6 3/3] net: phy: add DAPU Telecom DAP8211R(I) Gigabit Ethernet PHY driver
Date: Thu, 06 Aug 2026 08:57:04 +0000 [thread overview]
Message-ID: <20260806085705.319D61F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260805085540.452260-4-a.shimko.dev@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] RGMII configuration is written after the PHY software reset, preventing delay settings from taking effect.
--
--- Patch [3]: [PATCH net-next v6 3/3] net: phy: add DAPU Telecom DAP8211R(I) Gigabit Ethernet PHY driver ---
commit 0de15848a30c891806ee2f58213d5a3b6475e080
Author: Artem Shimko <a.shimko.dev@gmail.com>
net: phy: add DAPU Telecom DAP8211R(I) Gigabit Ethernet PHY driver
Add a new PHY driver for the DAPU Telecom DAP8211R(I) Gigabit Ethernet PHY.
This driver implements extended register access and provides device tree
support for RGMII delay configuration.
> diff --git a/drivers/net/phy/dap8211r.c b/drivers/net/phy/dap8211r.c
> new file mode 100644
> --- /dev/null
> +++ b/drivers/net/phy/dap8211r.c
[ ... ]
> +static int dap8211r_config_init(struct phy_device *phydev)
> +{
> + u16 set = 0;
[ ... ]
> + set |= FIELD_PREP(DAP8211R_RGMII_RX_DEL_MASK, rx_internal_delay);
> + set |= FIELD_PREP(DAP8211R_RGMII_TX_DEL_MASK, tx_internal_delay);
> +
> + ret = dap8211r_modify_ext(phydev, DAP8211R_PHY_CON, DAP8211R_PHY_SW_RST, 0);
> + if (ret)
> + return ret;
> +
> + /* Wait for reset self-clear (from low active to high) */
> + ret = read_poll_timeout(dap8211r_read_ext, val,
> + (val & DAP8211R_PHY_SW_RST),
> + 20, 200, false, phydev, DAP8211R_PHY_CON);
> + if (ret)
> + return ret;
> + if (val < 0)
> + return val;
> +
> + ret = dap8211r_modify_ext(phydev, DAP8211R_RGMII_CON, DAP8211R_RGMII_CONFIG_MASK, set);
[Severity: High]
Will these delay settings take effect? The function documentation notes that a
software reset is required to apply the settings, but the RGMII configuration
is written to DAP8211R_RGMII_CON after the software reset has already been
issued and completed.
Should dap8211r_modify_ext() for DAP8211R_RGMII_CON be called before
triggering DAP8211R_PHY_SW_RST so the PHY latches the new delay values?
> + if (ret)
> + return ret;
> +
> + return 0;
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260805085540.452260-1-a.shimko.dev@gmail.com?part=3
next prev parent reply other threads:[~2026-08-06 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 8:55 [PATCH net-next v6 0/3] Add DAPU Telecom DAP8211R(I) Gigabit Ethernet PHY driver Artem Shimko
2026-08-05 8:55 ` [PATCH net-next v6 1/3] dt-bindings: vendor-prefixes: add Guangdong Dapu Telecom Co., Ltd Artem Shimko
2026-08-06 7:20 ` Krzysztof Kozlowski
2026-08-06 9:08 ` Artem Shimko
2026-08-05 8:55 ` [PATCH net-next v6 2/3] dt-bindings: net: add DAPU Telecom DAP8211R(I) PHY binding Artem Shimko
2026-08-06 7:22 ` Krzysztof Kozlowski
2026-08-06 9:09 ` Artem Shimko
2026-08-05 8:55 ` [PATCH net-next v6 3/3] net: phy: add DAPU Telecom DAP8211R(I) Gigabit Ethernet PHY driver Artem Shimko
2026-08-05 12:40 ` Andrew Lunn
2026-08-06 9:07 ` Artem Shimko
2026-08-06 8:57 ` sashiko-bot [this message]
2026-08-06 9:06 ` Artem Shimko
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=20260806085705.319D61F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=a.shimko.dev@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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