From: Kevin Hilman <khilman@deeprootsystems.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 00/05] OMAP3: CPUidle driver
Date: Thu, 09 Oct 2008 16:27:17 +0300 [thread overview]
Message-ID: <87prm9ucei.fsf@deeprootsystems.com> (raw)
In-Reply-To: <001601c9293d$79bd4200$LocalHost@wipultra1382> (Rajendra Nayak's message of "Wed\, 8 Oct 2008 17\:30\:33 +0530")
"Rajendra Nayak" <rnayak@ti.com> writes:
> 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.
Excellent. Thank you. I'll pull into pm-20081006 today.
One question: You have C6 to hit chip-off, but it is never enabled.
Has this been tested? Enabling it allows me to hit chip OFF, but it
never comes back from OFF-mode. I will push some patches to make this
work with /sys/power/enable_off_mode.
Some minor problems that I will fixup when rebasing to the next pm
branch:
- You removed C0, but all the comments still refer to it
- /sys/power/enable_off_mode doesn't affect off-mode states
in CPUidle
patch 1:
- I still don't like the #ifdefs for the init sequence.
patch 2:
- checkpatch warning
Kevin
> 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 prev parent reply other threads:[~2008-10-09 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 12:00 [PATCH 00/05] OMAP3: CPUidle driver Rajendra Nayak
2008-10-09 13:27 ` Kevin Hilman [this message]
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=87prm9ucei.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.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