On 20 November 2014 15:22, Vivek Gautam gautamvivek1987@gmail.com wrote:
Hi Javier,
On Thu, Nov 20, 2014 at 2:15 PM, Javier Martinez Canillas javier.martinez@collabora.co.uk wrote:
Hello Vivek,
On 11/20/2014 08:51 AM, Vivek Gautam wrote:
I tested linux-next on Exynos5800 peach-pi board with linux-next and and the two patches $Subject and [0].
Below is my git hash: 4d9e6ee drm/exynos: Move platform drivers registration to module init 4545ed4 POSTED: arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy 36391a5 Add linux-next specific files for 20141119 9b1ced1 Merge branch 'akpm/master' 282497e mm: add strictlimit knob
used exynos_defconfig
Same here.
With this display works for me. Without $Subject patch i get lookup in drm.
I tested with today linux-next (next-20141120) and display is indeed working for me. So it seems that whatever caused the error in the phy-exynos-mipi-video driver reported by Paolo, got fixed recently.
My working git hash is:
65a8d01 arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy a9b43cb drm/exynos: Move platform drivers registration to module init 5b83d7a Add linux-next specific files for 20141120 1172916 mm: add strictlimit knob
I did have to disable CONFIG_SND_SOC_SNOW though, otherwise the kernel did not boot due the issue reported previously by Kevin.
Javier can you tell me your git hash. Was it on yesterday's linux-next ?
In fact, my branch where I could reproduce the phy-exynos-mipi-video issue was not based on yesterday's next but next-20141117. The git hash is:
9fb5d7c arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy f740096 drm/exynos: Move platform drivers registration to module init efefb5c Add linux-next specific files for 20141117 8c944d7 mm: add strictlimit knob
With 3.18-rc5 i could see display on Exynos5800 peach-pi with following git hash:
b6dca11 drm/exynos: dp: Remove support for unused dptx-phy 7cc5c2d ARM: exynos_defconfig: Enable options for display panel support d0aca5e arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy fc14f9c Linux 3.18-rc5 e35c5a2 Merge tag 'armsoc-for-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
I don't need this drm lockup patch with 3.18-rc5 (with exynos_defconfig).
Yes, that works because the commit that caused the Exynos DRM lockup was:
43c0767 ("of/platform: Move platform devices under /sys/devices/platform")
which landed in next-20141105.
Reverting 43c0767 and only applying [0] should have the same effect.
I am checking further with linux-samsung, coz i could see weird behavior as mentioned in [1] with linux-samsun/for-next merged with above git hash.
Great, it should be good to know what caused:
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
This patch has landed in mfd/for-next and linux-next. Without this on kgene/for-next, any driver seeking PMU register via syscon API will fail to get regmap handles.
Thanks, Pankaj Dubey
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
exynos-mipi-video-phy 10040714.video-phy: can't request region for resource [mem 0x10040714-0x1004071f]
The only reason i see this fails is since PMU is now requesting the entire memory region with base 0x10040000. We should convert the mipi-phy pmu register handling too through syscon.
even when I could not reproduce it anymore with today's linux-next.
-- Best Regards Vivek Gautam Samsung R&D Institute, Bangalore India -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html