[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <6a7570d0-2b3d-4403-afb1-f95433ad6ecb@app.fastmail.com>
Date: Mon, 18 Nov 2024 07:32:03 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Jacky Chou" <jacky_chou@...eedtech.com>, andrew+netdev@...n.ch,
"David S . Miller" <davem@...emloft.net>,
"Eric Dumazet" <edumazet@...gle.com>, "Jakub Kicinski" <kuba@...nel.org>,
"Paolo Abeni" <pabeni@...hat.com>, "Rob Herring" <robh@...nel.org>,
krzk+dt@...nel.org, "Conor Dooley" <conor+dt@...nel.org>,
"Philipp Zabel" <p.zabel@...gutronix.de>, Netdev <netdev@...r.kernel.org>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [net-next v2 3/7] net: ftgmac100: Add reset toggling for Aspeed SOCs
On Mon, Nov 18, 2024, at 07:02, Jacky Chou wrote:
> @@ -1969,10 +1971,29 @@ static int ftgmac100_probe(struct platform_device *pdev)
> }
>
> if (priv->is_aspeed) {
> + struct reset_control *rst;
> +
> err = ftgmac100_setup_clk(priv);
> if (err)
> goto err_phy_connect;
>
> + rst = devm_reset_control_get_optional(priv->dev, NULL);
> + if (IS_ERR(rst))
> + goto err_register_netdev;
> + priv->rst = rst;
> +
> + err = reset_control_assert(priv->rst);
Since that reset line is optional, how about making it
part of the normal probe procedure, not just the if(aspeed)
section? It seems this does nothing for older devices but
may help for future ones regardless of the SoC family.
Arnd
Powered by blists - more mailing lists