Hello Kukjin,
On 02/05/2015 03:45 PM, Javier Martinez Canillas wrote:
> Hello Andrzej,
>
> Thanks a lot for finally finding what was causing the HDMI issue.
>
> On 02/05/2015 01:35 PM, Andrzej Hajda wrote:
>> Hi,
>>
>> Exynos chipsets since 542x have asynchronous bridges connecting different
>
Hi,
On 02/05/2015 11:45 PM, Javier Martinez Canillas wrote:
> Hello Andrzej,
>
> Thanks a lot for finally finding what was causing the HDMI issue.
>
> On 02/05/2015 01:35 PM, Andrzej Hajda wrote:
>> Hi,
>>
>> Exynos chipsets since 542x have asynchronous bridges connecting different
>> IPs.
>> T
Hello Joonyoung,
On 02/06/2015 06:27 AM, Joonyoung Shim wrote:
> On 02/05/2015 11:45 PM, Javier Martinez Canillas wrote:
>>
>> I also tested on an Exynos5420 Peach Pit Chromebook and both the "Power
>> domain power-domain disable failed" message and the system crash are gone.
>>
>
> Really gone
Hello Andrzej,
Thanks a lot for finally finding what was causing the HDMI issue.
On 02/05/2015 01:35 PM, Andrzej Hajda wrote:
> Hi,
>
> Exynos chipsets since 542x have asynchronous bridges connecting different IPs.
> These bridges should be operational during power domain switching, ie
> associ
Hi,
Exynos chipsets since 542x have asynchronous bridges connecting different IPs.
These bridges should be operational during power domain switching, ie associated
clocks cannot be gated.
This patchset adds binding to provide such clocks per power domain and adds code
which enables them during dom
