From: "Rajendra Nayak" <rnayak@ti.com>
To: linux-omap@vger.kernel.org
Cc: 'Kevin Hilman' <khilman@deeprootsystems.com>
Subject: [PATCH 00/05] OMAP3: CPUidle driver
Date: Wed, 8 Oct 2008 17:30:33 +0530 [thread overview]
Message-ID: <001601c9293d$79bd4200$LocalHost@wipultra1382> (raw)
Hi,
This patch set implements Cpuidle driver for OMAP3 platforms. It is validated on the 3430SDP (using the
omap_3430sdp_min_defconfig) and applies on the pm-20081006 branch.
The following C states are defined and used
* C0 . System executing code (Not an idle state)
* C1 . MPU WFI + Core active
* C2 . MPU CSWR + Core active
* C3 . MPU OFF + Core active
* C4 . MPU CSWR + Core CSWR
* C5 . MPU OFF + Core CSWR
* C6 . MPU OFF + Core OFF
CPUidle support is not enabled by default in any of the defconfigs and hence has to enabled seperately
if you plan to test these patches.
CPUIdle ---> [*] CPU idle PM support
regards,
Rajendra
next reply other threads:[~2008-10-08 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 12:00 Rajendra Nayak [this message]
2008-10-09 13:27 ` [PATCH 00/05] OMAP3: CPUidle driver Kevin Hilman
2008-10-09 14:44 ` Kevin Hilman
2008-10-10 3:47 ` Rajendra Nayak
2008-10-14 10:41 ` Rajendra Nayak
2008-10-18 14:18 ` Kevin Hilman
2008-10-10 3:44 ` Rajendra Nayak
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='001601c9293d$79bd4200$LocalHost@wipultra1382' \
--to=rnayak@ti.com \
--cc=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