linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC][PATCH 1/1] ARM: Add initial hibernation support
Date: Fri, 16 Jul 2010 08:52:44 +0100	[thread overview]
Message-ID: <20100716075243.GB16124@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100715.120807.39160135.Hiroshi.DOYU@nokia.com>

On Thu, Jul 15, 2010 at 12:08:07PM +0300, Hiroshi DOYU wrote:
> From: ext Russell King - ARM Linux <linux@arm.linux.org.uk>
> Subject: Re: [RFC][PATCH 1/1] ARM: Add initial hibernation support
> Date: Thu, 15 Jul 2010 10:41:18 +0200
> 
> > On Thu, Jul 15, 2010 at 08:34:50AM +0300, Hiroshi DOYU wrote:
> >> Russell, would it be possible to put this into your next merge queue?
> > 
> > I think it needs quite a bit of rework - I certainly don't like all
> > those CP15 register accesses there - that's asking for lots of ifdefs
> > to spring up as more CPUs are supported.
> >
> > Eg, what about ensuring that state such as iWMMXt on PXA CPUs is
> > properly restored?
> 
> Right. This arch specific part can be something like
> "suspend-v[3-7].S" to accomodate those differences

It's not quite that simple - things like iWMMXt aren't part of the ARM
arch specs.

> > We already have code which knows what needs to be saved across a
> > power-off transition - its what we use for our normal suspend/resume
> > functionality, so we should look at re-using that code for hibernate
> > as well.  We really don't want to be maintaining two sets of code
> > doing the same thing.
> 
> Could you explain which code you're refering for the existing one?

The code which handles saving state for the existing suspend/resume
support.  This code already saves the necessary state from CP15 and
any other state which needs to be saved prior to putting the system
into low power mode.

Every machine class which supports suspend today has their own chunk
of code which does this, normally called something like sleep.S

  reply	other threads:[~2010-07-16  7:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30 14:28 [RFC][PATCH 0/1] ARM: Add initial hibernation support Hiroshi DOYU
2010-06-30 14:28 ` [RFC][PATCH 1/1] " Hiroshi DOYU
2010-07-14 13:22   ` Pavel Machek
2010-07-15  5:34     ` Hiroshi DOYU
2010-07-15  8:41       ` Russell King - ARM Linux
2010-07-15  9:08         ` Hiroshi DOYU
2010-07-16  7:52           ` Russell King - ARM Linux [this message]
2010-07-16  8:48             ` Shilimkar, Santosh
2010-07-16  9:18               ` Hiroshi DOYU
2010-07-16  9:10             ` Hiroshi DOYU
2010-08-30 22:23               ` Kevin Hilman
2010-07-15  4:48   ` Marek Vasut
2010-07-15  5:39     ` Hiroshi DOYU
2010-07-15  5:56       ` Marek Vasut
2010-07-15  6:00         ` Hiroshi DOYU
2010-07-15  6:04           ` Marek Vasut
2010-07-17 13:51             ` Marek Vasut
     [not found]             ` <4CD00106.8000001@panicking.kicks-ass.org>
2010-11-02 15:09               ` Marek Vasut
2010-11-26  7:39   ` MyungJoo Ham

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=20100716075243.GB16124@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).