public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com>
To: ext Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 00/11] OMAP3 CPUidle patches
Date: Wed, 2 Jul 2008 18:42:53 +0300	[thread overview]
Message-ID: <20080702154253.GC4404@codecarver.research.nokia.com> (raw)
In-Reply-To: <000701c8dc48$d1ce66a0$68bf18ac@ent.ti.com>

Hi Rajendra,

> 
> Not sure, but you can try with my .config while I try with yours. 
> I was doing some more testing today, and I saw a hang after a while of
> idle activity with OFF being attempted multiple times.
> Using lauterbach showed me it being stuck up in prcm_interrupt_handler trying 
> to clear MPU_IRQSTATUS.
> Looks like in the PRCM interrupt handler somehow PM_WKST1_CORE is not cleared
> (I see it set to 0x2000) and hence MPU_IRQSTATUS fails to clear.
> 

Ok. I disabled OneNAND support and now I get off mode on VDD2 as well.
Consumption on VDD1 is 4uA and 32uA on VDD2. Unfortunately after the
first wakeup, off mode is never reached again.

Cheers,

Peter.

  reply	other threads:[~2008-07-02 15:46 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 14:16 [PATCH 00/11] OMAP3 CPUidle patches Rajendra Nayak
2008-07-02 13:11 ` Peter 'p2' De Schrijver
2008-07-02 13:37   ` Rajendra Nayak
2008-07-02 15:42     ` Peter 'p2' De Schrijver [this message]
2008-07-03  8:39       ` Rajendra Nayak
2008-07-03 12:44         ` Peter 'p2' De Schrijver
2008-07-04  7:26         ` Högander Jouni
2008-07-04  9:32           ` Högander Jouni
2008-07-04  9:45             ` Koen Kooi
2008-07-04  9:45             ` Rajendra Nayak
2008-07-04  9:55               ` Högander Jouni
2008-07-04 11:08               ` Högander Jouni
2008-07-07  9:38               ` Kalle Jokiniemi
2008-07-07  9:56                 ` Högander Jouni
2008-07-07 13:58                   ` Premi, Sanjeev
2008-07-07 22:25                     ` Woodruff, Richard
2008-07-08  6:15                       ` Högander Jouni
2008-07-08 12:11                         ` Woodruff, Richard
2008-07-08 13:41                           ` Högander Jouni
2008-07-08 13:52                             ` Woodruff, Richard
2008-07-09  6:48                               ` Högander Jouni
2008-07-09 16:31                                 ` Woodruff, Richard
2008-07-04 11:05             ` Peter 'p2' De Schrijver
2008-07-04 11:39               ` Peter 'p2' De Schrijver
2008-07-03  5:57 ` Högander Jouni
2008-07-03 10:20   ` Rajendra Nayak
2008-07-15 13:20 ` Rajendra Nayak
2008-07-18 13:18 ` [PATCH 00/11] OMAP3 CPUidle patches - ver 2 Rajendra Nayak
     [not found] ` <002f01c8f7c5$0790fea0$LocalHost@wipultra1382>
2008-08-06 13:12   ` Rajendra Nayak
2008-08-07  9:54     ` Kalle Jokiniemi
2008-08-12 12:40     ` Högander Jouni
2008-08-13  5:57       ` Rajendra Nayak
2008-08-13  6:06         ` Rajendra Nayak
2008-08-13  6:55         ` Högander Jouni
2008-08-13 12:35           ` Woodruff, Richard
2008-08-13 13:12             ` Högander Jouni
2008-08-14  5:25             ` Rajendra Nayak
2008-08-19 19:08     ` Paul Walmsley

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=20080702154253.GC4404@codecarver.research.nokia.com \
    --to=peter.de-schrijver@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