All of lore.kernel.org
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: ls1021atwr: optimize the deep sleep latency
Date: Thu, 15 Oct 2015 09:39:37 -0700	[thread overview]
Message-ID: <561FD6C9.7080603@freescale.com> (raw)
In-Reply-To: <BY2PR03MB570EA0B2084AE32DCA611D9FA3E0@BY2PR03MB570.namprd03.prod.outlook.com>

>> 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

  reply	other threads:[~2015-10-15 16:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24  7:52 [U-Boot] [PATCH] arm: ls1021atwr: optimize the deep sleep latency Tang Yuantian
2015-10-14 21:33 ` York Sun
2015-10-15  1:28   ` Yuantian Tang
2015-10-15 16:39     ` York Sun [this message]
2015-10-30 16:21 ` York Sun

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=561FD6C9.7080603@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.