[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DB8PR04MB6795AE88083D595D275C3B2CE6EB9@DB8PR04MB6795.eurprd04.prod.outlook.com>
Date: Thu, 29 Jul 2021 02:32:02 +0000
From: Joakim Zhang <qiangqing.zhang@....com>
To: Andrew Lunn <andrew@...n.ch>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"shawnguo@...nel.org" <shawnguo@...nel.org>,
"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
"festevam@...il.com" <festevam@...il.com>,
dl-linux-imx <linux-imx@....com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH V2 net-next 5/7] net: fec: add MAC internal delayed clock
feature support
> -----Original Message-----
> From: Andrew Lunn <andrew@...n.ch>
> Sent: 2021年7月28日 22:11
> To: Joakim Zhang <qiangqing.zhang@....com>
> Cc: davem@...emloft.net; kuba@...nel.org; robh+dt@...nel.org;
> shawnguo@...nel.org; s.hauer@...gutronix.de; kernel@...gutronix.de;
> festevam@...il.com; dl-linux-imx <linux-imx@....com>;
> netdev@...r.kernel.org; devicetree@...r.kernel.org;
> linux-kernel@...r.kernel.org
> Subject: Re: [PATCH V2 net-next 5/7] net: fec: add MAC internal delayed clock
> feature support
>
> > + /* For rgmii internal delay, valid values are 0ps and 2000ps */
> > + if (of_property_read_u32(np, "tx-internal-delay-ps", &rgmii_delay))
> > + fep->rgmii_txc_dly = true;
> > + if (of_property_read_u32(np, "rx-internal-delay-ps", &rgmii_delay))
> > + fep->rgmii_rxc_dly = true;
>
> I don't see any validation of the only supported values are 0ps and 2000ps.
Hi Andrew,
I also take this into account, since I have limited the value to 0 and 2000 in fec dt-bindings.
It will report error when run dtbs_check if value is not invalid. Another reason is that actually
the value is not program to hardware, we only enable RGMII delay or not. If need, I think we
can only add a dev_warn() here, instead of stop the probe process?
Best Regards,
Joakim Zhang
> Andrew
Powered by blists - more mailing lists