From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: Sriram V <vshrirama@gmail.com>,
Peter Reid <ppeter.reid@gmail.com>,
Koen Kooi <koen@beagleboard.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Beagle PM hangs
Date: Fri, 30 Jan 2009 11:53:29 -0800 [thread overview]
Message-ID: <87skn0in9i.fsf@deeprootsystems.com> (raw)
In-Reply-To: <87hc3gk9au.fsf@deeprootsystems.com> (Kevin Hilman's message of "Fri\, 30 Jan 2009 09\:12\:09 -0800")
Kevin Hilman <khilman@deeprootsystems.com> writes:
> Richard,
>
> "Woodruff, Richard" <r-woodruff2@ti.com> writes:
>
>>> I wait for a min and try to wakeup - It works.
>>>
>>> If i wait a little longer before waking it up say, 3 or 4 minutes.
>>> It does not wakeup.
>>
>> That is consistent with your memory not being placed into self refresh properly.
>>
>> 5 general bugs I've seen over time:
>> sw bug:
>> - ctrl sequence issue before sleep
>> - CKE balls not muxed correctly
>> - crash on unexpected wake path
>> chip bug:
>> - (3430 >= es3 requires a errata sequence to work)
>> board bug:
>> - hooking ddr-chip-CKE wrongly or a way OMAP doesn't support like sharing between dies.
>
> Another possibility is that the the memory timings for the custom
> board are not set correctly.
>
Also, as another reference point:
I do not see this behavior on some other custom ES3-based hardware
using the PM branch. So that suggests some board-specific issues are
involved.
Kevin
next prev parent reply other threads:[~2009-01-30 19:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <345163910901280814nb847b34pca50f4ee6e49929d@mail.gmail.com>
2009-01-28 16:28 ` Beagle PM hangs Kevin Hilman
2009-01-28 17:46 ` Kevin Hilman
2009-01-30 14:16 ` Sriram V
2009-01-30 14:34 ` Woodruff, Richard
2009-01-30 17:12 ` Kevin Hilman
2009-01-30 19:41 ` Pandita, Vikram
2009-01-30 19:53 ` Kevin Hilman [this message]
2009-01-30 21:31 ` Woodruff, Richard
2009-02-02 5:00 ` Nayak, Rajendra
2009-01-30 21:34 ` Koen Kooi
2009-01-30 22:03 ` Woodruff, Richard
2009-01-30 22:09 ` Koen Kooi
2009-01-30 22:39 ` Kevin Hilman
2009-01-30 22:49 ` Woodruff, Richard
2009-01-30 23:21 ` Kevin Hilman
2009-01-31 11:18 ` Igor Stoppa
2009-01-30 22:40 ` Woodruff, Richard
2009-01-29 17:20 ` Peter Reid
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=87skn0in9i.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=koen@beagleboard.org \
--cc=linux-omap@vger.kernel.org \
--cc=ppeter.reid@gmail.com \
--cc=r-woodruff2@ti.com \
--cc=vshrirama@gmail.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