All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 29 Jul 2014 22:39:40 -0700	[thread overview]
Message-ID: <20140730053940.GX29045@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1407291922370.13035@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [140729 12:39]:
> On Tue, 29 Jul 2014, Tony Lindgren wrote:
> 
> > Hmm maybe different u-boot version then? I'm using
> > 2014.04-00001-g5f09f5b.
> >  
> > > Are you using NFS root on 37xxevm or MMC root?
> > 
> > Using nfsroot and omap2plus_defconfig. My dmesg attached
> > in case it provides some clues. I don't have console=ttyO
> > here, but I've verified that it works with that too.
> 
> Walked through the PM test script by hand, and the proximal cause of the 
> problem became obvious...
> 
> Turns out a five-second delay for a three-second autosuspend_delay_ms is 
> no longer sufficient time for kernels to enter idle.  A ten-second sleep 
> seems to be long enough.

Oh OK.
 
> Not sure what exactly is causing that weirdness yet, or when that started 
> happening.  Am suspecting it could be some of the RCU changes over the 
> past couple of years.  We don't have RCU_FAST_NO_HZ enabled in 
> omap2plus_defconfig; we should probably switch that on.

OK
 
> Now 37xxevm and the 3730beaglexm are entering idle as they should be.  
> Test report below; logs etc. have been uploaded.  Thanks for the debug 
> discussion,

Great, good to hear you found what caused it :)
 
> PM: chip retention via dynamic idle:
>     FAIL ( 5/ 7): 2430sdp, 3530es3beagle, 4430es2panda, 4460pandaes,
> 		  4460varsomom
>     Pass ( 2/ 7): 3730beaglexm, 37xxevm
> 
> PM: chip off except CORE via suspend:
>     Pass ( 1/ 1): 3730beaglexm
> 
> PM: chip off except CORE via dynamic idle:
>     Pass ( 1/ 1): 3730beaglexm
> 
> PM: chip off via suspend:
>     FAIL ( 4/ 5): 3530es3beagle, 4430es2panda, 4460pandaes,
> 		  4460varsomom
>     Pass ( 1/ 5): 37xxevm
> 
> PM: chip off via dynamic idle:
>     FAIL ( 4/ 5): 3530es3beagle, 4430es2panda, 4460pandaes,
> 		  4460varsomom
>     Pass ( 1/ 5): 37xxevm

The following patch should fix the tests above for 3530es3beagle.
Care to test and ack as I don't have one?

Regards,

Tony

8< -----------------------------------
From: Tony Lindgren <tony@atomide.com>
Date: Tue, 29 Jul 2014 22:36:59 -0700
Subject: [PATCH] ARM: dts: Enable UART wake-up events for beagleboard

For device tree based booting, we need to use wake-up
interrupts like we already do for some omaps. This fixes
a PM regression on beagleboard compared to legacy booting.

Signed-off-by: Tony Lindgren <tony@atomide.com>

--- a/arch/arm/boot/dts/omap3-beagle.dts
+++ b/arch/arm/boot/dts/omap3-beagle.dts
@@ -292,6 +292,7 @@
 &uart3 {
 	pinctrl-names = "default";
 	pinctrl-0 = <&uart3_pins>;
+	interrupts-extended = <&intc 74 &omap3_pmx_core OMAP3_UART3_RX>;
 };
 
 &gpio1 {

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: Tue, 29 Jul 2014 22:39:40 -0700	[thread overview]
Message-ID: <20140730053940.GX29045@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1407291922370.13035@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [140729 12:39]:
> On Tue, 29 Jul 2014, Tony Lindgren wrote:
> 
> > Hmm maybe different u-boot version then? I'm using
> > 2014.04-00001-g5f09f5b.
> >  
> > > Are you using NFS root on 37xxevm or MMC root?
> > 
> > Using nfsroot and omap2plus_defconfig. My dmesg attached
> > in case it provides some clues. I don't have console=ttyO
> > here, but I've verified that it works with that too.
> 
> Walked through the PM test script by hand, and the proximal cause of the 
> problem became obvious...
> 
> Turns out a five-second delay for a three-second autosuspend_delay_ms is 
> no longer sufficient time for kernels to enter idle.  A ten-second sleep 
> seems to be long enough.

Oh OK.
 
> Not sure what exactly is causing that weirdness yet, or when that started 
> happening.  Am suspecting it could be some of the RCU changes over the 
> past couple of years.  We don't have RCU_FAST_NO_HZ enabled in 
> omap2plus_defconfig; we should probably switch that on.

OK
 
> Now 37xxevm and the 3730beaglexm are entering idle as they should be.  
> Test report below; logs etc. have been uploaded.  Thanks for the debug 
> discussion,

Great, good to hear you found what caused it :)
 
> PM: chip retention via dynamic idle:
>     FAIL ( 5/ 7): 2430sdp, 3530es3beagle, 4430es2panda, 4460pandaes,
> 		  4460varsomom
>     Pass ( 2/ 7): 3730beaglexm, 37xxevm
> 
> PM: chip off except CORE via suspend:
>     Pass ( 1/ 1): 3730beaglexm
> 
> PM: chip off except CORE via dynamic idle:
>     Pass ( 1/ 1): 3730beaglexm
> 
> PM: chip off via suspend:
>     FAIL ( 4/ 5): 3530es3beagle, 4430es2panda, 4460pandaes,
> 		  4460varsomom
>     Pass ( 1/ 5): 37xxevm
> 
> PM: chip off via dynamic idle:
>     FAIL ( 4/ 5): 3530es3beagle, 4430es2panda, 4460pandaes,
> 		  4460varsomom
>     Pass ( 1/ 5): 37xxevm

The following patch should fix the tests above for 3530es3beagle.
Care to test and ack as I don't have one?

Regards,

Tony

8< -----------------------------------
From: Tony Lindgren <tony@atomide.com>
Date: Tue, 29 Jul 2014 22:36:59 -0700
Subject: [PATCH] ARM: dts: Enable UART wake-up events for beagleboard

For device tree based booting, we need to use wake-up
interrupts like we already do for some omaps. This fixes
a PM regression on beagleboard compared to legacy booting.

Signed-off-by: Tony Lindgren <tony@atomide.com>

--- a/arch/arm/boot/dts/omap3-beagle.dts
+++ b/arch/arm/boot/dts/omap3-beagle.dts
@@ -292,6 +292,7 @@
 &uart3 {
 	pinctrl-names = "default";
 	pinctrl-0 = <&uart3_pins>;
+	interrupts-extended = <&intc 74 &omap3_pmx_core OMAP3_UART3_RX>;
 };
 
 &gpio1 {

  reply	other threads:[~2014-07-30  5:41 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
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 [this message]
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=20140730053940.GX29045@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: link
Be 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.