Hello Paolo,
On 11/20/2014 04:57 PM, Paolo Pisati wrote:
On Thu, Nov 20, 2014 at 03:22:23PM +0530, Vivek Gautam wrote:
On linux-samsung tree the only patch that's missing apart from dptx-phy patches is the syscon patch from Pankaj Dubey: b784b98 mfd: syscon: Decouple syscon interface from platform devices
So with below git hash, linux-samsung/for-next display works fine along with other devices that request PMU system controller :
7bd219e drm/exynos: dp: Remove support for unused dptx-phy e8f21fd arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy 7099bde Revert "Revert "ARM: exynos_defconfig: Enable options for display panel support"" 713a994 mfd: syscon: Decouple syscon interface from platform devices 7552917 Revert "ARM: exynos_defconfig: Enable options for display panel support" /* This is Kukjin's for-next today */ ff0391a Merge branch 'v3.19-samsung-defconfig' into for-next 26c6283 Merge branch 'v3.18-samsung-fixes' into for-next cf864fd Merge branch 'v3.18-samsung-defconfig' into for-next 98b6380 ARM: exynos_defconfig: Enable max77802 rtc and clock drivers 839275c ARM: exynos_defconfig: Use 16 minors per MMC block device 0526f27 ARM: dts: Explicitly set dr_mode on exynos5250-snow fc14f9c Linux 3.18-rc5
are you using a clean exynos_defconfig? don't you need Javier's "drm/exynos: Move platform drivers registration to module init" patch too?
Since Kukjin's for-next is based on Linux 3.18-rc5, the OF patch that causes the Exynos DRM deadlock is not there. That commit landed in next20141105.
kgene/for-next at:
7552917 Revert "ARM: exynos_defconfig: Enable options for display panel support"
plus:
5e1e068 arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy 36d908e drm/exynos: dp: Remove support for unused dptx-phy 624bff2 POSTED: mfd: syscon: Decouple syscon interface from syscon devices 68944e3 Revert "Revert "ARM: exynos_defconfig: Enable options for display panel support""
hangs with a black screen (albeit backlight seems to be on) on boot. I'm betting on Javier's patch at this point (i even tried disabling SND_SOC_SNOW but that didn't help).
I only tested with next20141120 but Vivek tested with Kukjin for-next AFAIU.
What's your kernel command line and u-boot env vars?
Best regards, Javier