From: Domen Puncer <domen.puncer@telargo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] icecube/lite5200b: wakeup from low-power support
Date: Sat, 31 Mar 2007 20:38:43 +0200 [thread overview]
Message-ID: <20070331183843.GA3143@nd47.coderock.org> (raw)
In-Reply-To: <460E9853.80902@semihalf.com>
[ Gah, saw it didn't make it to u-boot ML, resending ]
On 31/03/07 19:20 +0200, Rafal Jaworowski wrote:
> Domen Puncer wrote:
> >U-Boot part of Lite5200b low power mode support.
> >Puts SDRAM out of self-refresh and transfers control to
> >address saved at physical 0x0.
> >
>
> Hi Domen,
Hi!
>
> As I understand while waking up from the low-power mode the machine is
> effectively powering on, similarly to the cold reset, so U-Boot runs
> from the beginning as usual, but after the SDRAM controller has been
> initialised we detect the wakeup and teleport to the saved DRAM address.
Right.
>
> Since in case of a wakeup from the low-power mode we skip everything in
> U-Boot that is happening past initdram(), please clarify the following:
>
> - are you sure there are no steps beyond init_func_ram()/board_init_f()
> that should be performed while waking up? For example:
>
> - are all timers settings properly re-stored?
Hmm... right, I forgot to restart watchdog... but that will be done in
Linux code.
>
> - wouldn't the host/PCI bridge need to be re-initialised and
> re-configured as part of the wakeup process? Did you happen to test some
> PCI devices and would they survive after wakeup from the the low-power
> mode? (A similar question would apply to the USB controller)
Honestly, I don't know for PCI. IIRC some time ago, kernel compiled
with CONFIG_PCI didn't boot for me.
USB controller/devices survived the wakeup last time I checked.
>
> Also, a more general question: isn't time base update required after the
> wakeup, specially if it's been a long sleep?
Lite5200b doesn't have an external time source.
Thanks!
Domen
prev parent reply other threads:[~2007-03-31 18:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070315103959.GA22215@moe.telargo.com>
2007-03-15 10:44 ` [U-Boot-Users] [PATCH] icecube/lite5200b: wakeup from low-power support Domen Puncer
2007-03-26 16:08 ` Grant Likely
2007-04-03 8:46 ` Domen Puncer
2007-04-16 4:45 ` Grant Likely
2007-04-16 6:25 ` Domen Puncer
2007-04-16 7:10 ` Wolfgang Denk
2007-04-16 12:04 ` Stefan Roese
2007-04-16 13:08 ` Domen Puncer
2007-04-16 13:36 ` Grant Likely
2007-04-20 12:13 ` Stefan Roese
2007-04-20 13:47 ` Wolfgang Denk
2007-04-17 11:29 ` Stefan Roese
2007-04-17 14:50 ` Wolfgang Denk
2007-04-18 5:55 ` [U-Boot-Users] [PATCH] icecube/lite5200b: document " Domen Puncer
2007-03-31 17:20 ` [U-Boot-Users] [PATCH] icecube/lite5200b: " Rafal Jaworowski
2007-03-31 18:38 ` Domen Puncer [this message]
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=20070331183843.GA3143@nd47.coderock.org \
--to=domen.puncer@telargo.com \
--cc=u-boot@lists.denx.de \
/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