From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.16-rc4
Date: Mon, 28 Jul 2014 23:42:43 -0700 [thread overview]
Message-ID: <20140729064243.GF29045@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1407251857480.5875@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [140725 12:16]:
> On Mon, 7 Jul 2014, Tony Lindgren wrote:
>
> > With v3.16-rc4 the PM features for omap3 should be working
> > finally for device tree based booting. At lest beaglexm and
> > 3xxevm should work.
>
> Just to follow up briefly on this: there was indeed a bug in the OMAP3
> test scripts here that resulted in the UART wakeup not being enabled.
>
> Once that was fixed, system suspend-based chip-retention and chip-off
> modes work.
OK
> However, scheduler-idle based chip-retention and chip-off still are not
> working. Looking at the logs, it appears that some domains are not
> dynamically going idle. For example, looking at:
>
> http://www.pwsan.com/omap/testlogs/test_v3.16-rc6/20140724142225/pm/37xxevm/37xxevm_log.txt
>
> it can be seen that core_pwrdm's retention count doesn't increase between
> the two PM debug dumps. The important lines are:
>
> core_pwrdm (ON),OFF:0,RET:2,INA:0,ON:3,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0,RET-MEMBANK2-OFF:0
>
> and
>
> core_pwrdm (ON),OFF:0,RET:2,INA:0,ON:3,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0,RET-MEMBANK2-OFF:0
>
> That's why the test reports mark the dynamic PM modes as failing.
>
> ...
>
> Here's an example where things worked:
>
> http://www.pwsan.com/omap/testlogs/test_v3.10/20130717134228/pm/3530es3beagle/3530es3beagle_log.txt
>
> In this one, it can be seen that the CORE counts transitioned from:
>
> core_pwrdm (ON),OFF:0,RET:2,INA:0,ON:3,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0,RET-MEMBANK2-OFF:0
>
> to
>
> core_pwrdm (ON),OFF:0,RET:10,INA:0,ON:11,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0,RET-MEMBANK2-OFF:0
>
> between the retention suspend/resume test ending and the dynamic
> retention idle test ending.
Hmm I think the difference with the working v3.10 one is that you have
root=/dev/mmcblk0p2 instead of root=/dev/nfs. As the Ethernet on beagle
is on the USB EHCI, this is still blocking the deeper idle states AFAIK.
Care to test -rc7 with root=/dev/mmcblk0p2 to see if that works?
On the am37xx-evm nfsroot will work as it's on the GPMC bus.
Regards,
Tony
next prev parent reply other threads:[~2014-07-29 6:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-06 23:41 OMAP baseline test results for v3.16-rc4 Paul Walmsley
2014-07-07 8:02 ` Tony Lindgren
2014-07-14 17:28 ` Paul Walmsley
2014-07-15 6:04 ` Tony Lindgren
2014-07-15 19:56 ` Paul Walmsley
2014-07-25 19:14 ` Paul Walmsley
2014-07-29 6:42 ` Tony Lindgren [this message]
2014-07-29 8:25 ` Paul Walmsley
2014-07-29 8:49 ` Tony Lindgren
2014-07-29 12:32 ` Paul Walmsley
2014-07-29 12:57 ` Paul Walmsley
2014-07-29 14:53 ` Tony Lindgren
2014-07-29 19:37 ` Paul Walmsley
2014-07-30 5:39 ` Tony Lindgren
2014-07-30 7:53 ` Paul Walmsley
2014-07-31 13:11 ` Tony Lindgren
2014-07-31 19:27 ` Paul Walmsley
2014-08-01 7:10 ` Tony Lindgren
2014-08-01 7:52 ` Tony Lindgren
2014-08-07 22:21 ` Paul Walmsley
2014-08-08 2:14 ` Felipe Balbi
2014-08-08 6:11 ` Paul Walmsley
2014-08-08 14:34 ` Felipe Balbi
2014-08-08 23:39 ` Paul Walmsley
2014-08-09 2:49 ` Felipe Balbi
2014-08-08 2:29 ` Fabio Estevam
2014-08-08 6:14 ` Paul Walmsley
2014-08-09 12:41 ` Ezequiel Garcia
2014-07-31 13:12 ` Tero Kristo
2014-07-29 8:50 ` 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=20140729064243.GF29045@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).