From: "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com>
To: ext Kevin Hilman <khilman@deeprootsystems.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: new PM branch available
Date: Wed, 4 Feb 2009 18:38:46 +0200 [thread overview]
Message-ID: <20090204163846.GC22194@codecarver.research.nokia.com> (raw)
In-Reply-To: <87eiye89y1.fsf@deeprootsystems.com>
Hi Kevin,
>
> Did you happen to notice what was keeping PER out of retention before
> the u-boot upgrade? Looks like we might still need some init-time
> reset code to compensate for bootloaders.
>
No. I still have the old u-boot version though, so I can reproduce the
problem. After fosdem :)
> > The only way to get core to retention was to force idle USBOTG and
> > disable the USBOTG driver.
>
> This is the same issue on 3430SDP. The PM branch code does the
> force-idle, and I usually have USB built as modules and not loaded
> when I do the tests.
>
Ok.
> I'm guessing this is a result of u-boot configuring/using USB.
>
> > Dynamic retention seems to work only once the system has been in static
> > retention once.
> >
> > Static off mode seems to work, but resume from off kills the UART. The
> > system seems to run though, at least LED0 flickers as usual when the
> > system runs. Sometimes it hangs and I have seen one reboot.
>
> I have noticed this as well.
>
> I haven't looked at all at the T2 scripts being used on Beagle. Do
> you think some of these issues may be related to those scripts?
>
It might be. They are very basic compared to some others I have seen. I
will have a look at those tonight.
Cheers,
Peter.
--
goa is a state of mind
next prev parent reply other threads:[~2009-02-04 16:39 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 21:51 new PM branch available Kevin Hilman
2009-01-14 7:35 ` Koen Kooi
2009-01-14 18:09 ` David Brownell
2009-01-14 22:14 ` Kevin Hilman
2009-01-15 8:18 ` Koen Kooi
2009-01-14 12:40 ` Ramesh Gupta Guntha
2009-01-14 16:35 ` Kevin Hilman
2009-01-14 13:57 ` Sriram V
2009-01-14 16:39 ` Kevin Hilman
2009-01-15 13:42 ` Premi, Sanjeev
2009-01-15 15:01 ` Kevin Hilman
2009-01-15 15:17 ` Premi, Sanjeev
2009-01-15 15:34 ` Kevin Hilman
2009-01-15 16:00 ` Premi, Sanjeev
2009-01-15 15:00 ` Sriram V
[not found] ` <8bf247760901150654n78b198f0o5c2270186e9c119e@mail.gmail.com>
2009-01-15 15:07 ` Kevin Hilman
2009-01-16 13:49 ` Nayak, Rajendra
2009-01-16 19:03 ` Kevin Hilman
2009-01-19 15:46 ` Premi, Sanjeev
2009-01-19 16:04 ` Premi, Sanjeev
2009-01-23 10:19 ` Nayak, Rajendra
2009-01-23 11:21 ` Högander Jouni
2009-01-23 12:00 ` Nayak, Rajendra
2009-01-23 12:10 ` Nayak, Rajendra
2009-01-23 16:49 ` Kevin Hilman
2009-01-23 12:10 ` Koen Kooi
2009-01-23 17:20 ` Kevin Hilman
2009-01-23 18:27 ` Koen Kooi
2009-01-23 17:48 ` Kevin Hilman
2009-01-27 9:18 ` Nayak, Rajendra
2009-02-02 17:45 ` Peter 'p2' De Schrijver
2009-02-02 19:42 ` Kevin Hilman
2009-02-02 20:06 ` Kevin Hilman
2009-02-04 0:52 ` Peter 'p2' De Schrijver
2009-02-04 16:04 ` Kevin Hilman
2009-02-04 16:15 ` Koen Kooi
2009-02-04 16:38 ` Peter 'p2' De Schrijver [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-18 18:56 Nicholas Chen
2009-03-18 19:01 ` Kevin Hilman
2009-03-18 19:22 ` Nicholas Chen
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=20090204163846.GC22194@codecarver.research.nokia.com \
--to=peter.de-schrijver@nokia.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