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: "Woodruff, Richard" <r-woodruff2@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: OMAP3 PM: off-mode during idle, problem with UART1 console
Date: Fri, 19 Jun 2009 09:20:49 -0700	[thread overview]
Message-ID: <87ab44xkim.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB0305A54975@dbde02.ent.ti.com> (Rajendra Nayak's message of "Fri\, 19 Jun 2009 15\:12\:44 +0530")

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

>>-----Original Message-----
>>From: Kevin Hilman [mailto:khilman@deeprootsystems.com] 
>>Sent: Wednesday, June 17, 2009 8:37 PM
>>To: Nayak, Rajendra
>>Cc: Woodruff, Richard; linux-omap@vger.kernel.org
>>Subject: Re: OMAP3 PM: off-mode during idle, problem with UART1 console
>>
>>"Nayak, Rajendra" <rnayak@ti.com> writes:
>>
>>> What Silicon Rev does your SDP have? I currently am using an 
>>ES3.1 based SDP
>>> and I havent seen any of these issues you have reported with 
>>off-while-idle.
>>
>>I have and ES3.0 SDP. 
>>
>>> Infact I have kept the board running overnight a couple 
>>times in the last week 
>>> with off-while-idle and voltage scaling to 0v enabled, 
>>mainly to test the recent
>>> patch set (disabling Auto idle for PER in scratchpad memory) 
>>for stability.
>>
>>Ah, great.  That is really good to know.  Are you using 
>>omap_3430sdp_pm_defconfig?
>>
>>I see the same problems with and without your patches.
>>
>>> I will see if I can get hold of an ES3 and ES2.1 based SDP's 
>>and see if I reproduce
>>> the issue. Besides I use nfs and I am not sure if that's got 
>>something to do with it.
>>> Will try a ramdisk also.
>>
>>I'm using a ramdisk.
>>
>>> Does it take you a while to reproduce this, or is it seen 
>>after the very first UART
>>> inactivity?
>>
>>It happens on the first try.
>>
>>Could you try my uImage which has my initramfs rootfs built-in on your
>>ES3.1 SDP?
>>
>>   http://userweb.kernel.org/~khilman/tmp/rajendra/uImage.pm-vanilla
>>
>>Immediately after booting, I do
>>
>># echo 1 > /sys/power/enable_off_mode                          
>>                 
>># echo 1 > /sys/power/voltage_off_while_idle                   
>>                 
>># echo 1 > /sys/power/sleep_while_idle                         
>>                 
>>
>>and after UART inactivity, I start to see sys_off_mode LED blinking.
>
> Kevin,
>
> This image works just fine on both my ES3.1 GP as well as ES3.0 EMU SDP.
> After the sys_off LED blinks, a key press stops the blinking and also gets
> be the debug console back.
>

Rajendra,

Thanks a lot for testing.  It sounds like something specific to the
ES3.0 GP SDP.

Kevin

  reply	other threads:[~2009-06-19 16:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 21:05 OMAP3 PM: off-mode during idle, problem with UART1 console Kevin Hilman
2009-06-17  6:11 ` Nayak, Rajendra
2009-06-17 14:38   ` Woodruff, Richard
2009-06-17 15:07     ` Kevin Hilman
2009-06-17 15:06   ` Kevin Hilman
2009-06-19  9:42     ` Nayak, Rajendra
2009-06-19 16:20       ` Kevin Hilman [this message]
2009-06-19 16:40         ` Woodruff, Richard

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=87ab44xkim.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=r-woodruff2@ti.com \
    --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