public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: "Mohammed, Afzal" <afzal@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: RE: OMAP3EVM not booting on l-o master
Date: Tue, 24 Apr 2012 15:23:14 +0300	[thread overview]
Message-ID: <1335270194.2149.89.camel@sokoban> (raw)
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93E96F157@DBDE01.ent.ti.com>

On Tue, 2012-04-24 at 14:00 +0200, Mohammed, Afzal wrote:
> Hi Tero,
> 
> On Mon, Apr 23, 2012 at 17:29:48, Kristo, Tero wrote:
> > Okay thats good (although I wonder why the attachment got corrupted.)
> > Did you check if the device suspends / resumes properly also? Can you
> > check what do you have in the /proc/interrupts for the hwmod_io
> > interrupt just after boot / after one suspend?
> 
> Device suspends & resumes properly.
> 
> At boot 2, after one suspend-resume 3

Okay that looks normal to me, you just get some prcm interrupts during
boot which was causing the device to hang earlier. Thanks for testing
out.

Paul, how should we take this forward?

-Tero



  reply	other threads:[~2012-04-24 12:23 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04  5:36 OMAP3EVM not booting on l-o master Mohammed, Afzal
2012-04-04  9:11 ` Mohammed, Afzal
2012-04-05  9:33   ` Paul Walmsley
2012-04-05 10:07     ` Paul Walmsley
2012-04-05 16:22       ` Mohammed, Afzal
2012-04-05 19:52         ` Paul Walmsley
2012-04-06  5:09           ` Mohammed, Afzal
2012-04-06  7:13             ` Paul Walmsley
2012-04-06  7:52               ` Mohammed, Afzal
2012-04-23  9:24                 ` Tero Kristo
2012-04-23 10:07                   ` Mohammed, Afzal
2012-04-23 10:13                     ` Tero Kristo
2012-04-23 10:43                       ` Mohammed, Afzal
2012-04-23 11:59                         ` Tero Kristo
2012-04-24 12:00                           ` Mohammed, Afzal
2012-04-24 12:23                             ` Tero Kristo [this message]
2012-04-24 17:07                   ` Kevin Hilman
2012-04-27 13:16                     ` Tero Kristo
2012-04-27 23:15                       ` Kevin Hilman
2012-04-28 11:51                         ` Mohammed, Afzal
2012-04-30 12:46                         ` Tero Kristo
2012-04-30 20:40                           ` Kevin Hilman
2012-05-01 12:55                             ` Mohammed, Afzal
2012-05-01 14:08                               ` Kevin Hilman
2012-05-02  5:48                                 ` Mohammed, Afzal
2012-05-02  8:39                                   ` Tero Kristo
2012-05-02  8:45                             ` Paul Walmsley
2012-05-02 14:27                               ` Kevin Hilman
2012-05-11 22:39                                 ` Paul Walmsley
2012-04-05 21:21       ` Kevin Hilman
2012-04-05 10:11     ` Mohammed, Afzal
2012-04-05 10:17       ` Paul Walmsley
2012-04-05 10:23         ` Raja, Govindraj
2012-04-05 16:19           ` Mohammed, Afzal
2012-04-05 17:16             ` Tony Lindgren
2012-04-06  4:54               ` Mohammed, Afzal
2012-04-06 17:41                 ` Tony Lindgren
2012-04-06 18:08                   ` Paul Walmsley
2012-04-06 18:24                     ` Tony Lindgren

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=1335270194.2149.89.camel@sokoban \
    --to=t-kristo@ti.com \
    --cc=afzal@ti.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox