Hi Rahul,
On 22 May 2014 19:41, Rahul Sharma wrote:
> Fimd probe is accessing fimd Registers without enabling the fimd
> gate clocks. If FIMD clocks are kept disabled in Uboot or disbaled
> during kernel boottime, the system hangs during boottime.
>
> This issue got surfaced when verifying with s
Fimd probe is accessing fimd Registers without enabling the fimd
gate clocks. If FIMD clocks are kept disabled in Uboot or disbaled
during kernel boottime, the system hangs during boottime.
This issue got surfaced when verifying with sysmmu enabled. Probe of
fimd Sysmmu enables the master clock be
;> > samsung.com;
>> > linaro-kernel at lists.linaro.org; linux-media at vger.kernel.org
>> > Subject: Re: [PATCH v3] drm/exynos: enable FIMD clocks
>> >
>> > On 1 April 2013 14:13, Vikas Sajjan wrote:
>> > > While migrating to common clock f
-samsung-soc at vger.kernel.org;
> jy0922.shim at samsung.com; inki.dae at samsung.com; kgene.kim at samsung.com;
> linaro-kernel at lists.linaro.org; linux-media at vger.kernel.org
> Subject: Re: [PATCH v3] drm/exynos: enable FIMD clocks
>
> On 1 April 2013 14:13, Vikas Sajjan wrote:
>
PM
> > To: Vikas Sajjan
> > Cc: dri-devel at lists.freedesktop.org; linux-samsung-soc at
> > vger.kernel.org;
> > jy0922.shim at samsung.com; inki.dae at samsung.com; kgene.kim at
> > samsung.com;
> > linaro-kernel at lists.linaro.org; linux-media at vger.ker
iresh.ku...@linaro.org]
>> > Sent: Monday, April 01, 2013 5:51 PM
>> > To: Vikas Sajjan
>> > Cc: dri-devel@lists.freedesktop.org; linux-samsung-...@vger.kernel.org;
>> > jy0922.s...@samsung.com; inki@samsung.com; kgene@samsung.com;
>> > linaro-ker
PM
> > To: Vikas Sajjan
> > Cc: dri-devel@lists.freedesktop.org; linux-samsung-...@vger.kernel.org;
> > jy0922.s...@samsung.com; inki@samsung.com; kgene@samsung.com;
> > linaro-ker...@lists.linaro.org; linux-me...@vger.kernel.org
> > Subject: Re: [PATCH v3] drm/exy
vger.kernel.org;
> jy0922.s...@samsung.com; inki@samsung.com; kgene@samsung.com;
> linaro-ker...@lists.linaro.org; linux-me...@vger.kernel.org
> Subject: Re: [PATCH v3] drm/exynos: enable FIMD clocks
>
> On 1 April 2013 14:13, Vikas Sajjan wrote:
> > While migrating to comm
On 1 April 2013 14:13, Vikas Sajjan wrote:
> While migrating to common clock framework (CCF), found that the FIMD clocks
s/found/we found/
> 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.
>
>
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.
this patc
On 1 April 2013 14:13, Vikas Sajjan wrote:
> While migrating to common clock framework (CCF), found that the FIMD clocks
s/found/we found/
> 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.
>
>
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.
this patc
12 matches
Mail list logo
