From: sashiko-bot@kernel.org
To: "James Hilliard" <james.hilliard1@gmail.com>
Cc: lee@kernel.org, robh@kernel.org, devicetree@vger.kernel.org,
mfd@lists.linux.dev, conor+dt@kernel.org
Subject: Re: [PATCH net-next v3 4/4] net: phy: add X-Powers AC200/AC300 EPHY driver
Date: Fri, 07 Aug 2026 01:25:51 +0000 [thread overview]
Message-ID: <20260807012552.396BE1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260805-submit-acx00-of-dynamic-v1-v3-4-32c3210a6f25@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Missing `phy_restore_page()` on the error path of `phy_select_page()` leaves the MDIO bus permanently locked.
--
--- Patch [4]: [PATCH net-next v3 4/4] net: phy: add X-Powers AC200/AC300 EPHY driver ---
commit fc0883818634a8eab77474550b0a3aac9604dc17
Author: James Hilliard <james.hilliard1@gmail.com>
net: phy: add X-Powers AC200/AC300 EPHY driver
This commit introduces a new Ethernet PHY driver for the X-Powers AC200
and AC300 companion ICs. It provides package-specific I2C or MDIO control
initialization and implements the standard PHY driver callbacks.
> diff --git a/drivers/net/phy/xpowers-acx00-main.c b/drivers/net/phy/xpowers-acx00-main.c
> new file mode 100644
> index 0000000000000..2260ddea4b315
> --- /dev/null
> +++ b/drivers/net/phy/xpowers-acx00-main.c
[ ... ]
> @@ -0,0 +1,536 @@
[ ... ]
> +static int acx00_ephy_config_init(struct phy_device *phydev)
> +{
[ ... ]
> + if (priv->is_ac300 && priv->use_low_calibration_tuning) {
> + afe_eq_rx_detect =
> + ACX00_PAGE6_AFE_EQ_RX_DETECT_LOW_CAL_VALUE;
> + tx_level_value = ACX00_PAGE6_TX_LEVEL_LOW_CAL_VALUE;
> + }
> +
> + oldpage = phy_select_page(phydev, ACX00_PAGE_1);
> + if (oldpage < 0)
> + return oldpage;
[Severity: High]
Does this error path leave the MDIO bus permanently locked?
Looking at phy_select_page(), it holds the MDIO bus lock even when returning
a negative error code so that the caller can safely clean up. Since this path
returns directly instead of jumping to the out_restore_page label, could this
result in an unrecoverable deadlock for any future accesses on the same bus?
> +
> + ret = __phy_write(phydev, ACX00_PAGE1_APS_CONTROL_REG,
> + ACX00_PAGE1_APS_DISABLED_4S_VALUE);
> + if (ret)
> + goto out_restore_page;
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260805-submit-acx00-of-dynamic-v1-v3-0-32c3210a6f25@gmail.com?part=4
next prev parent reply other threads:[~2026-08-07 1:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 1:24 [PATCH net-next v3 0/4] net: phy: add X-Powers AC200/AC300 EPHY support James Hilliard
2026-08-06 1:24 ` [PATCH net-next v3 1/4] dt-bindings: mfd: x-powers: add AC200 James Hilliard
2026-08-06 9:34 ` Jagielski, Jedrzej
2026-08-07 1:24 ` sashiko-bot
2026-08-06 1:24 ` [PATCH net-next v3 2/4] mfd: add X-Powers AC200 support James Hilliard
2026-08-07 1:25 ` sashiko-bot
2026-08-06 1:24 ` [PATCH net-next v3 3/4] dt-bindings: net: x-powers: add AC200/AC300 EPHY packages James Hilliard
2026-08-07 1:25 ` sashiko-bot
2026-08-06 1:24 ` [PATCH net-next v3 4/4] net: phy: add X-Powers AC200/AC300 EPHY driver James Hilliard
2026-08-07 1:25 ` sashiko-bot [this message]
2026-08-06 9:18 ` [PATCH net-next v3 0/4] net: phy: add X-Powers AC200/AC300 EPHY support Jagielski, Jedrzej
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=20260807012552.396BE1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=james.hilliard1@gmail.com \
--cc=lee@kernel.org \
--cc=mfd@lists.linux.dev \
--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