On Wed, Sep 17, 2014 at 3:27 PM, Kamil Debski wrote:
> Hi,
>
>> From: Kiran Avnd [mailto:ki...@chromium.org]
>> Sent: Wednesday, September 17, 2014 11:26 AM
>>
>> Hi Kamil,
>>
>> On Tue, Sep 16, 2014 at 7:50 PM, Kamil Debski
>> wrote:
>> >
>> > Hi Kiran,
>> >
>> > > From: Kiran AVND [mailto:avnd.
Hi,
> From: Kiran Avnd [mailto:ki...@chromium.org]
> Sent: Wednesday, September 17, 2014 11:26 AM
>
> Hi Kamil,
>
> On Tue, Sep 16, 2014 at 7:50 PM, Kamil Debski
> wrote:
> >
> > Hi Kiran,
> >
> > > From: Kiran AVND [mailto:avnd.ki...@samsung.com]
> > > Sent: Monday, September 15, 2014 8:43 AM
Hi Kamil,
On Tue, Sep 16, 2014 at 7:50 PM, Kamil Debski wrote:
>
> Hi Kiran,
>
> > From: Kiran AVND [mailto:avnd.ki...@samsung.com]
> > Sent: Monday, September 15, 2014 8:43 AM
> >
> > From: Arun Mankuzhi
> >
> > In MFC's dynamic clock gating, we turn on the clock in try_run and turn
> > off the
Hi Kiran,
> From: Kiran AVND [mailto:avnd.ki...@samsung.com]
> Sent: Monday, September 15, 2014 8:43 AM
>
> From: Arun Mankuzhi
>
> In MFC's dynamic clock gating, we turn on the clock in try_run and turn
> off the clock upon receiving an interrupt. But this leads to excessive
> gating/ungating