Florian, Any word on version 2 of this series? I'd like to base the conversion of kirkwood to DT based ethernet init on it. thx, Jason. On Tue, Jan 29, 2013 at 04:24:03PM +0100, Florian Fainelli wrote: > Hi all, > > This patch converts the mv643xx_eth driver to use the mvmdio MDIO bus driver > instead of rolling its own implementation. As a result, all users of this > mv643xx_eth driver are converted to register an "orion-mdio" platform_device. > The mvmdio driver is also updated to support an interrupt line which reports > SMI error/completion, and to allow traditionnal platform device registration > instead of just device tree. > > David, I think it makes sense for you to merge all of this, since we do > not want the architecture files to be desynchronized from the mv643xx_eth to > avoid runtime breakage. The potential for merge conflicts should be very small. > > You can probably safely merge patches 1 to 4 if Thomas agrees, and we will > see what kind of feeback I get on patch 5. > > Florian Fainelli (5): > net: mvmdio: unmap base register address at driver removal > net: mvmdio: rename base register cookie from smireg to regs > net: mvmdio: enhance driver to support SMI error/done interrupts > net: mvmdio: allow Device Tree and platform device to coexist > mv643xx_eth: convert to use the Marvell Orion MDIO driver > > .../devicetree/bindings/net/marvell-orion-mdio.txt | 3 + > arch/arm/plat-orion/common.c | 84 +++++++-- > arch/powerpc/platforms/chrp/pegasos_eth.c | 20 +++ > arch/powerpc/sysdev/mv64x60_dev.c | 14 +- > drivers/net/ethernet/marvell/Kconfig | 1 + > drivers/net/ethernet/marvell/mv643xx_eth.c | 187 +------------------- > drivers/net/ethernet/marvell/mvmdio.c | 136 +++++++++++--- > 7 files changed, 226 insertions(+), 219 deletions(-) > > -- > 1.7.10.4 > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
