This series is basically to deprecate using phy-omap-control and use syscon APIs to program the control module registers. Changes from v2: No changes. Changes from v1: *) cleanup ti_pipe3_probe in multiple steps *) other minor cleanups Changes from [1] in PHY patches include *) cleanup ti_pipe3_probe *) have mask, power_on and power_off values in usb_phy_data for omap-usb2 phy The patches have been pushed to git://git.ti.com/linux-phy/linux-phy.git syscon [1] -> https://lkml.org/lkml/2015/6/23/189 All the testing was done both before applying the dt patches and after applying the dt patches (dt patches will be posted shortly). Logs with SYSCON DT DRA72 EVM : http://pastebin.ubuntu.com/14025205/ DRA7 EVM : http://pastebin.ubuntu.com/14025212/ AM43XX EVM: http://pastebin.ubuntu.com/14025222/ OMAP5 UEVM: http://pastebin.ubuntu.com/14025228/ Logs without SYSCON DT DRA72 EVM : http://pastebin.ubuntu.com/14025233/ DRA7 EVM : http://pastebin.ubuntu.com/14025238/ AM43XX EVM: http://pastebin.ubuntu.com/14025329/ OMAP5 UEVM: http://pastebin.ubuntu.com/14025248/ The config I used: http://pastebin.ubuntu.com/14025336/ Kishon Vijay Abraham I (9): phy: ti-pipe3: introduce local struct device* in probe phy: ti-pipe3: move clk initialization to a separate function phy: ti-pipe3: move sysctrl initialization to a separate function phy: ti-pipe3: move mem resource initialization to a separate function phy: ti-pipe3: use ti_pipe3_power_off to power off the PHY during probe phy: ti-pipe3: use *syscon* framework API to power on/off the PHY phy: ti-pipe3: use *syscon* framework API to set PCS value of the PHY phy: omap-usb2: use omap_usb_power_off to power off the PHY during probe phy: omap-usb2: use *syscon* framework API to power on/off the PHY Documentation/devicetree/bindings/phy/ti-phy.txt | 20 +- drivers/phy/phy-omap-usb2.c | 96 +++++-- drivers/phy/phy-ti-pipe3.c | 304 ++++++++++++++++------ include/linux/phy/omap_usb.h | 23 ++ 4 files changed, 340 insertions(+), 103 deletions(-) -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
