public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2 v2] mpc85xx/t104x: Add deep sleep framework support
Date: Tue, 11 Mar 2014 09:03:37 -0700	[thread overview]
Message-ID: <531F33D9.7060805@freescale.com> (raw)
In-Reply-To: <7f6f79601f34418e9c6d4e07331efd8b@BL2PR03MB115.namprd03.prod.outlook.com>

On 03/10/2014 11:16 PM, Tang Yuantian-B29983 wrote:
>> -----Original Message-----
>> From: Sun York-R58495
>> Sent: Tuesday, March 11, 2014 1:45 AM
>> To: Tang Yuantian-B29983
>> Cc: u-boot at lists.denx.de; Li Yang-Leo-R58472; Jin Zhengxiong-R64188; Wood
>> Scott-B07421
>> Subject: Re: [PATCH 2/2 v2] mpc85xx/t104x: Add deep sleep framework
>> support
>>
>> On 02/28/2014 03:09 AM, Yuantian.Tang at freescale.com wrote:
>>> From: Tang Yuantian <yuantian.tang@freescale.com>
>>>
>>> When T104x soc wakes up from deep sleep, control is passed to the
>>> primary core that starts executing uboot. After re-initialized some IP
>>> blocks, like DDRC, kernel will take responsibility to continue to
>>> restore environment it leaves before.
>>>
>>> Signed-off-by: Tang Yuantian <Yuantian.Tang@freescale.com>
>>> ---
>>> v2:
>>> 	- added explaination for CONFIG_DEEP_SLEEP
>>> 	- fixed some issues
>>>
>>>  README                                 |  4 +++
>>>  arch/powerpc/cpu/mpc85xx/asm-offsets.c | 24 ++++++++++++++
>>
>> Please fix the out-of-tree compiling issue. You will see it if you run
>> make with O=<path> parameter.
>>
>> York
> 
> Could you be more specific? What *path* should I give?
> If I do the below, I got error:
> 
> $ make O=/home/tangyt/opensource/u-boot/
>   /home/tangyt/opensource/u-boot is not clean, please run 'make mrproper'
>   in the '/home/tangyt/opensource/u-boot' directory.
> make[1]: *** [prepare3] Error 1
> make: *** [sub-make] Error 2
> 

It is out-of-tree compiling. You should use a clean path.

cd <u-boot source)
mkdir ../build
make O=../build T1040QDS_config
make O=../build

You should add other flags you normally use.

York

  parent reply	other threads:[~2014-03-11 16:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 11:09 [U-Boot] [PATCH 1/2 v2] mpc85xx: Add support for the supplement configuration unit register Yuantian.Tang at freescale.com
2014-02-28 11:09 ` [U-Boot] [PATCH 2/2 v2] mpc85xx/t104x: Add deep sleep framework support Yuantian.Tang at freescale.com
2014-03-10 17:44   ` York Sun
2014-03-11  6:16     ` Yuantian Tang
2014-03-11  6:22       ` Prabhakar Kushwaha
2014-03-11 16:03       ` York Sun [this message]
2014-03-12  6:52         ` Yuantian Tang

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=531F33D9.7060805@freescale.com \
    --to=yorksun@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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