[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130423080257.GQ32299@pengutronix.de>
Date: Tue, 23 Apr 2013 10:02:57 +0200
From: Sascha Hauer <s.hauer@...gutronix.de>
To: Mugunthan V N <mugunthanvnm@...com>
Cc: netdev@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
linux-omap@...r.kernel.org, davem@...emloft.net
Subject: Re: [net-next PATCH 0/3] Adding phy register fixup in DT
On Mon, Apr 22, 2013 at 11:50:35PM +0530, Mugunthan V N wrote:
> In earlier days phy fixup was added to phy frame work in board files.
> As there won't be any board files here after the same has to be done in DT
> This patch series adds the following features
> * support for adding phy resigter fixup via DT
> * adds phy id for EVMsk n DTS file
> * adds phy fixup for AM335x EVM and EVMsk
>
> Mugunthan V N (3):
> drivers: of: add phy fixup support in DT
> ARM: dts: AM33XX: Add CPSW phy_id device tree data to am335x-evmsk
> ARM: dts: AM33XX: add phy fixup for evm and evmsk boards
I generally do not offend to phy fixups from the devicetree. I see
though that becomes more and more common that we have to configure
the tx delays in phys.
The current way seems to be to hardcode register values for each board
which seems not very flexible and forces us to read phy datasheets
each time for a new board.
Wouldn't it make more sense to configure the actual delays (in ns) and
let the phy drivers figure out how to turn this into register values?
Not that I volunteer to write such things... :-/
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 |
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists