From: "Eugeny S. Mints" <eugeny.mints@gmail.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: Sat, 02 May 2009 13:31:24 +0400 [thread overview]
Message-ID: <49FC12EC.7030609@gmail.com> (raw)
In-Reply-To: <1241203145.18100.370.camel@blackhole>
Peter,
Peter Barada wrote:
> 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.
>
> This is due to no code calling suspend_set_ops() which used to be in
> arch/arm/mach-omap2/pm34xx.c - this isn't in either Tony or Kevin's
> current tree.
>
> 1) Am I way off base (i.e. am I missing something obvious here)?
>
check out Kevin's email "Re: n800 high idle power consumption" on 4/24
on this list. TBH
I haven't checked pm branch recently so have no idea if re-basing is
complete and if it
causes the issue you found.
Thanks,
Eugeny
next prev parent reply other threads:[~2009-05-02 9:31 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 [this message]
2009-05-05 14:54 ` 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=49FC12EC.7030609@gmail.com \
--to=eugeny.mints@gmail.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