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 14:15:24 -0600 [thread overview]
Message-ID: <4D0A735C.80906@ti.com> (raw)
In-Reply-To: <87fwtxef3r.fsf@deeprootsystems.com>
Kevin Hilman had written, on 12/16/2010 12:40 PM, the following:
[...]
> Your Beagle u-boot must be leaving something else on besides OTG. I'm
> using a relatively recent u-boot
>
> U-Boot 2010.12-rc1 (Nov 16 2010 - 08:31:35)
>
> that I built from source for my Beagle C3 (ES3.0), and suspend/idle test
> works for me:
>
> SUSPEND:OFF test | PASS | OFF: 0->1| RET:0 ->0 (6 sec)
> SUSPEND:RET test | PASS | OFF: 1->1| RET:0 ->1 (6 sec)
> IDLE:OFF test | PASS | OFF: 1->4| RET:1 ->4 (21 sec)
> IDLE:RET test | PASS | OFF: 4->4| RET:4 ->11 (21 sec)
>
> Is it still CORE that's not hitting RET for you?
yeah, I just think I am darned blind! DSS power domain did not reach
state on Beagle and am guessing that could be due to the evil bootloader
I was using - anyways, hoping once Senthils' hwmod patches make in, it
should be fixed as well.. unless someone has a reset of DSS clock patch
or something.. similar to OTG. arrgh.. as far as I am concerned, problem
known at least! for some reason, latest 201012-rc1|2|master etc
u-boot.bin is goofing up on me.. will look at that later on if no one
beats me to it.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2010-12-16 20:15 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
2010-12-16 18:40 ` Kevin Hilman
2010-12-16 20:15 ` Nishanth Menon [this message]
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=4D0A735C.80906@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 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.