From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: OMAP baseline test results for v3.16-rc4 Date: Thu, 31 Jul 2014 06:11:08 -0700 Message-ID: <20140731131107.GB29045@atomide.com> References: <20140729064243.GF29045@atomide.com> <20140729084930.GH29045@atomide.com> <20140729145312.GT29045@atomide.com> <20140730053940.GX29045@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:62726 "EHLO mho-02-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751255AbaGaNMc (ORCPT ); Thu, 31 Jul 2014 09:12:32 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Paul Walmsley Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kernel-build-reports@lists.linaro.org * Paul Walmsley [140730 00:55]: > On Tue, 29 Jul 2014, Tony Lindgren wrote: > > > The following patch should fix the tests above for 3530es3beagle. > > Care to test and ack as I don't have one? > > 3530es3beagle retention dynamic idle tests hang on next-20140729. (Maybe > other boards fail too - haven't tested any others). I just checked that today's linux next works for off-idle and wake-up events for at least 37xx evm. > http://www.pwsan.com/omap/testlogs/next_20140729/20140730010841/pm/3530es3beagle/3530es3beagle_log.txt > > Adding the patch you sent doesn't change that, but now some extra warning > messages appear ("PRM: I/O chain clock line assertion timed out"): > > http://www.pwsan.com/omap/testlogs/next_20140729_beagle_pm/20140730004856/pm/3530es3beagle/3530es3beagle_log.txt Weird it should just work. I don't know why the "PRM: I/O chain clock line assertion timed out" happens for you, I have not seen that. So far I've tested it on n900, beagle xm and 37xx-evm. None of those are 3530 though, but it should behave the same way as on n900. Regards, Tony From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Thu, 31 Jul 2014 06:11:08 -0700 Subject: OMAP baseline test results for v3.16-rc4 In-Reply-To: References: <20140729064243.GF29045@atomide.com> <20140729084930.GH29045@atomide.com> <20140729145312.GT29045@atomide.com> <20140730053940.GX29045@atomide.com> Message-ID: <20140731131107.GB29045@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Paul Walmsley [140730 00:55]: > On Tue, 29 Jul 2014, Tony Lindgren wrote: > > > The following patch should fix the tests above for 3530es3beagle. > > Care to test and ack as I don't have one? > > 3530es3beagle retention dynamic idle tests hang on next-20140729. (Maybe > other boards fail too - haven't tested any others). I just checked that today's linux next works for off-idle and wake-up events for at least 37xx evm. > http://www.pwsan.com/omap/testlogs/next_20140729/20140730010841/pm/3530es3beagle/3530es3beagle_log.txt > > Adding the patch you sent doesn't change that, but now some extra warning > messages appear ("PRM: I/O chain clock line assertion timed out"): > > http://www.pwsan.com/omap/testlogs/next_20140729_beagle_pm/20140730004856/pm/3530es3beagle/3530es3beagle_log.txt Weird it should just work. I don't know why the "PRM: I/O chain clock line assertion timed out" happens for you, I have not seen that. So far I've tested it on n900, beagle xm and 37xx-evm. None of those are 3530 though, but it should behave the same way as on n900. Regards, Tony