On Thursday 18 October 2012 02:07 AM, Jon Hunter wrote:
Ok, thanks. Yes, only updating the register when the cache value changed
would not work due to the possibility of context being lost. So
Rajendra's change makes sense. However, I think there is room to
optimise this.
With this change, on id
On 10/17/2012 03:58 PM, Paul Walmsley wrote:
> On Wed, 17 Oct 2012, Jon Hunter wrote:
>
>> Are you looking to go one step further and only update the sysconfig on
>> enabling when the context has been lost? That would require more
>> changes.
>
> Yes that's exactly it. That would avoid adding a
On Wed, 17 Oct 2012, Jon Hunter wrote:
> Are you looking to go one step further and only update the sysconfig on
> enabling when the context has been lost? That would require more
> changes.
Yes that's exactly it. That would avoid adding a special case for what
should be the common case. From
On 10/17/2012 03:25 PM, Paul Walmsley wrote:
> cc Rajendra
>
> Hi Jon
>
> On Wed, 17 Oct 2012, Jon Hunter wrote:
>
>> Currently, whenever we idle a device _idle_sysc() is called and writes to the
>> devices SYSCONFIG register to set the idle mode. A lot devices are using the
>> smart-idle mode
cc Rajendra
Hi Jon
On Wed, 17 Oct 2012, Jon Hunter wrote:
> Currently, whenever we idle a device _idle_sysc() is called and writes to the
> devices SYSCONFIG register to set the idle mode. A lot devices are using the
> smart-idle mode and so the write to the SYSCONFIG register is programming the
Currently, whenever we idle a device _idle_sysc() is called and writes to the
devices SYSCONFIG register to set the idle mode. A lot devices are using the
smart-idle mode and so the write to the SYSCONFIG register is programming the
same value that is already stored in the register.
Writes to the
