public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: linux-omap@vger.kernel.org
Subject: new 2.6.30-based PM branch
Date: Wed, 17 Jun 2009 16:39:26 -0700	[thread overview]
Message-ID: <87ocsmv39t.fsf@deeprootsystems.com> (raw)

Hello,

Now that 2.6.30 is out, the PM branch has been rebased onto current
linux-omap master which is 2.6.30 based.  The previous, 2.6.29-based
PM branch will continue to exist and be renamed to pm-2.6.29.  I will
continue to accept bugfixes against pm-2.6.29, but all new work should
be done on the new pm branch.

Both branches are available in my linux-omap-pm tree[1], but only the
2.6.30-based one (named 'pm') will be sync'd daily to Tony's
linux-omap repo.

This new PM branch has had basic testing on the following OMAP3
platforms

- 3430SDP (initramfs, NFS)
- OMAP3 EVM (initramfs, NFS)
- Beagle (MMC rootfs)
- RX51 (OneNAND rootfs)
- Zoom2 (initramfs, ** problems w/NFS, see below)

And is able to do full-chip retention and off in idle and suspend on
all of these platforms.

Rather than try to manage multiple defconfigs for these boards, there
is a now a new all-in-one defconfig that will work on all these
boards.  Well, almost.  

omap3_pm_defconfig will work out of the box on SDP and EVM, and will
boot on Beagle, Zoom2 and RX51 simply by changing
    
     System Type-->TI OMAP implementations-->Low-level debug console UART
    
from UART1 to UART3 (the LL_DEBUG support is still a little dumb and
needs some fixing, but that's for another day.)

Known problems:

- Zoom2 network doesn't work, not yet debugged
- ES3.0-based SDPs have problems with UART1 coming back from off-while-idle 
  UART 3 works fine.

Kevin

[1] http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git

                 reply	other threads:[~2009-06-17 23:39 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=87ocsmv39t.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