3.19/for-next: peachpi: phy failures

3.19/for-next: peachpi: phy failures

[Paolo Pisati]

Today's 3.19/for-next regressed on usb (and display panel too) on my samsung
chromebook2 peach pi.

Blindly typing i was able to login and get a dmesg, and this is the relevant
part:

...
[    0.195049] exynos-dp-video-phy 10040728.video-phy: Failed to lookup PMU regmap
[    0.195304] exynos-mipi-video-phy 10040714.video-phy: can't request region for resource [mem 0x10040714-0x1004071f]
[    0.195327] exynos-mipi-video-phy: probe of 10040714.video-phy failed with error -16
[    0.195807] samsung-usb2-phy 12130000.phy: Failed to map PMU registers (via syscon)
[    0.195836] platform 12130000.phy: Driver samsung-usb2-phy requests probe deferral
[    0.196095] exynos5_usb3drd_phy 12100000.phy: Failed to lookup PMU regmap
[    0.196124] platform 12100000.phy: Driver exynos5_usb3drd_phy requests probe deferral
[    0.196196] exynos5_usb3drd_phy 12500000.phy: Failed to lookup PMU regmap
[    0.196222] platform 12500000.phy: Driver exynos5_usb3drd_phy requests probe deferral
...

the funny thing is that usb has always worked fine for me on 318rc4, plus adding
those patches:

d10d142 arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
92dcb9d drm/exynos: dp: Remove support for unused dptx-phy
ddda2b6 ARM: exynos_defconfig: Enable options for display panel support

i got the display to work too (albeit only for fb support, drm
wasn't working yet - that's why i was trying the for-next branch).

Any idea? Has anyone tested for-next on this chromebook?
-- 
bye,
p.