From: Kevin Hilman <khilman@deeprootsystems.com>
To: Peter Barada <peterb@logicpd.com>
Cc: linux-omap <linux-omap@vger.kernel.org>
Subject: Re: No OMAP PM code on the PM branch???
Date: Tue, 05 May 2009 07:54:34 -0700 [thread overview]
Message-ID: <87ljpb4n2t.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1241203145.18100.370.camel@blackhole> (Peter Barada's message of "Fri\, 01 May 2009 14\:39\:05 -0400")
Peter Barada <peterb@logicpd.com> writes:
> I'm looking through Kevin's PM branch, and I've done a quick-port of
> 2.6.30-rc1 to Logic's OMAP3530 LV SOM starting with the rk21 board code,
> and "echo mem > /sys/power/state" does nothing. Worse,
> "cat /sys/power/state" doesn't show anything.
Since 2.6.30, there is no OMAP PM code in linux-omap master branch.
The only working PM is now in the PM branch.
I am currently rebasing the PM branch to 2.6.30-rc series and it
should be published this week.
Kevin
prev parent reply other threads:[~2009-05-05 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 18:39 No OMAP PM code on the PM branch??? Peter Barada
2009-05-02 9:31 ` Eugeny S. Mints
2009-05-05 14:54 ` Kevin Hilman [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=87ljpb4n2t.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=peterb@logicpd.com \
/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