Thread (13 messages) 13 messages, 5 authors, 2009-03-25

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

From: Soohyung Cho <hidden>
Date: 2009-03-23 06:17:20

2009/3/23 Li Yang-R58472 [off-list ref]
quoted
-----Original Message-----
From: Wood Scott-B07421
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?

Li Yang-R58472 wrote:
quoted
quoted
However, the code should treat "mem" as "standby" on chips
that don't
quoted
quoted
support deep sleep.  What does the device tree
Well, shouldn't the valid() callback reject unsupported
states instead
quoted
of covering up?
I don't think so, in this case.  The user is not asking for
"sleep" or deep sleep"; they are asking for a power state
that meets the definition of "standby" (which sleep does) or
which meets the definition of "mem"
(which both sleep and deep sleep do).  When the user asks for
"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

I also agree to Leo.
It can be confusing, if "mem" means both sleep and deep sleep.
It would be better not to show "mem", if 8349 don't have deep sleep mode.

- Soohyung
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help