From: Peter Barada <peterb@logicpd.com>
To: linux-omap <linux-omap@vger.kernel.org>
Subject: Power Management question...
Date: Mon, 29 Dec 2008 21:31:47 -0500 [thread overview]
Message-ID: <1230604308.7951.4.camel@blackhole> (raw)
I'm trying to put together a 2.6.27 (from the 2.6.27 tag) kernel with
power management, and what I'm seeing is a bit weird...
When I put it into "mem" state (i.e. save to DRAM and sleep the world,
leaving DRAM alive), I see current consumption actually *increase*.
Also, any interrupt (touch, serial, mmc insert/removal) automagicaly
wakes it up.
Any pointers on how to make sense of this? I would have thought that
drivers have to specify which interrupts are capable of waking the
core...
--
Peter Barada <peterb@logicpd.com>
reply other threads:[~2008-12-30 2:31 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=1230604308.7951.4.camel@blackhole \
--to=peterb@logicpd.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