From: "Rajendra Nayak" <rnayak@ti.com>
To: 'Kevin Hilman' <khilman@deeprootsystems.com>
Cc: linux-omap@vger.kernel.org
Subject: RE: [PATCH 00/05] OMAP3: CPUidle driver
Date: Fri, 10 Oct 2008 09:17:30 +0530 [thread overview]
Message-ID: <00dd01c92a8a$ebd26f20$LocalHost@wipultra1382> (raw)
In-Reply-To: <87hc7lu8tc.fsf@deeprootsystems.com>
> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org
> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Kevin Hilman
> Sent: Thursday, October 09, 2008 8:15 PM
> To: Rajendra Nayak
> Cc: linux-omap@vger.kernel.org
> Subject: Re: [PATCH 00/05] OMAP3: CPUidle driver
>
> Kevin Hilman <khilman@deeprootsystems.com> writes:
>
> > "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.
>
> I got this to work on custom HW, but not on 3430SDP. Can you confirm
> whether or not you can use C6 on 3430SDP? Off-in-idle without CPUidle
> seems to work, but not with CPUidle + C6.
Ok.. I'll try and fix this. I seem to have missed enabling this after all
the comment fixes that I did. Maybe I broke something.
>
> Kevin
>
> > 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
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2008-10-10 3:47 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
2008-10-09 14:44 ` Kevin Hilman
2008-10-10 3:47 ` Rajendra Nayak [this message]
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='00dd01c92a8a$ebd26f20$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