From: Kevin Hilman <khilman@deeprootsystems.com>
To: linux-omap@vger.kernel.org
Subject: PM branch update: rebase to .31-rc, added omap_hwmod/omap_device
Date: Mon, 20 Jul 2009 17:19:42 -0700 [thread overview]
Message-ID: <87fxcqq44h.fsf@deeprootsystems.com> (raw)
The PM branch hosted in my linux-omap-pm repo[1] has been updated.
Significant changes:
- rebased to omap/master (currently v2.6.31-rc1)
- Using new omap_hwmod and omap_device infrastructure from Paul Walmsley
- more reorg into groups of commits for easier submission upstream
Tested on the following platforms using omap3_pm_defconfig with
busybox-based initramfs, and tested full-chip RET and OFF in idle and
suspend:
- 3430SDP
- OMAP3EVM
- Beagle
- Overo
- RX51
- Zoom2 (use 'pm-staging/zoom2' branch as well, which is Vikram's
zoom2 branch rebased on top of PM branch with DEBUG_LL
support and misc. fixes)
Known problems:
- no DVFS because of next item...
- SRF driver broken, needs update for new hwmod/omap_device layer
(default config used PM NOOP)
- network drivers and off-mode
- various hangs when using off-while-idle and NFS-mounted rootfs
- network drivers likely need some context save/restore support
- SDRAM on 2 CSes (Beagle, Overo, RX51)
- need to boot with mem=128M so only a single CS is used
- 2 CS support patches from Jean Pihet solve this problem,
but not yet merged.
- 3430SDP ES3.0
- UART1 doesn't come back from off-while-idle (ok on es3.1 SDP)
[1] http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git
next reply other threads:[~2009-07-21 0:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 0:19 Kevin Hilman [this message]
2009-08-12 14:37 ` PM branch update: rebase to .31-rc, added omap_hwmod/omap_device Hemanth V
2009-08-12 14:58 ` Kevin Hilman
2009-08-13 6:00 ` Reddy, Teerth
2009-08-13 13:03 ` Kevin Hilman
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=87fxcqq44h.fsf@deeprootsystems.com \
--to=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.