From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.9-rc3
Date: Tue, 19 Mar 2013 14:21:19 +0530 [thread overview]
Message-ID: <51482707.6020501@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1303181536230.29332@utopia.booyaka.com>
+ Tero,
On Monday 18 March 2013 09:08 PM, Paul Walmsley wrote:
>
> Here are some basic OMAP test results for Linux v3.9-rc3.
> Logs and other details at:
>
> http://www.pwsan.com/omap/testlogs/test_v3.9-rc3/20130314094808/
>
>
> Test summary
> ------------
>
Thanks for the summary Paul. A usual, it is quite exhaustive. Few
questions and comments below.
[..]
> Failing tests: needing investigation
> ------------------------------------
>
[..]
> PM tests:
>
[..]
>
> * 4430es2panda, 4460pandaes: pwrdm state mismatch on CAM, DSS, ABE
>
I thought we discussed about boot-loader dependency already.
> * 4460pandaes: pwrdm state mismatch on IVAHD, TESLA
>
Same here.
> * 4430es2panda: CORE, TESLA, IVAHD, L3INIT didn't enter target state
> - Probably due to lack of reset code for M3, DSP, SL2IF, FSUSB
> per discussion with Tero Kristo
> - Likely dependent on the bootloader version
> - fails with 2012.07-00136-g755de79
>
Do you still see the issue after upgrading the boot-loader version ?
> * 4460pandaes: chip not entering retention in dynamic idle
> - Presumably 4430es2panda also fails this
> - Suspend-to-RAM enters full chip retention
>
Assuming dynmic idle is CPUIdle, core retention isn't supported
in CPUDILE so it is expected
>
> Other:
>
> * 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
> - Unknown cause; could be due to the lack of hierarchical enable/disable
> in hwmod code
> - Jon Hunter reports this does not appear with the same X-loader/bootloader
> on his 4430ES2.3 Panda, so could be ES-level dependent
I confirm Jon's observation even on my OMAP4430 ES2.3 SDP.
Regards,
Santosh
next prev parent reply other threads:[~2013-03-19 8:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 15:38 OMAP baseline test results for v3.9-rc3 Paul Walmsley
2013-03-18 16:21 ` Anca Emanuel
2013-03-18 16:33 ` Paul Walmsley
2013-03-18 17:17 ` Paul Walmsley
2013-03-19 8:51 ` Santosh Shilimkar [this message]
2013-03-19 9:12 ` Tero Kristo
2013-03-26 18:43 ` Paul Walmsley
2013-03-27 9:11 ` Tero Kristo
2013-04-01 17:24 ` Tony Lindgren
2013-04-02 20:25 ` Paul Walmsley
2013-03-26 18:29 ` 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=51482707.6020501@ti.com \
--to=santosh.shilimkar@ti.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).