public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: pm-core broken
Date: Thu, 16 Dec 2010 11:57:04 -0600	[thread overview]
Message-ID: <4D0A52F0.8060603@ti.com> (raw)
In-Reply-To: <87wrn9hdxy.fsf@deeprootsystems.com>

Kevin Hilman had written, on 12/16/2010 10:36 AM, the following:
> Nishanth Menon <nm@ti.com> writes:
> 
>> Hi Kevin,
>>
>> Just fyi, I tested pm-core(no patches of mine) against SDP3430(ES3.1)
>> and Beagle Rev C1(ES3.0) (that is the only board I could dig up): both
>> fail - I think basically <3630 is broken atm!.
>>
>> Beagleboard:
>> with omap2plus_defconfig + MLO, u-boot.bin from
>> http://www.angstrom-distribution.org/demo/beagleboard/
>> filesystem is a minimal busybox that I had built and init=/bin/sh to
>> prevent any other apps running in the background - I use the same on
>> SDP3630 and 3430 platforms.
>>
>> branch: pm-core (from your tree).
>> defconfig: omap2plus_defconfig - no changes other than disable RM680
>> board - currently causes a build failure.
> 
> At least for Beagle (and I assume it's same for SDP, but don't have one
> to test with) the problem is that u-boot leaves the USB OTG block in a
> state that does not idle, and thus prevents CORE from hitting RET.
> 
> The solution: ensure the USB OTG block is reset.
> 
> Also in my tree, threre is an usb-otg-reset branch which you can merge
> with pm-core to test if this helps.
> 
> Until we have the USB OTG hwmod conversion merged, this temporary hack
> is needed.  After conversion to hwmod, all hwmod will be reset during
> boot so we are not affected by bootloader (mis)behavior.

Arrgh.. we have some sort of regression for .37 formal release (off will 
probably broken as a result without these patches no for mainline 
bootloaders/custom bootloaders that dont understand the dependency 
clearly?).

Anyways, with the 5 patches in usb-otg-reset - test results:
SDP3630 (ES1.0):
SUSPEND:OFF test | PASS | OFF: 0->1| RET:0 ->0 (8 sec)
SUSPEND:RET test | PASS | OFF: 1->1| RET:0 ->1 (6 sec)
IDLE:OFF test | PASS | OFF: 1->22| RET:1 ->1 (21 sec)
IDLE:RET test | PASS | OFF: 22->22| RET:1 ->24 (21 sec)

SDP3430 (ES3.1):
SUSPEND:OFF test | PASS | OFF: 0->1| RET:0 ->0 (7 sec) 

SUSPEND:RET test | PASS | OFF: 1->1| RET:0 ->1 (6 sec) 

IDLE:OFF test | PASS | OFF: 1->21| RET:1 ->1 (22 sec) 

IDLE:RET test | PASS | OFF: 21->21| RET:1 ->23 (21 sec)

Beagle C1 (ES3.0):
SUSPEND:OFF test | FAIL | OFF: 0->0| RET:0 ->0 (6 sec) 

SUSPEND:RET test | FAIL | OFF: 0->0| RET:0 ->0 (6 sec) 

IDLE:OFF test | FAIL | OFF: 0->0| RET:0 ->0 (21 sec) 

IDLE:RET test | FAIL | OFF: 0->0| RET:0 ->0 (21 sec)


-- 
Regards,
Nishanth Menon

  reply	other threads:[~2010-12-16 17:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D09719E.7080700@ti.com>
2010-12-16  2:26 ` pm-core broken Nishanth Menon
2010-12-16  3:00   ` Hiremath, Vaibhav
2010-12-16 16:08     ` Nishanth Menon
2010-12-16 16:36   ` Kevin Hilman
2010-12-16 17:57     ` Nishanth Menon [this message]
2010-12-16 18:40       ` Kevin Hilman
2010-12-16 20:15         ` Nishanth Menon
2010-12-16 20:40           ` Nishanth Menon

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=4D0A52F0.8060603@ti.com \
    --to=nm@ti.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    /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