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: Thu, 31 Jul 2014 06:11:08 -0700	[thread overview]
Message-ID: <20140731131107.GB29045@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1407300725290.4477@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [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

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: Thu, 31 Jul 2014 06:11:08 -0700	[thread overview]
Message-ID: <20140731131107.GB29045@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1407300725290.4477@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [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

  reply	other threads:[~2014-07-31 13:12 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
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 [this message]
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=20140731131107.GB29045@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.