From: Kevin Hilman <khilman@deeprootsystems.com>
To: linux-omap@vger.kernel.org
Subject: next PM branch preview
Date: Tue, 05 May 2009 11:11:52 -0700 [thread overview]
Message-ID: <87hbzz8lnb.fsf@deeprootsystems.com> (raw)
Hello,
I've rebased the PM branch on to current linux-omap HEAD (currently
2.6.30-rc4) and it is available from my tree[1] as the branch named
'pm-next'
There's still a couple issues for me to work, out but since people
have been asking, I've made it publicly available.
So far, I have only tested full-chip retention in suspend and PM idle
(not CPUidle) using minimal kernels on the following platforms:
- 3430SDP: initramfs
- RX51: OneNAND rootfs
- OMAP3EVM: initramfs
- Beagle: initramfs
Not tested:
- CPUidle
- DVFS (CPUfreq)
Known issues:
- 3430SDP: CORE pwrdm does not hit retention
- hangs on return from OFF
- OMAP3EVM: debounce used on TS GPIO (in GPIO6) and result in
"Clock gpio6_dbck didn't enable in 100000 tries"
Also note that I only build minimal kernels using very few drivers.
So I've also added the defconfigs I used for the boards so it's clear
what I'm using to test. They are named *_pm_defconfig.
Kevin
[1] http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git
reply other threads:[~2009-05-05 18:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87hbzz8lnb.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.