[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<SEYPR06MB5134798B2F2890FF527775FD9D272@SEYPR06MB5134.apcprd06.prod.outlook.com>
Date: Mon, 18 Nov 2024 07:45:52 +0000
From: Jacky Chou <jacky_chou@...eedtech.com>
To: Arnd Bergmann <arnd@...db.de>, "andrew+netdev@...n.ch"
<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"
<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" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject:
回覆: [net-next v2 3/7] net: ftgmac100: Add reset toggling for Aspeed SOCs
Hi Arnd,
Thank you for you reply.
> > }
> >
> > 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.
Agree.
Because it is optional, even if reset line does not exist on other SoCs, it will
not affect the behavior of the code.
Thank you for pointing this out.
I will adjust it to normal probe procedure in next version.
Or I will separate it from Aspeed AST2700 support series.
Jacky
Powered by blists - more mailing lists