On Wed, May 22, 2019 at 12:24 PM Hoegeun Kwon
wrote:
> On 4/10/19 1:24 AM, Eric Anholt wrote:
>
> Hoegeun Kwon writes:
>
>
> On 4/2/19 2:48 AM, Eric Anholt wrote:
>
> Hoegeun Kwon writes:
>
>
> There is a problem when often dpms goes from off to on. pm idle is not
> in sync and the problem oc
On 4/10/19 1:24 AM, Eric Anholt wrote:
> Hoegeun Kwon writes:
>
>> On 4/2/19 2:48 AM, Eric Anholt wrote:
>>> Hoegeun Kwon writes:
>>>
There is a problem when often dpms goes from off to on. pm idle is not
in sync and the problem occurs. Modify pm_runtime_put from
asynchronous to sy
Hoegeun Kwon writes:
> On 4/2/19 2:48 AM, Eric Anholt wrote:
>> Hoegeun Kwon writes:
>>
>>> There is a problem when often dpms goes from off to on. pm idle is not
>>> in sync and the problem occurs. Modify pm_runtime_put from
>>> asynchronous to synchronous.
>> Why would we need the power domain
On 4/2/19 2:48 AM, Eric Anholt wrote:
> Hoegeun Kwon writes:
>
>> There is a problem when often dpms goes from off to on. pm idle is not
>> in sync and the problem occurs. Modify pm_runtime_put from
>> asynchronous to synchronous.
> Why would we need the power domain to go to off before we try to
Hoegeun Kwon writes:
> There is a problem when often dpms goes from off to on. pm idle is not
> in sync and the problem occurs. Modify pm_runtime_put from
> asynchronous to synchronous.
Why would we need the power domain to go to off before we try to come
back? Any idea? Also, please specify w
