Hello,
On 03/16/2015 03:16 PM, Javier Martinez Canillas wrote:
> Andrzej,
>
> I looked at the Exynos5250 manual and I didn't find anything obvious
> that is missing in the DISP1 pd dev node but the asynchronous bridges
> clocks needed on Exynos5420 was also not well documented so I don't
> know i
Hello,
On 03/16/2015 03:16 PM, Javier Martinez Canillas wrote:
>>
>> Tested-by: Andreas Färber
>>
>> This fixes the display on the Spring Chromebook as well!
>>
>
> Thanks for testing Andreas but this patch seems to only solve a symptom
> rather than the root cause.
>
> Since the error happen
Hello,
On 03/16/2015 01:15 PM, Andreas Färber wrote:
> Am 14.03.2015 um 09:11 schrieb Javier Martinez Canillas:
>> By making the DP controller a consumer of DISP1, the PD is powered
>> off when the exynos-dp probe is deferred and powered on again when
>> the exynos-drm driver is probed.
>>
>> But
Am 14.03.2015 um 09:11 schrieb Javier Martinez Canillas:
> By making the DP controller a consumer of DISP1, the PD is powered
> off when the exynos-dp probe is deferred and powered on again when
> the exynos-drm driver is probed.
>
> But this causes the exynos-dp driver failing to obtain the strea
By making the DP controller a consumer of DISP1, the PD is powered
off when the exynos-dp probe is deferred and powered on again when
the exynos-drm driver is probed.
But this causes the exynos-dp driver failing to obtain the stream
clock since the FIMD has been powered off with the DISP1 PD:
exy
