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
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
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
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
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
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.
>
>
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
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
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
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.
>
>
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
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
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
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.
>
>
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
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
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
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.
>
>
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
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
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
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.
>
>
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
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
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
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.
>
>
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
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
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
30 matches
Mail list logo
