[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200227185526.GE1686232@kwain>
Date: Thu, 27 Feb 2020 19:55:26 +0100
From: Antoine Tenart <antoine.tenart@...tlin.com>
To: Quentin Schulz <foss@...il.net>
Cc: Antoine Tenart <antoine.tenart@...tlin.com>, davem@...emloft.net,
andrew@...n.ch, f.fainelli@...il.com, hkallweit1@...il.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 3/3] net: phy: mscc: implement RGMII skew delay
configuration
Hi Quentin,
On Thu, Feb 27, 2020 at 05:21:58PM +0100, Quentin Schulz wrote:
> On 2020-02-27 16:28, Antoine Tenart wrote:
> >
> > + if (of_find_property(dev->of_node, "vsc8584,rgmii-skew-rx", NULL) ||
> > + of_find_property(dev->of_node, "vsc8584,rgmii-skew-tx", NULL)) {
> > + of_property_read_u32(dev->of_node, "vsc8584,rgmii-skew-rx",
> > &skew_rx);
> > + of_property_read_u32(dev->of_node, "vsc8584,rgmii-skew-tx",
> > &skew_tx);
> > +
>
> Reading the code, I think **!**of_property_read_u32 could directly replace
> of_find_property in your condition and spare you two calls to that function.
Sure.
> Final nitpick: I would see a check of the skew_rx/tx from DT before you put
> them in the following line, they could be drastically different from 0-8
> value set that you expect considering you're reading a u32 (pass them
> through a GENMASK at least?)
That makes sense, I can add a check.
Thanks,
Antoine
--
Antoine Ténart, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Powered by blists - more mailing lists