[PATCH] drm/exynos: enable fimd clocks in probe before accessing fimd registers

2014-04-20 Thread Rahul Sharma
From: Rahul Sharma Fimd probe is accessing fimd Registers without enabling the fimd gate clocks. This hangs the system at boot time. This issue got surfaced when verifying with sysmmu enabled. Probe of fimd Sysmmu enables the master clock before accessing sysmmu regs and then disables. Later fim

[PATCH] drm/exynos: enable FIMD clocks

2013-03-19 Thread Sachin Kamat
On 19 March 2013 15:29, Vikas Sajjan wrote: > While migrating to common clock framework (CCF), found that the FIMD clocks > were pulled down by the CCF. > If CCF finds any clock(s) which has NOT been claimed by any of the > drivers, then such clock(s) are PULLed low by CCF. > > By calling clk_prep

[PATCH] drm/exynos: enable FIMD clocks

2013-03-19 Thread Viresh Kumar
On 19 March 2013 15:29, Vikas Sajjan wrote: > While migrating to common clock framework (CCF), found that the FIMD clocks > were pulled down by the CCF. > If CCF finds any clock(s) which has NOT been claimed by any of the > drivers, then such clock(s) are PULLed low by CCF. > > By calling clk_prep

[PATCH] drm/exynos: enable FIMD clocks

2013-03-19 Thread Vikas Sajjan
While migrating to common clock framework (CCF), found that the FIMD clocks were pulled down by the CCF. If CCF finds any clock(s) which has NOT been claimed by any of the drivers, then such clock(s) are PULLed low by CCF. By calling clk_prepare_enable() for FIMD clocks fixes the issue. Signed-of

Re: [PATCH] drm/exynos: enable FIMD clocks

2013-03-19 Thread Sachin Kamat
On 19 March 2013 15:29, Vikas Sajjan wrote: > While migrating to common clock framework (CCF), found that the FIMD clocks > were pulled down by the CCF. > If CCF finds any clock(s) which has NOT been claimed by any of the > drivers, then such clock(s) are PULLed low by CCF. > > By calling clk_prep

Re: [PATCH] drm/exynos: enable FIMD clocks

2013-03-19 Thread Viresh Kumar
On 19 March 2013 15:29, Vikas Sajjan wrote: > While migrating to common clock framework (CCF), found that the FIMD clocks > were pulled down by the CCF. > If CCF finds any clock(s) which has NOT been claimed by any of the > drivers, then such clock(s) are PULLed low by CCF. > > By calling clk_prep

[PATCH] drm/exynos: enable FIMD clocks

2013-03-19 Thread Vikas Sajjan
While migrating to common clock framework (CCF), found that the FIMD clocks were pulled down by the CCF. If CCF finds any clock(s) which has NOT been claimed by any of the drivers, then such clock(s) are PULLed low by CCF. By calling clk_prepare_enable() for FIMD clocks fixes the issue. Signed-of