From: Simon Horman <horms@kernel.org>
To: jacky_chou@aspeedtech.com
Cc: Simon Horman <horms@kernel.org>,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, andrew+netdev@lunn.ch,
netdev@vger.kernel.org
Subject: Re: [net-next,v2,06/15] net: ftgmac100: Use devm_clk_get_enabled
Date: Tue, 20 Jan 2026 12:19:39 +0000 [thread overview]
Message-ID: <20260120121939.795771-1-horms@kernel.org> (raw)
In-Reply-To: <20260116-ftgmac-cleanup-v2-6-81f41f01f2a8@aspeedtech.com>
This is an AI-generated review of your patch. The human sending this
email has considered the AI review valid, or at least plausible.
For local reproduction steps see https://netdev-ai.bots.linux.dev/ai-local.html
---
net: ftgmac100: Use devm_clk_get_enabled
This patch converts the ftgmac100 driver to use devm_clk_get_enabled()
and devm_clk_get_optional_enabled() to simplify clock management and
cleanup paths.
> diff --git a/drivers/net/ethernet/faraday/ftgmac100.c b/drivers/net/ethernet/faraday/ftgmac100.c
> index ec2e7ec23ddf..ffd86655bcc8 100644
> --- a/drivers/net/ethernet/faraday/ftgmac100.c
> +++ b/drivers/net/ethernet/faraday/ftgmac100.c
> @@ -1801,13 +1801,10 @@ static int ftgmac100_setup_clk(struct ftgmac100 *priv)
> struct clk *clk;
> int rc;
>
> - clk = devm_clk_get(priv->dev, NULL /* MACCLK */);
> + clk = devm_clk_get_enabled(priv->dev, NULL /* MACCLK */);
> if (IS_ERR(clk))
> return PTR_ERR(clk);
> priv->clk = clk;
> - rc = clk_prepare_enable(priv->clk);
> - if (rc)
> - return rc;
>
> /* Aspeed specifies a 100MHz clock is required for up to
> * 1000Mbit link speeds. As NCSI is limited to 100Mbit, 25MHz
> @@ -1816,21 +1813,15 @@ static int ftgmac100_setup_clk(struct ftgmac100 *priv)
> rc = clk_set_rate(priv->clk, priv->use_ncsi ? FTGMAC_25MHZ :
> FTGMAC_100MHZ);
> if (rc)
> - goto cleanup_clk;
> + return rc;
>
> /* RCLK is for RMII, typically used for NCSI. Optional because it's not
> * necessary if it's the AST2400 MAC, or the MAC is configured for
> * RGMII, or the controller is not an ASPEED-based controller.
> */
> - priv->rclk = devm_clk_get_optional(priv->dev, "RCLK");
> - rc = clk_prepare_enable(priv->rclk);
> - if (!rc)
> - return 0;
> + priv->rclk = devm_clk_get_optional_enabled(priv->dev, "RCLK");
>
> -cleanup_clk:
> - clk_disable_unprepare(priv->clk);
> -
> - return rc;
> + return 0;
> }
Should the return value of devm_clk_get_optional_enabled() be checked
here? The old code would fail probe if RCLK existed but
clk_prepare_enable() failed. The new code unconditionally returns 0,
ignoring any potential error from devm_clk_get_optional_enabled().
Looking at other drivers using this API, most check for IS_ERR(). For
example, cctrng_probe() in drivers/char/hw_random/cctrng.c does:
drvdata->clk = devm_clk_get_optional_enabled(dev, NULL);
if (IS_ERR(drvdata->clk))
return dev_err_probe(...);
While the clock is optional (may not exist), if it does exist but fails
to enable, this seems like a condition that should cause probe to fail
rather than succeed silently?
[ ... ]
--
pw-bot: changes-requested
next prev parent reply other threads:[~2026-01-20 12:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 2:09 [PATCH net-next v2 00/15] net: ftgmac100: Various probe cleanups Jacky Chou
2026-01-16 2:09 ` [PATCH net-next v2 01/15] net: ftgmac100: List all compatibles Jacky Chou
2026-01-16 2:09 ` [PATCH net-next v2 02/15] net: ftgmac100: Add match data containing MAC ID Jacky Chou
2026-01-16 2:09 ` [PATCH net-next v2 03/15] net: ftgmac100: Replace all of_device_is_compatible() Jacky Chou
2026-01-16 2:09 ` [PATCH net-next v2 04/15] net: ftgmac100: Use devm_alloc_etherdev() Jacky Chou
2026-01-16 2:09 ` [PATCH net-next v2 05/15] net: ftgmac100: Use devm_request_memory_region/devm_ioremap Jacky Chou
2026-01-16 2:09 ` [PATCH net-next v2 06/15] net: ftgmac100: Use devm_clk_get_enabled Jacky Chou
2026-01-20 12:19 ` Simon Horman [this message]
2026-01-22 5:37 ` [net-next,v2,06/15] " Jacky Chou
2026-01-16 2:09 ` [PATCH net-next v2 07/15] net: ftgmac100: Simplify error handling for ftgmac100_initial_mac Jacky Chou
2026-01-16 2:09 ` [PATCH net-next v2 08/15] net: ftgmac100: Move NCSI probe code into a helper Jacky Chou
2026-01-16 2:09 ` [PATCH net-next v2 09/15] net: ftgmac100: Always register the MDIO bus when it exists Jacky Chou
2026-01-20 12:14 ` [net-next,v2,09/15] " Simon Horman
2026-01-20 12:21 ` Simon Horman
2026-01-20 14:08 ` Andrew Lunn
2026-01-22 7:31 ` Jacky Chou
2026-01-22 13:40 ` Andrew Lunn
2026-01-24 19:31 ` Andrew Lunn
2026-01-29 6:07 ` Jacky Chou
2026-01-29 13:06 ` Andrew Lunn
2026-02-02 5:29 ` Jacky Chou
2026-01-16 2:09 ` [PATCH net-next v2 10/15] net: ftgmac100: Simplify legacy MDIO setup Jacky Chou
2026-01-16 2:09 ` [PATCH net-next v2 11/15] net: ftgmac100: Move DT probe into a helper Jacky Chou
2026-01-16 2:09 ` [PATCH net-next v2 12/15] net: ftgmac100: Remove redundant PHY_POLL Jacky Chou
2026-01-16 2:09 ` [PATCH net-next v2 13/15] net: ftgmac100: Simplify error handling for ftgmac100_setup_mdio Jacky Chou
2026-01-16 2:09 ` [PATCH net-next v2 14/15] net: ftgmac100: Simplify condition on HW arbitration Jacky Chou
2026-01-16 2:09 ` [PATCH net-next v2 15/15] net: ftgmac100: Fix wrong netif_napi_del in release Jacky Chou
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=20260120121939.795771-1-horms@kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jacky_chou@aspeedtech.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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