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:46:55 -0500	[thread overview]
Message-ID: <486BBF0F.6040607@freescale.com> (raw)
In-Reply-To: <61D15FC6-64DC-4342-B16D-4FBFF86099A9@kernel.crashing.org>

Kumar Gala wrote:
> 
> On Jul 2, 2008, at 12:12 PM, Scott Wood wrote:
> 
>> 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
> 
> I read this as the memory address 0, 0x4.  do you mean the first two 
> words of the save area?

Both.  Memory addresses 0 and 4 are saved in the first two words of the 
save area, so that we can overwrite the former with the magic number and 
resume address.

>>
>>         * 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.
> 
> ahh, might be useful to add SS_MEMSAVE into the comment.

OK.

-Scott

      reply	other threads:[~2008-07-02 17:47 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
2008-07-02 17:37     ` Kumar Gala
2008-07-02 17:46       ` Scott Wood [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=486BBF0F.6040607@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).