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 2/2] ARM: CSR: add PM sleep entry for SiRFprimaII
Date: Mon, 15 Aug 2011 09:20:27 +0100	[thread overview]
Message-ID: <20110815082027.GA26827@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAGsJ_4yigTt40g0-9jrz5qAbdrQdsXuQ65MhX+x1AZ1M4Ztr=w@mail.gmail.com>

On Mon, Aug 15, 2011 at 03:43:13PM +0800, Barry Song wrote:
> Sorry, my fault. i simply picked these lines which have been verified
> to be working in local old 2.6.38.8 kernel and really didn't think and
> refine more carefully.
> in deep sleep mode, SiRFprimaII will powerdown CPU core.

... just like everyone else.

> due to this,
> i just ignored to delete the codes saving registers of all kinds of
> CPU modes. but it is not the real situation in kernel. For example,
> IRQ mode used the stack of corrupted thread, and kernel was not in
> interrupt while going to pm_ops->enter(), then it is unnecessary to
> enter IRQ and save sp of IRQ:

No.  There is _no_ need to save and restore these registers.  They
can simply be re-setup.  The generic cpu_suspend stuff already
takes care of that.

> Ok. agree. then the work flow for SiRFprimaII suspend can be:
> pm.enter()->
>     sirfsoc_cpu_sleep(v:p offset)
>     1. save registers on stack
>     2. load sirfsoc_cpu_resume to r3
>     3. bl cpu_suspend
>     4. make sdram self-refresh
>     5. write force DEEPSLEEP by rtciobrg
> 
> One issue is L2

That's why I did not include it in the list of code which could be
eliminated.

  parent reply	other threads:[~2011-08-15  8:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05  2:54 [RFC PATCH 0/2] ARM: CSR: add rtciobrg and PM sleep entry Barry Song
2011-08-05  2:54 ` [RFC PATCH 1/2] ARM: CSR: add rtc i/o bridge interface for SiRFprimaII Barry Song
2011-08-05 10:09   ` Jamie Iles
2011-08-05 11:28     ` Barry Song
2011-08-05 11:32       ` Jamie Iles
2011-08-05 12:19         ` Barry Song
2011-08-05  2:54 ` [RFC PATCH 2/2] ARM: CSR: add PM sleep entry " Barry Song
2011-08-12 13:54   ` Arnd Bergmann
2011-08-17  1:37     ` Barry Song
2011-08-17 11:48       ` Arnd Bergmann
2011-08-18  2:01         ` Barry Song
2011-08-18 10:35           ` Arnd Bergmann
2011-08-18 11:58             ` Barry Song
2011-08-14  7:59   ` Russell King - ARM Linux
2011-08-15  7:43     ` Barry Song
2011-08-15  7:54       ` Barry Song
2011-08-15  8:20       ` Russell King - ARM Linux [this message]
2011-08-15  8:27         ` Barry Song
2011-08-16  1:34           ` Barry Song
2011-08-21  8:53             ` Russell King - ARM Linux
2011-08-21 12:54               ` Barry Song

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=20110815082027.GA26827@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).