suspend-to-mem on the mpc8349e-mitx-gp?

Li Yang-R58472 LeoLi at freescale.com
Fri Mar 20 14:43:12 EST 2009


> -----Original Message-----
> From: Wood Scott-B07421 
> Sent: Friday, March 20, 2009 12:11 AM
> To: Li Yang-R58472
> Cc: Soohyung Cho; linuxppc-dev at ozlabs.org
> Subject: Re: suspend-to-mem on the mpc8349e-mitx-gp?
> 
> On Thu, Mar 19, 2009 at 12:24:26AM -0700, Li Yang-R58472 wrote:
> > > -----Original Message-----
> > > From: linuxppc-dev-bounces+leoli=freescale.com at ozlabs.org
> > > [mailto:linuxppc-dev-bounces+leoli=freescale.com at ozlabs.org]
> > > On Behalf Of Soohyung Cho
> > > Sent: Thursday, March 19, 2009 1:47 PM
> > > To: linuxppc-dev at ozlabs.org; Wood Scott-B07421
> > > Subject: suspend-to-mem on the mpc8349e-mitx-gp?
> > > 
> > > Hello.
> > > 
> > > I need to enable suspend-to-mem(deep sleep) on my 
> mpc8349e-mitx-gp 
> > > box.
> > > When I send "mem" message to /sys/power/state, the box 
> seems to get 
> > > stop.
> > > I think the box get stop when it executes suspend-asm.S codes.
> > > 
> > > I know that the latest linux supports suspend-to-mem on the 
> > > mpc8313erdb box well.
> > > Is it impossible to enable suspend-to-mem on the mpc8349e-mitx-gp?
> > 
> > I don't think the MPC8349 hardware has the deep sleep functionality.
> 
> However, the code should treat "mem" as "standby" on chips 
> that don't support deep sleep.  What does the device tree 

Well, shouldn't the valid() callback reject unsupported states instead
of covering up?

- Leo



More information about the Linuxppc-dev mailing list