public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: jean.pihet@newoldbits.com, linux-omap@vger.kernel.org,
	santosh.shilimkar@ti.com, linux-arm-kernel@lists.infradead.org,
	Jean Pihet <j-pihet@ti.com>
Subject: Re: [PATCH] OMAP3: run the ASM sleep code from DDR
Date: Wed, 29 Jun 2011 16:30:13 -0700	[thread overview]
Message-ID: <87wrg4p662.fsf@ti.com> (raw)
In-Reply-To: <20110629215423.GI23312@n2100.arm.linux.org.uk> (Russell King's message of "Wed, 29 Jun 2011 22:54:23 +0100")

Russell King - ARM Linux <linux@arm.linux.org.uk> writes:

> On Wed, Jun 29, 2011 at 12:06:07PM -0700, Kevin Hilman wrote:
>> Russell King - ARM Linux <linux@arm.linux.org.uk> writes:
>> 
>> > On Wed, Jun 29, 2011 at 10:29:49AM -0700, Kevin Hilman wrote:
>> >> Russell, if you're OK with it, can you add it to your suspend branch for
>> >> the upcoming merge window?
>> >
>> > Yes - though I think we can go a little bit further - this patch is on
>> > top of my code so far, and is untested.  There isn't a need for the
>> > saving of these registers to be in assembly because we can read them
>> > just as easily from C code.
>> 
>> Indeed
>> 
>> > Comments?
>> 
>> Looks good to me (although untested) care to respin on top of $SUBJECT
>> patch?  
>> 
>> Minor comments below...
>
> Done.

Tested-by: Kevin Hilman <khilman@ti.com>

Tested full-chip retention and off on 3430/n900, 3530/Overo and
3630/Zoom3.

Kevin


  reply	other threads:[~2011-06-29 23:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29 16:40 [PATCH] OMAP3: run the ASM sleep code from DDR jean.pihet
2011-06-29 17:29 ` Kevin Hilman
2011-06-29 17:48   ` Jean Pihet
2011-06-29 18:05   ` Russell King - ARM Linux
2011-06-29 19:06     ` Kevin Hilman
2011-06-29 21:54       ` Russell King - ARM Linux
2011-06-29 23:30         ` Kevin Hilman [this message]
2011-06-29 21:45 ` Russell King - ARM Linux
2011-06-30  8:55 ` Peter De Schrijver
2011-07-12  6:07 ` Pavel Machek
2011-07-13  8:14   ` Paul Walmsley
  -- strict thread matches above, loose matches on Subject: below --
2011-06-17  8:52 jean.pihet
2011-06-17  9:51 ` Santosh Shilimkar
2011-06-24  0:17 ` Kevin Hilman
2011-06-24  8:32   ` Jean Pihet
2011-06-24 14:42     ` Kevin Hilman

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=87wrg4p662.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=j-pihet@ti.com \
    --cc=jean.pihet@newoldbits.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=santosh.shilimkar@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