From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from metis.ext.pengutronix.de ([92.198.50.35]:57105 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753615Ab3HVGfI (ORCPT ); Thu, 22 Aug 2013 02:35:08 -0400 Date: Thu, 22 Aug 2013 08:34:48 +0200 From: Sascha Hauer Subject: Re: [RFC] phy: micrel: Convert micrel PHY driver to use OF Message-ID: <20130822063448.GS31036@pengutronix.de> References: <1376412156-3899-1-git-send-email-dinguyen@altera.com> <20130822051347.GD5151@quad.lixom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130822051347.GD5151@quad.lixom.net> Sender: devicetree-owner@vger.kernel.org To: Olof Johansson Cc: dinguyen@altera.com, dinh.linux@gmail.com, netdev@vger.kernel.org, Richard Cochran , Linus Walleij , Felipe Balbi , "David S. Miller" , Giuseppe Cavallaro , Rob Herring , devicetree@vger.kernel.org List-ID: On Wed, Aug 21, 2013 at 10:13:47PM -0700, Olof Johansson wrote: > (adding devicetree@vger.kernel.org) > > > On Tue, Aug 13, 2013 at 11:42:36AM -0500, dinguyen@altera.com wrote: > > --- > > Hello, > > > > I would like to solicit comments on the need to convert the ethernet PHY > > drivers to use OF/device trees? For the platform that I'm interested in, > > SOCFPGA, it is using the stmicro ethernet driver. It has a Micrel PHY > > on the board. The only way that I know of how to change the skew settings > > for the phy is through a board level initialization. > > > > One of the ARM maintainers suggested that perhaps refactoring the ethernet > > driver to use device tree would be nice. But that would not help me with > > configuring the PHY settings. > > > > So a little investigation led me to believe that refactoring the /net/phy > > drivers into a device tree implementation would help greatly. I was thinking > > it could be done like the pinctrl or some of the usb/phy driver. > > > > Since I am only familiar with the ARM SoC space, I want to make sure that > > this idea is right approach. I can start with the micrel PHY driver > > first, as that is the only HW I have access to. > > Hi, > > Sorry for the slow reply here. > > I don't think this is quite the right approach. > > What you want to do is to make the phy devices register based on device tree > contents, which also means removing the run function, or rather moving it to > a generic run function in the phy subsystem that acts based on device tree > contents instead of a hard-coded per-board run function. > > It sounds like defining that binding might end up getting complicated. > I suggest you consider recruiting some of the more seasoned devicetree folks on > this endeavor. > > It's possible that you'll mostly have per-vendor/phy type properties to tune > the various settings, but it's also likely that you will have some generic and > shared (optional) properties such as gpios for resetting, or regulators for > powering, the phy. This patch recently was merged: http://patchwork.ozlabs.org/patch/268661/ It solves exactly the same problem of specifying the skew settings. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |