From mboxrd@z Thu Jan  1 00:00:00 1970
From: York Sun <yorksun@freescale.com>
Date: Thu, 15 Oct 2015 09:39:37 -0700
Subject: [U-Boot] [PATCH] arm: ls1021atwr: optimize the deep sleep
	latency
In-Reply-To: <BY2PR03MB570EA0B2084AE32DCA611D9FA3E0@BY2PR03MB570.namprd03.prod.outlook.com>
References: <1443081122-3563-1-git-send-email-Yuantian.Tang@freescale.com>
 <561ECA41.70907@freescale.com>
 <BY2PR03MB570EA0B2084AE32DCA611D9FA3E0@BY2PR03MB570.namprd03.prod.outlook.com>
Message-ID: <561FD6C9.7080603@freescale.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

>> Yuantian,
>>
>> Please explain more why the second stage u-boot is reserved? Wouldn't
>> Linux overwrite the memory?
>>
> If both CONFIG_DEEP_SLEEP and CONFIG_SD_BOOT are defined,
> The DDR memory the second stage uboot occupied whould be reserved.
> It is achieved in commit: 41ba57d0c which is the first patch to add the deep sleep support.
> 
> This patch doesn't reserve any memory, it just utilized the fact that the second stage uboot has been reserved already if deep sleep is enabled.
> 

Thanks for explanation.

York