From: Vivek gautam <gautam.vivek@xxxxxxxxxxx> Based on 'for-next' branch of Kgene's linux-samsung tree; along with dts patches for USB 2.0 phy[1], and Exynos5800 [2]. Also based on the latest USB 3.0 DRD phy driver patches posted [3]. Changes from v5: - Added node reference names for new boards. - Removed 'samsung,pmu-offset' porperty from nodes, since with latest driver bindings this is not required. - Added aliase nodes in Exynos5420 to facilitate latest driver bindings. - Added patch to add VBUS regulator for peach-pi board also. - Dropped patches removing older usb-phy driver: usb-phy: samsung-usb3: Remove older phy-samsung-usb3 driver ARM: exynos_defconfig: Remove SAMSUNG_USB3PHY config as appeared in V5 version of this series. Will post them separately after the new driver is merged. [1] http://www.spinics.net/lists/linux-samsung-soc/msg30494.html [2] http://comments.gmane.org/gmane.linux.kernel.samsung-soc/31133 [3] https://lkml.org/lkml/2014/5/13/285 Vivek Gautam (7): ARM: dts: exynos5420: Enable support for USB 3.0 PHY controller ARM: dts: exynos5420: Enable support for DWC3 controller ARM: dts: exynos5250: Enable support for generic USB DRD phy ARM: dts: exynos5250: Update DWC3 usb controller to use new phy driver ARM: dts: exynos5250-snow: Add Vbus regulator for USB 3.0 ARM: dts: exynos5420-peach-pit: Add Vbus regulator for USB 3.0 ARM: dts: exynos5420-smdk5420: Add Vbus regulator for USB 3.0 Vivek gautam (1): ARM: dts: exynos5800-peach-pi: Add Vbus regulator for USB 3.0 arch/arm/boot/dts/exynos5250-snow.dts | 22 ++++++++++++ arch/arm/boot/dts/exynos5250.dtsi | 20 +++++------ arch/arm/boot/dts/exynos5420-peach-pit.dts | 46 ++++++++++++++++++++++++ arch/arm/boot/dts/exynos5420-smdk5420.dts | 46 ++++++++++++++++++++++++ arch/arm/boot/dts/exynos5420.dtsi | 54 ++++++++++++++++++++++++++++ arch/arm/boot/dts/exynos5800-peach-pi.dts | 46 ++++++++++++++++++++++++ 6 files changed, 222 insertions(+), 12 deletions(-) -- 1.7.10.4 -- 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
