From: Tony Lindgren <tony@atomide.com> To: Paul Walmsley <paul@pwsan.com> Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kernel-build-reports@lists.linaro.org Subject: Re: OMAP baseline test results for v3.16-rc4 Date: Mon, 7 Jul 2014 01:02:39 -0700 [thread overview] Message-ID: <20140707080238.GF28884@atomide.com> (raw) In-Reply-To: <alpine.DEB.2.02.1407062339420.15016@utopia.booyaka.com> * Paul Walmsley <paul@pwsan.com> [140706 16:43]: > > Here are some basic OMAP test results for Linux v3.16-rc4. > Logs and other details at: ... > PM: chip retention via dynamic idle: > FAIL ( 7/ 7): 2430sdp, 3530es3beagle, 3730beaglexm, 37xxevm, > 4430es2panda, 4460pandaes, 4460varsomom > > PM: chip off except CORE via suspend: > FAIL ( 1/ 1): 3730beaglexm > > PM: chip off except CORE via dynamic idle: > FAIL ( 1/ 1): 3730beaglexm > > PM: chip off via suspend: > FAIL ( 5/ 5): 3530es3beagle, 37xxevm, 4430es2panda, 4460pandaes, > 4460varsomom > > PM: chip off via dynamic idle: > FAIL ( 5/ 5): 3530es3beagle, 37xxevm, 4430es2panda, 4460pandaes, > 4460varsomom 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. Maybe you are using legacy booting path to idle the UARTs still? FYI, I'm doing this to find the UART entries: uarts=$(find /sys/class/tty/ttyO*/device/power/ -type d) for uart in $uarts; do echo 3000 > $uart/autosuspend_delay_ms done uarts=$(find /sys/class/tty/ttyO*/power/ -type d) for uart in $uarts; do echo enabled > $uart/wakeup echo auto > $uart/control done echo 1 > /sys/kernel/debug/pm_debug/enable_off_mode Regards, Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren) To: linux-arm-kernel@lists.infradead.org Subject: OMAP baseline test results for v3.16-rc4 Date: Mon, 7 Jul 2014 01:02:39 -0700 [thread overview] Message-ID: <20140707080238.GF28884@atomide.com> (raw) In-Reply-To: <alpine.DEB.2.02.1407062339420.15016@utopia.booyaka.com> * Paul Walmsley <paul@pwsan.com> [140706 16:43]: > > Here are some basic OMAP test results for Linux v3.16-rc4. > Logs and other details at: ... > PM: chip retention via dynamic idle: > FAIL ( 7/ 7): 2430sdp, 3530es3beagle, 3730beaglexm, 37xxevm, > 4430es2panda, 4460pandaes, 4460varsomom > > PM: chip off except CORE via suspend: > FAIL ( 1/ 1): 3730beaglexm > > PM: chip off except CORE via dynamic idle: > FAIL ( 1/ 1): 3730beaglexm > > PM: chip off via suspend: > FAIL ( 5/ 5): 3530es3beagle, 37xxevm, 4430es2panda, 4460pandaes, > 4460varsomom > > PM: chip off via dynamic idle: > FAIL ( 5/ 5): 3530es3beagle, 37xxevm, 4430es2panda, 4460pandaes, > 4460varsomom 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. Maybe you are using legacy booting path to idle the UARTs still? FYI, I'm doing this to find the UART entries: uarts=$(find /sys/class/tty/ttyO*/device/power/ -type d) for uart in $uarts; do echo 3000 > $uart/autosuspend_delay_ms done uarts=$(find /sys/class/tty/ttyO*/power/ -type d) for uart in $uarts; do echo enabled > $uart/wakeup echo auto > $uart/control done echo 1 > /sys/kernel/debug/pm_debug/enable_off_mode Regards, Tony
next prev parent reply other threads:[~2014-07-07 8:02 UTC|newest] Thread overview: 60+ 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-06 23:41 ` Paul Walmsley 2014-07-07 8:02 ` Tony Lindgren [this message] 2014-07-07 8:02 ` Tony Lindgren 2014-07-14 17:28 ` Paul Walmsley 2014-07-14 17:28 ` Paul Walmsley 2014-07-15 6:04 ` Tony Lindgren 2014-07-15 6:04 ` Tony Lindgren 2014-07-15 19:56 ` Paul Walmsley 2014-07-15 19:56 ` Paul Walmsley 2014-07-25 19:14 ` Paul Walmsley 2014-07-25 19:14 ` Paul Walmsley 2014-07-29 6:42 ` Tony Lindgren 2014-07-29 6:42 ` Tony Lindgren 2014-07-29 8:25 ` Paul Walmsley 2014-07-29 8:25 ` Paul Walmsley 2014-07-29 8:49 ` Tony Lindgren 2014-07-29 8:49 ` Tony Lindgren 2014-07-29 12:32 ` Paul Walmsley 2014-07-29 12:32 ` Paul Walmsley 2014-07-29 12:57 ` Paul Walmsley 2014-07-29 12:57 ` Paul Walmsley 2014-07-29 14:53 ` Tony Lindgren 2014-07-29 14:53 ` Tony Lindgren 2014-07-29 19:37 ` Paul Walmsley 2014-07-29 19:37 ` Paul Walmsley 2014-07-30 5:39 ` Tony Lindgren 2014-07-30 5:39 ` Tony Lindgren 2014-07-30 7:53 ` Paul Walmsley 2014-07-30 7:53 ` Paul Walmsley 2014-07-31 13:11 ` Tony Lindgren 2014-07-31 13:11 ` Tony Lindgren 2014-07-31 19:27 ` Paul Walmsley 2014-07-31 19:27 ` Paul Walmsley 2014-08-01 7:10 ` Tony Lindgren 2014-08-01 7:10 ` Tony Lindgren 2014-08-01 7:52 ` Tony Lindgren 2014-08-01 7:52 ` Tony Lindgren 2014-08-07 22:21 ` Paul Walmsley 2014-08-07 22:21 ` Paul Walmsley 2014-08-08 2:14 ` Felipe Balbi 2014-08-08 2:14 ` Felipe Balbi 2014-08-08 6:11 ` Paul Walmsley 2014-08-08 6:11 ` Paul Walmsley 2014-08-08 14:34 ` Felipe Balbi 2014-08-08 14:34 ` Felipe Balbi 2014-08-08 23:39 ` Paul Walmsley 2014-08-08 23:39 ` Paul Walmsley 2014-08-09 2:49 ` Felipe Balbi 2014-08-09 2:49 ` Felipe Balbi 2014-08-08 2:29 ` Fabio Estevam 2014-08-08 2:29 ` Fabio Estevam 2014-08-08 6:14 ` Paul Walmsley 2014-08-08 6:14 ` Paul Walmsley 2014-08-09 12:41 ` Ezequiel Garcia 2014-08-09 12:41 ` Ezequiel Garcia 2014-07-31 13:12 ` Tero Kristo 2014-07-31 13:12 ` Tero Kristo 2014-07-29 8:50 ` Paul Walmsley 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=20140707080238.GF28884@atomide.com \ --to=tony@atomide.com \ --cc=kernel-build-reports@lists.linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=paul@pwsan.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.