From: Kevin Hilman <khilman@deeprootsystems.com>
To: linux-omap@vger.kernel.org
Subject: PM branch updated
Date: Tue, 30 Jun 2009 18:31:32 -0700 [thread overview]
Message-ID: <87ocs51957.fsf@deeprootsystems.com> (raw)
Hello,
I just pushed an updated PM branch to my linux-omap-pm repo[1], and it
will be sync'd to Tony's linux-omap tree shortly.
What's changed: Not many functional changes, but lots of restructuring
to organize/regroup patches into changesets for upstream. In addition
to the various fixes coming in from the list, here are some other
user-visible changes:
- 600 MHz OPP (a.k.a. overdrive) allowed in CPUfreq
- default CPUfreq governor: userspace, so default OPP is determined
by bootloader, and not changed during kernel boot
- UARTs obey /sys/devices/.../power/wakeup
- serial ports separated so each port can be controlled
separately under /sys/devices
Basic retention/off while idle and suspend testing on the following
OMAP3 boards:
- 3430SDP (NFS root)
- OMAP3EVM (NFS root)
- Beagle (MMC rootfs)
- RX51 (OneNAND rootfs)
- Overo (Water + Tobi) (thanks to Gumstix for the hardware!)
** Known problems: retention during idle eventually hangs with what
looks like memory corruption (not debugged further.) Looks like
Overo support in linux-omap needs some updates, including a
sanity check of the SDRC settings.
Upcoming changes:
The next PM branch will drop the current omapdev code and replace it
with the latest versions of omap_hwmod and omap_device code from Paul
Walmsely.
Kevin
next reply other threads:[~2009-07-01 1:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 1:31 Kevin Hilman [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-06 1:14 PM branch updated Kevin Hilman
2009-08-06 11:22 ` Roger Quadros
2009-08-06 17:13 ` Kevin Hilman
2009-08-07 8:29 ` Jean Pihet
2009-08-07 17:11 ` Kevin Hilman
2009-08-10 8:26 ` Jean Pihet
2009-08-23 21:40 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=87ocs51957.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox