-----Original Message-----
From: Wood Scott-B07421=20
Sent: Friday, March 20, 2009 10:42 PM
To: Li Yang-R58472
Cc: Soohyung Cho; linuxppc-dev@ozlabs.org
Subject: Re: suspend-to-mem on the mpc8349e-mitx-gp?
=20
Li Yang-R58472 wrote:

quoted

quoted

However, the code should treat "mem" as "standby" on chips=20

that don't=20

quoted

quoted

support deep sleep.  What does the device tree

=20
Well, shouldn't the valid() callback reject unsupported=20

states instead=20

quoted

of covering up?

=20
I don't think so, in this case.  The user is not asking for=20
"sleep" or deep sleep"; they are asking for a power state=20
that meets the definition of "standby" (which sleep does) or=20
which meets the definition of "mem"=20
(which both sleep and deep sleep do).  When the user asks for=20
"mem", we provide the lowest power mode that qualifies.

In my understanding, "mem" which is suspend-to-ram means all CPU states =
and registers are kept in memory and the CPU is completely off during =
suspension.  I don't think the sleep mode of 8349 qualifies, does it?

- Leo