From: Kevin Hilman <khilman@deeprootsystems.com>
To: Ramesh Gupta Guntha <grgupta77@gmail.com>
Cc: Shreyas Mahajan <mahajan.shreyas@gmail.com>,
"Premi, Sanjeev" <premi@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: Omap3430 does not resume after suspend
Date: Tue, 03 Feb 2009 23:01:44 -0800 [thread overview]
Message-ID: <87tz7a8z3b.fsf@deeprootsystems.com> (raw)
In-Reply-To: <3a2dabf50902032244t4e045587idf6e574c1fca654f@mail.gmail.com> (Ramesh Gupta Guntha's message of "Wed\, 4 Feb 2009 12\:14\:03 +0530")
Ramesh Gupta Guntha <grgupta77@gmail.com> writes:
> Hi Shreyas,
>
> On 2/4/09, Shreyas Mahajan <mahajan.shreyas@gmail.com> wrote:
>> Hi,
>> Thanks for constantly tolerating my ignorance. I git-cloned the
>> latest PM tree available and booted my 3430 LDP board with ldp
>> defconfig configuration. Now the problem regarding hanging of machine
>> after some small interval is solved but when I done 'echo mem
>> >/sys/power/state' it gives error to suspend,
>> This is log for it,
>>
>> '/ # echo mem > /sys/power/state
>> <6>PM: Syncing filesystems ... PM: Syncing filesystems ... done.
>> done.
>> Freezing user space processes ... Freezing user space processes ...
>> (elapsed 0.00 seconds) (elapsed 0.00 seconds) done.
>> done.
>> Freezing remaining freezable tasks ... Freezing remaining freezable
>> tasks ... (elapsed 0� )����r$�Powerdomain (core_pwrdm) d1
>> Powerdomain (per_pwrdm) didn't enter target state 1
>> �*43
>> Could not enter target state in pm_suspendend to debug)
>> � 1�ռ���, 森�Ѡr��
>> Restarting tasks ... Restarting tasks ... done.%�������� J$�4%�% Ѵ�*43
>> done.F�)������������ J$�4%�% Ѵ�*43
>> '
>> I searched similar problems on mailing list, in which suspend log
>> contains exactly which process could not be stopped as reason to
>> suspend failure. But in above log, I could not interpret such a
>> reason.
>> Could anyone please help me with this?
>
> Please look into below mail thread on the PM off mode support in l-o list.
>
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg08968.html
>
> If you are trying it on SDP , use u-boot mentioned in the above link.
>
>
> use below settings before running echo mem > /sys/power/state for off mode.
>
> echo 1 > /sys/power/clocks_off_while_idle
> echo 1 > /sys/power/voltage_off_while_idle
> echo 1 > /sys/power/enable_off_mode
>
>
> I tried it on my SDP with omap_3430sdp_min_defconfig, I am seeing all
> the domains entering to OFF mode.
>
In addition to above, I suggest you turn of CONFIG_DEBUG_LL as well as
that will clutter up your serial console with garbage during
suspend/resume.
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-02-04 7:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 9:24 Omap3430 does not resume after suspend Shreyas Mahajan
2009-01-30 14:02 ` Premi, Sanjeev
2009-02-03 6:14 ` Shreyas Mahajan
2009-02-03 9:32 ` Premi, Sanjeev
2009-02-04 6:30 ` Shreyas Mahajan
2009-02-04 6:44 ` Ramesh Gupta Guntha
2009-02-04 7:01 ` Kevin Hilman [this message]
[not found] ` <d105d8d00902032329u2878dbf0m2609ca70b08feb7d@mail.gmail.com>
2009-02-04 7:30 ` Fwd: " Shreyas Mahajan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tz7a8z3b.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=grgupta77@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=mahajan.shreyas@gmail.com \
--cc=premi@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox