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 Kevin Hilman <khilman@deeprootsystems.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: new PM branch available
Date: Mon, 2 Feb 2009 19:45:32 +0200	[thread overview]
Message-ID: <20090202174532.GJ4954@codecarver.research.nokia.com> (raw)
In-Reply-To: <87iqoij2me.fsf@deeprootsystems.com>

Hi Kevin,

> Hello,
> 
> The latest PM branch is now available[1].
> 
> I've done basic testing of retention and off-mode (suspend and dynamic
> idle) on Beagle and custom HW.  My SDP has something still keeping
> CORE active that others have not seen, but I have yet to debug.  Any
> other reports from SDP testing would be appreciated.
> 
> Notable changes/updates
> - rebased on latest clock updates and fixes from Paul
> - clockfw pre- and post- notifiers
> - DVFS for VDD2
> 

I tried it on a beagleboard last night, but couldn't get even static
retention to work. Some domains (core, per, dss) stay on, but even mpu
and neon don't go to retention. They only go to inactive. 
So could you send your .config file ? Which rootfs are you using, I'm
using debian, so maybe something keeps the CPU busy. Are you using NAND
or MMC to store your rootfs ? Which beagle HW rev do you have ? I'm
testing on a B5 board. And which u-boot are you using ?

Thanks,

Peter.

-- 
goa is a state of mind

  parent reply	other threads:[~2009-02-02 17:45 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
2009-01-27  9:18             ` Nayak, Rajendra
2009-02-02 17:45 ` Peter 'p2' De Schrijver [this message]
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=20090202174532.GJ4954@codecarver.research.nokia.com \
    --to=peter.de-schrijver@nokia.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    /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