linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/3] mpc83xx: Power Management support
Date: Wed, 02 Jul 2008 12:12:03 -0500	[thread overview]
Message-ID: <486BB6E3.1060602@freescale.com> (raw)
In-Reply-To: <7B906E0F-3149-43F0-815A-8314BF5BA039@kernel.crashing.org>

Kumar Gala wrote:
>> +#define SS_MEMSAVE    0x00
> 
> What is this? add a comment?

There's a comment where MEMSAVE is used:

         /* The first 2 words of memory are used to communicate with the
          * bootloader, to tell it how to resume.
          *
          * The first word is the magic number 0xf5153ae5, and the second
          * is the pointer to mpc83xx_deep_resume.
          *
          * The original content of these two words is saved in the state
          * save area.
          */

We could stick a /* First 8 bytes of RAM */ after the #define if you want.

>> +#define SS_HID        0x08 /* 3 HIDs */
>> +#define SS_IABR        0x14 /* 2 IABRs */
>> +#define SS_IBCR        0x1c
>> +#define SS_DABR        0x20 /* 2 DABRs */
>> +#define SS_DBCR        0x28
>> +#define SS_SP        0x2c
>> +#define SS_SR        0x30 /* 16 segment registers */
>> +#define SS_CURRENT    0x70
> 
> How about SS_R2 to match the pmac sleep.S code.  It will make 
> refactoring all this easier in the future.

OK.

-Scott

  reply	other threads:[~2008-07-02 17:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25 21:50 [PATCH 1/3] mpc83xx: Power Management support Scott Wood
2008-06-26 13:43 ` Kumar Gala
2008-06-26 14:07   ` Scott Wood
2008-06-26 14:39   ` Liu Dave
2008-06-26 14:54     ` Kumar Gala
2008-07-02 16:03 ` Kumar Gala
2008-07-02 16:38   ` Scott Wood
2008-07-02 17:06 ` Kumar Gala
2008-07-02 17:12   ` Scott Wood [this message]
2008-07-02 17:37     ` Kumar Gala
2008-07-02 17:46       ` Scott Wood

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=486BB6E3.1060602@freescale.com \
    --to=scottwood@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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).