Rodrigo Vivi writes:
> On Sat, Feb 10, 2018 at 09:43:59AM +, Chris Wilson wrote:
>> Quoting Andy Lutomirski (2018-02-09 17:55:38)
>> > On Fri, Feb 9, 2018 at 7:39 AM, Rodrigo Vivi
>> > wrote:
>> > > Rodrigo Vivi writes:
>> > > So, I move the hacked scheduled to 10s and forced psr_activate
On Sat, Feb 10, 2018 at 09:43:59AM +, Chris Wilson wrote:
> Quoting Andy Lutomirski (2018-02-09 17:55:38)
> > On Fri, Feb 9, 2018 at 7:39 AM, Rodrigo Vivi wrote:
> > > Rodrigo Vivi writes:
> > > So, I move the hacked scheduled to 10s and forced psr_activate 10ms
> > > after that and the resul
Quoting Andy Lutomirski (2018-02-09 17:55:38)
> On Fri, Feb 9, 2018 at 7:39 AM, Rodrigo Vivi wrote:
> > Rodrigo Vivi writes:
> > So, I move the hacked scheduled to 10s and forced psr_activate 10ms
> > after that and the result is this:
> >
> >
> > [ 11.757909] [drm:intel_psr_enable [i915]] *ERR
On Thu, 2018-02-08 at 23:39 -0800, Rodrigo Vivi wrote:
> Rodrigo Vivi writes:
>
> > "Pandiyan, Dhinakaran" writes:
> >
> >> On Thu, 2018-02-08 at 14:48 -0800, Rodrigo Vivi wrote:
> >>> Hi Andy,
> >>>
> >>> thanks for getting involved with PSR and sorry for not replying sooner.
> >>>
> >>> I fir
On Fri, Feb 9, 2018 at 7:39 AM, Rodrigo Vivi wrote:
> Rodrigo Vivi writes:
>
>> "Pandiyan, Dhinakaran" writes:
>>
>>> On Thu, 2018-02-08 at 14:48 -0800, Rodrigo Vivi wrote:
Hi Andy,
thanks for getting involved with PSR and sorry for not replying sooner.
I first saw this
Rodrigo Vivi writes:
> "Pandiyan, Dhinakaran" writes:
>
>> On Thu, 2018-02-08 at 14:48 -0800, Rodrigo Vivi wrote:
>>> Hi Andy,
>>>
>>> thanks for getting involved with PSR and sorry for not replying sooner.
>>>
>>> I first saw this patch on that bugzilla entry but only now I stop to
>>> really t
"Pandiyan, Dhinakaran" writes:
> On Thu, 2018-02-08 at 14:48 -0800, Rodrigo Vivi wrote:
>> Hi Andy,
>>
>> thanks for getting involved with PSR and sorry for not replying sooner.
>>
>> I first saw this patch on that bugzilla entry but only now I stop to
>> really think why I have written the cod
On Thu, 2018-02-08 at 17:01 -0800, Andy Lutomirski wrote:
>
>
> > On Feb 8, 2018, at 4:39 PM, Pandiyan, Dhinakaran
> > wrote:
> >
> >
> >> On Thu, 2018-02-08 at 14:48 -0800, Rodrigo Vivi wrote:
> >> Hi Andy,
> >>
> >> thanks for getting involved with PSR and sorry for not replying sooner.
> On Feb 8, 2018, at 4:39 PM, Pandiyan, Dhinakaran
> wrote:
>
>
>> On Thu, 2018-02-08 at 14:48 -0800, Rodrigo Vivi wrote:
>> Hi Andy,
>>
>> thanks for getting involved with PSR and sorry for not replying sooner.
>>
>> I first saw this patch on that bugzilla entry but only now I stop to
>>
On Thu, 2018-02-08 at 14:48 -0800, Rodrigo Vivi wrote:
> Hi Andy,
>
> thanks for getting involved with PSR and sorry for not replying sooner.
>
> I first saw this patch on that bugzilla entry but only now I stop to
> really think why I have written the code that way.
>
> So some clarity below.
Hi Andy,
thanks for getting involved with PSR and sorry for not replying sooner.
I first saw this patch on that bugzilla entry but only now I stop to
really think why I have written the code that way.
So some clarity below.
On Mon, Feb 05, 2018 at 10:07:09PM +, Andy Lutomirski wrote:
> The
From: Andy Lutomirski
The current PSR code has a two call sites that each schedule delayed
work to activate PSR. As far as I can tell, each call site intends
to keep PSR inactive for the given amount of time and then allow it
to be activated.
The call sites are:
- intel_psr_enable(), which ex
The current PSR code has a two call sites that each schedule delayed
work to activate PSR. As far as I can tell, each call site intends
to keep PSR inactive for the given amount of time and then allow it
to be activated.
The call sites are:
- intel_psr_enable(), which explicitly states in a com
13 matches
Mail list logo
