From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: Omap3430 does not resume after suspend Date: Tue, 03 Feb 2009 23:01:44 -0800 Message-ID: <87tz7a8z3b.fsf@deeprootsystems.com> References: <3a2dabf50902032244t4e045587idf6e574c1fca654f@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from wf-out-1314.google.com ([209.85.200.173]:1093 "EHLO wf-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750892AbZBDHBz convert rfc822-to-8bit (ORCPT ); Wed, 4 Feb 2009 02:01:55 -0500 Received: by wf-out-1314.google.com with SMTP id 27so2697969wfd.4 for ; Tue, 03 Feb 2009 23:01:48 -0800 (PST) In-Reply-To: <3a2dabf50902032244t4e045587idf6e574c1fca654f@mail.gmail.com> (Ramesh Gupta Guntha's message of "Wed\, 4 Feb 2009 12\:14\:03 +0530") Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Ramesh Gupta Guntha Cc: Shreyas Mahajan , "Premi, Sanjeev" , linux-omap@vger.kernel.org Ramesh Gupta Guntha writes: > Hi Shreyas, > > On 2/4/09, Shreyas Mahajan 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 machin= e >> 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=EF=BF=BD )=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BDr= $=EF=BF=BDPowerdomain (core_pwrdm) d1 >> Powerdomain (per_pwrdm) didn't enter target state 1 >> =EF=BF=BD*43 >> Could not enter target state in pm_suspendend to debug) >> =EF=BF=BD 1=EF=BF=BD=D5=BC=EF=BF=BD=EF=BF=BD=EF=BF=BD, =E6=A3=AE=EF=BF= =BD=D1=A0r=EF=BF=BD=EF=BF=BD >> Restarting tasks ... Restarting tasks ... done.%=EF=BF=BD=EF=BF=BD=EF= =BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD J$=EF=BF=BD4%=EF=BF= =BD% =D1=B4=EF=BF=BD*43 >> done.F=EF=BF=BD=F3=B0=AF=85)=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF= =BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD J$=EF= =BF=BD4%=EF=BF=BD% =D1=B4=EF=BF=BD*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" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html