On Mon, Apr 30, 2012 at 03:00:56PM -0700, Kevin Hilman wrote:
> "Mark A. Greer" writes:
>
> > On Fri, Apr 27, 2012 at 02:12:12PM -0700, Kevin Hilman wrote:
> >> "Mark A. Greer" writes:
> >>
> >> > On Tue, Apr 24, 2012 at 01:51:05PM -0700, Mark A. Greer wrote:
> >
> >> > Just thinking out loud..
"Mark A. Greer" writes:
> On Fri, Apr 27, 2012 at 02:12:12PM -0700, Kevin Hilman wrote:
>> "Mark A. Greer" writes:
>>
>> > On Tue, Apr 24, 2012 at 01:51:05PM -0700, Mark A. Greer wrote:
>
>> > Just thinking out loud...
>> >
>> > We could chose whether pm_idle & cpuidle issue a wfi based on
>> >
On Fri, Apr 27, 2012 at 02:12:12PM -0700, Kevin Hilman wrote:
> "Mark A. Greer" writes:
>
> > On Tue, Apr 24, 2012 at 01:51:05PM -0700, Mark A. Greer wrote:
> > Just thinking out loud...
> >
> > We could chose whether pm_idle & cpuidle issue a wfi based on
> > whether there is a davinci-emac pre
On Fri, Apr 27, 2012 at 02:12:12PM -0700, Kevin Hilman wrote:
> "Mark A. Greer" writes:
>
> > On Tue, Apr 24, 2012 at 01:51:05PM -0700, Mark A. Greer wrote:
> > We could chose whether pm_idle & cpuidle issue a wfi based on
> > whether there is a davinci-emac present. The issue with that is
> >
"Mark A. Greer" writes:
> On Tue, Apr 24, 2012 at 01:51:05PM -0700, Mark A. Greer wrote:
>> On Wed, Apr 11, 2012 at 03:37:47PM -0600, Paul Walmsley wrote:
>> > Hi
>>
>> Hi Paul, Kevin.
>>
>> > On Wed, 11 Apr 2012, Mark A. Greer wrote:
>> >
>> > > From: "Mark A. Greer"
>> > >
>> > > Currently
On Tue, Apr 24, 2012 at 01:51:05PM -0700, Mark A. Greer wrote:
> On Wed, Apr 11, 2012 at 03:37:47PM -0600, Paul Walmsley wrote:
> > Hi
>
> Hi Paul, Kevin.
>
> > On Wed, 11 Apr 2012, Mark A. Greer wrote:
> >
> > > From: "Mark A. Greer"
> > >
> > > Currently, the OMAP3 cpuidle driver calls omap3
On Wed, Apr 11, 2012 at 03:37:47PM -0600, Paul Walmsley wrote:
> Hi
Hi Paul, Kevin.
> On Wed, 11 Apr 2012, Mark A. Greer wrote:
>
> > From: "Mark A. Greer"
> >
> > Currently, the OMAP3 cpuidle driver calls omap3_enter_idle()
> > which calls omap_sram_idle(). omap_sram_idle() eventually
> > ca
On Wed, Apr 11, 2012 at 04:47:31PM -0600, Paul Walmsley wrote:
> cc Govindraj
>
> On Wed, 11 Apr 2012, Mark A. Greer wrote:
>
> > On Wed, Apr 11, 2012 at 03:37:47PM -0600, Paul Walmsley wrote:
> >
> > > I don't quite understand this patch. Are you saying that AM3517/3505
> > > can't wake from W
cc Govindraj
On Wed, 11 Apr 2012, Mark A. Greer wrote:
> On Wed, Apr 11, 2012 at 03:37:47PM -0600, Paul Walmsley wrote:
>
> > I don't quite understand this patch. Are you saying that AM3517/3505
> > can't wake from WFI? That would seem odd.
>
> No, I'm saying that I/O doesn't seem to wake it
On Wed, Apr 11, 2012 at 03:37:47PM -0600, Paul Walmsley wrote:
>
> On Wed, 11 Apr 2012, Mark A. Greer wrote:
>
> > From: "Mark A. Greer"
> >
> > Currently, the OMAP3 cpuidle driver calls omap3_enter_idle()
> > which calls omap_sram_idle(). omap_sram_idle() eventually
> > causes a 'wfi' instruc
Hi
On Wed, 11 Apr 2012, Mark A. Greer wrote:
> From: "Mark A. Greer"
>
> Currently, the OMAP3 cpuidle driver calls omap3_enter_idle()
> which calls omap_sram_idle(). omap_sram_idle() eventually
> causes a 'wfi' instruction to be executed effectively putting
> the system to sleep. It is assume
From: "Mark A. Greer"
Currently, the OMAP3 cpuidle driver calls omap3_enter_idle()
which calls omap_sram_idle(). omap_sram_idle() eventually
causes a 'wfi' instruction to be executed effectively putting
the system to sleep. It is assumed that an I/O wake-up event
will occur to wake the system u
12 matches
Mail list logo