Hi, Till now we were modelling the RESET line as a voltage regulator and using the regulator framework to manage it. [1] introduces a GPIO based reset controller driver. We use that to manage the PHY reset line, at least for DT boots. For legacy boots, will still need to use the regulator framework for reset lines. Felipe, The first patch is for you. The Kconfig change might conflict if you apply this on top of my PHY Kconfig cleanup series. Benoit, Patches 2 to 6 are for you. NOTE: All patches depend on [1] which is yet to be merged in. cheers, -roger [1] - http://thread.gmane.org/gmane.linux.drivers.devicetree/41348 Roger Quadros (6): usb: phy-nop: Use RESET Controller for managing the reset line ARM: dts: omap3-beagle: Use reset-gpio driver for hsusb2_reset ARM: dts: omap4-panda: Use reset-gpio driver for hsusb1_reset ARM: dts: omap5-uevm: Use reset-gpio driver for hsusb2_reset ARM: dts: omap3-beagle-xm: Add USB Host support ARM: dts: omap3-beagle: Make USB host pin naming consistent .../devicetree/bindings/usb/usb-nop-xceiv.txt | 10 ++- arch/arm/boot/dts/omap3-beagle-xm.dts | 75 +++++++++++++++++--- arch/arm/boot/dts/omap3-beagle.dts | 41 +++++------ arch/arm/boot/dts/omap4-panda-common.dtsi | 22 ++---- arch/arm/boot/dts/omap5-uevm.dts | 17 ++--- drivers/usb/phy/Kconfig | 1 + drivers/usb/phy/phy-nop.c | 48 ++++++++++--- 7 files changed, 146 insertions(+), 68 deletions(-) -- 1.7.4.1 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
