public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Nayak, Rajendra" <rnayak@ti.com>
Cc: "Högander Jouni" <jouni.hogander@nokia.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: new PM branch available
Date: Fri, 23 Jan 2009 09:48:32 -0800	[thread overview]
Message-ID: <871vut7w27.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB02F51109B5@dbde02.ent.ti.com> (Rajendra Nayak's message of "Fri\, 23 Jan 2009 17\:30\:24 +0530")

"Nayak, Rajendra" <rnayak@ti.com> writes:

>  
>
>> -----Original Message-----
>> From: Högander Jouni [mailto:jouni.hogander@nokia.com] 
>> Sent: Friday, January 23, 2009 4:52 PM
>> To: Nayak, Rajendra
>> Cc: Kevin Hilman; linux-omap@vger.kernel.org
>> Subject: Re: new PM branch available
>> 
>> "ext Nayak, Rajendra" <rnayak@ti.com> writes:
>> 
>> >> I did some testing today on my 3.0GP 3430SDP. This is with 
>> the omap_3430sdp_min_defconfig.
>> >>
>> >> 1) Idle.
>> >> echo -n 1 > /sys/power/clocks_off_while_idle
>> >> echo -n 1 > /sys/power/enable_off
>> >> Could not hit RET. something seems to be still active. Not 
>> sure if it could be something
>> >> to do with this error that's thrown while bootup
>> >>
>> >> <6>Disabling unused clock "dpll5_ck"
>> >> Disabling unused clock "dpll5_ck"
>> >> <3>clock: dpll5_ck failed transition to 'locked'
>> >> clock: dpll5_ck failed transition to 'locked'
>> >> 
>> >> This is the same results I see on my SDP.
>> >> 
>> >> Looking at the registers, I am pretty sure it is the D2D 
>> clockdomain
>> >> that still has activity, but due to very poor Stacked-mode 
>> docs and no
>> >> responses to the D2D questions asked to TI I have not been able to
>> >> figure this one out.
>> >> 
>> >> Help debugging this would be greatly appreciated.
>> >
>> > I looked some more into this today and saw that the hang is 
>> indeed caused
>> > due to some kind of debug console going dead. The system 
>> was still looping in the
>> > idle thread. I could even do a telnet remotely to my board and take
>> > some debug dumps..
>> 
>> This might help you:
>
> Yup, this does help. There's no hang now either in idle or in suspend.

Rajendra,

Is CORE hitting retention for you?  while UART wakeups are now working,
CORE is still not hitting retention.

Kevin

> Not sure why this was affecting only the SDP while the pm branch seems
> to function without this for beagle and other omap3 platforms?
>
>> 
>> diff --git a/arch/arm/mach-omap2/pm34xx.c 
>> b/arch/arm/mach-omap2/pm34xx.c
>> index b2db0ba..266e4f5 100644
>> --- a/arch/arm/mach-omap2/pm34xx.c
>> +++ b/arch/arm/mach-omap2/pm34xx.c
>> @@ -401,6 +401,8 @@ void omap_sram_idle(void)
>>                         omap3_prcm_restore_context();
>>                         omap3_sram_restore_context();
>>                 }
>> +               omap_uart_resume_idle(0);
>> +               omap_uart_resume_idle(1);
>>                 if (core_next_state == PWRDM_POWER_OFF)
>>                         prm_clear_mod_reg_bits(OMAP3430_AUTO_OFF,
>>                                                OMAP3430_GR_MOD,
>> 
>> -- 
>> Jouni Högander
>> 
>> 
>> 
--
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

  parent reply	other threads:[~2009-01-23 17:48 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 21:51 new PM branch available Kevin Hilman
2009-01-14  7:35 ` Koen Kooi
2009-01-14 18:09   ` David Brownell
2009-01-14 22:14   ` Kevin Hilman
2009-01-15  8:18     ` Koen Kooi
2009-01-14 12:40 ` Ramesh Gupta Guntha
2009-01-14 16:35   ` Kevin Hilman
2009-01-14 13:57 ` Sriram V
2009-01-14 16:39   ` Kevin Hilman
2009-01-15 13:42     ` Premi, Sanjeev
2009-01-15 15:01       ` Kevin Hilman
2009-01-15 15:17         ` Premi, Sanjeev
2009-01-15 15:34           ` Kevin Hilman
2009-01-15 16:00             ` Premi, Sanjeev
2009-01-15 15:00     ` Sriram V
     [not found]     ` <8bf247760901150654n78b198f0o5c2270186e9c119e@mail.gmail.com>
2009-01-15 15:07       ` Kevin Hilman
2009-01-16 13:49 ` Nayak, Rajendra
2009-01-16 19:03   ` Kevin Hilman
2009-01-19 15:46     ` Premi, Sanjeev
2009-01-19 16:04       ` Premi, Sanjeev
2009-01-23 10:19     ` Nayak, Rajendra
2009-01-23 11:21       ` Högander Jouni
2009-01-23 12:00         ` Nayak, Rajendra
2009-01-23 12:10           ` Nayak, Rajendra
2009-01-23 16:49             ` Kevin Hilman
2009-01-23 12:10           ` Koen Kooi
2009-01-23 17:20             ` Kevin Hilman
2009-01-23 18:27               ` Koen Kooi
2009-01-23 17:48           ` Kevin Hilman [this message]
2009-01-27  9:18             ` Nayak, Rajendra
2009-02-02 17:45 ` Peter 'p2' De Schrijver
2009-02-02 19:42   ` Kevin Hilman
2009-02-02 20:06     ` Kevin Hilman
2009-02-04  0:52     ` Peter 'p2' De Schrijver
2009-02-04 16:04       ` Kevin Hilman
2009-02-04 16:15         ` Koen Kooi
2009-02-04 16:38         ` Peter 'p2' De Schrijver
  -- strict thread matches above, loose matches on Subject: below --
2009-03-18 18:56 Nicholas Chen
2009-03-18 19:01 ` Kevin Hilman
2009-03-18 19:22   ` Nicholas Chen

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=871vut7w27.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=jouni.hogander@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=rnayak@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