[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171107155947.GC18410@lunn.ch>
Date: Tue, 7 Nov 2017 16:59:47 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Vladimir Zapolskiy <vladimir_zapolskiy@...tor.com>
Cc: Chris Zhong <zyw@...k-chips.com>,
Sergei Shtylyov <sergei.shtylyov@...entembedded.com>,
Roger Quadros <rogerq@...com>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, heiko@...ech.de,
netdev@...r.kernel.org, Russell King <linux@...linux.org.uk>,
linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org,
Rob Herring <robh+dt@...nel.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] ARM: dts: add phy-reset property for rk3066a-rayeager
emac
> As a side question, which is mainly addressed to Sergei and Roger,
> I don't quite understand why PHY properties were initially added to
> MAC/MDIO bus device tree nodes, in my opinion they must be moved under
> PHY device tree nodes.
If you look at the implementation, they are not actually PHY
properties. They are MDIO properties. It is the MDIO driver using them
to perform an 'MDIO bus reset'. The property names are wrong.
The device tree structure could be better. It mixes the MAC and the
MDIO properties in the same node. It would of been better to have
separate nodes.
The MDIO core now has equivalent functionality. So yes, it would be
better to use the generic MDIO properties, not these driver
properties.
Andrew
Powered by blists - more mailing lists