From: Kevin Hilman <khilman@deeprootsystems.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 00/16] OMAP3: Context save/Restore + OFF mode support
Date: Tue, 30 Sep 2008 17:26:56 +0300 [thread overview]
Message-ID: <87r671btfz.fsf@deeprootsystems.com> (raw)
In-Reply-To: <01f101c91fd1$c6c95900$LocalHost@wipultra1382> (Rajendra Nayak's message of "Fri\, 26 Sep 2008 17\:46\:57 +0530")
"Rajendra Nayak" <rnayak@ti.com> writes:
> This patch set adds context save/restore routines for minimal kernel and OFF mode
> support in idle and suspend. This patch set applies on top of pm-1 branch.
>
> This has context save/restore support implemented for the following modules
> GPMC, UART, GPIO, I2C, PRCM, INTC, SCM, SRAM.
>
> A sysfs knob to dynamically control OFF mode is provided at
> /sys/power/enable_off_mode. This is set to 0 (disabled) by default.
>
Hi Rajendra,
This series is in much better shape, and allows me to hit retention or
OFF in idle and suspend. Thanks!
I will pull this series into pm-1 tomorrow. There are few minor
things that I will cleanup upon merging.
- common:
- in several new functions, no space between local variable
definition and start of code
- copyright 2007 additions. Shouldn't these be 2008?
- 6/16: INTC
- remove the comment MIRs being saved with PRCM since this is no longer true
- 11/16: PER/NEON
- checkpatch warnings
- 15/16: /sys/power/enable_off_mode
- your method doesn't quite work, I have an alternative
- 14/16: CORE off
- checkpatch errors and warnings
Thanks,
Kevin
prev parent reply other threads:[~2008-09-30 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 12:16 [PATCH 00/16] OMAP3: Context save/Restore + OFF mode support Rajendra Nayak
2008-09-30 14:26 ` Kevin Hilman [this message]
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=87r671btfz.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