Op 29-05-15 om 02:55 schreef Matt Roper:
> On Wed, May 20, 2015 at 06:04:27PM +0200, maarten.lankho...@linux.intel.com
> wrote:
>> From: Ander Conselvan de Oliveira
>>
>> To make this work we load the new hardware state into the
>> atomic_state, then swap it with the sw state.
>>
>> This lets us
On Wed, May 20, 2015 at 06:04:27PM +0200, maarten.lankho...@linux.intel.com
wrote:
> From: Ander Conselvan de Oliveira
>
> To make this work we load the new hardware state into the
> atomic_state, then swap it with the sw state.
>
> This lets us change the force restore path in setup_hw_state()
On Wed, May 27, 2015 at 07:30:01AM +0200, Maarten Lankhorst wrote:
> Hey,
>
> Op 20-05-15 om 18:04 schreef maarten.lankho...@linux.intel.com:
> > From: Ander Conselvan de Oliveira
> >
> > To make this work we load the new hardware state into the
> > atomic_state, then swap it with the sw state.
>
Hey,
Op 20-05-15 om 18:04 schreef maarten.lankho...@linux.intel.com:
> From: Ander Conselvan de Oliveira
>
> To make this work we load the new hardware state into the
> atomic_state, then swap it with the sw state.
>
> This lets us change the force restore path in setup_hw_state()
> to use a sing
From: Ander Conselvan de Oliveira
To make this work we load the new hardware state into the
atomic_state, then swap it with the sw state.
This lets us change the force restore path in setup_hw_state()
to use a single call to intel_mode_set() to restore all the
previous state.
As a nice bonus th
