From: Chin Liang See <clsee@altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC 4/4] arm: socfpga: scrub the SDRAM to properly enable ECC support
Date: Thu, 13 Oct 2016 00:13:39 +0800 [thread overview]
Message-ID: <1476288819.2220.30.camel@altera.com> (raw)
In-Reply-To: <20161010155223.23751-5-dinguyen@kernel.org>
On Mon, 2016-10-10 at 10:52 -0500, Dinh Nguyen wrote:
> From: Dinh Nguyen <dinguyen@opensource.altera.com>
>
> In order for SDRAM ECC to work correctly, the SDRAM needs to get
> zero'd which
> enables the ECC bit. By using the PL330 DMA to fill the SDRAM with
> zeroes,
> the operation is completed in ~1.2 seconds, versus ~14 seconds with a
> memset.
>
> Signed-off-by: Dinh Nguyen <dinguyen@opensource.altera.com>
> ---
> arch/arm/mach-socfpga/include/mach/reset_manager.h | 21
> ++++++++++++++++
> arch/arm/mach-socfpga/include/mach/sdram.h | 2 ++
> arch/arm/mach-socfpga/spl.c | 8 +++++++
> arch/arm/mach-socfpga/wrap_sdram_config.c | 28
> ++++++++++++++++++++++
> configs/socfpga_cyclone5_defconfig | 2 ++
> 5 files changed, 61 insertions(+)
>
[..]
> diff --git a/arch/arm/mach-socfpga/wrap_sdram_config.c
> b/arch/arm/mach-socfpga/wrap_sdram_config.c
> index 31cc7de..dfa6423 100644
> --- a/arch/arm/mach-socfpga/wrap_sdram_config.c
> +++ b/arch/arm/mach-socfpga/wrap_sdram_config.c
> @@ -5,8 +5,10 @@
> */
>
> #include <common.h>
> +#include <dma.h>
> #include <errno.h>
> #include <asm/arch/sdram.h>
> +#include <asm/pl330.h>
>
> /* Board-specific header. */
> #include <qts/sdram_config.h>
> @@ -310,3 +312,29 @@ const struct socfpga_sdram_misc_config
> *socfpga_get_sdram_misc_config(void)
> {
> return &misc_config;
> }
> +
> +#if (CONFIG_HPS_SDR_CTRLCFG_CTRLCFG_ECCEN == 1)
> +/* init the whole SDRAM ECC bit */
> +void sdram_ecc_init(void)
> +{
> + struct pl330_transfer_struct pl330;
> + u8 pl330_buf[2000];
Would need size of 2500 if the SDRAM size is 2GB
Thanks
Chin Liang
next prev parent reply other threads:[~2016-10-12 16:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 15:52 [U-Boot] [RFC] 0/4] Add Pl330 DMA support Dinh Nguyen
2016-10-10 15:52 ` [U-Boot] [RFC 1/4] drivers: dma: Add the ARM PL330 DMA driver Dinh Nguyen
2016-10-12 16:04 ` Chin Liang See
2016-10-10 15:52 ` [U-Boot] [RFC 2/4] dma: Kconfig: Add CONFIG_PL330_DMA entry Dinh Nguyen
2016-10-12 16:05 ` Chin Liang See
2016-10-14 15:17 ` Marek Vasut
2016-10-10 15:52 ` [U-Boot] [RFC 3/4] dm: add DMA_SUPPORTS_DEV_TO_MEM type to DMA_UCLASS Dinh Nguyen
2016-10-13 0:03 ` Simon Glass
2016-10-14 15:20 ` Marek Vasut
2016-10-10 15:52 ` [U-Boot] [RFC 4/4] arm: socfpga: scrub the SDRAM to properly enable ECC support Dinh Nguyen
2016-10-12 16:13 ` Chin Liang See [this message]
2016-10-16 16:03 ` Marek Vasut
2016-10-14 7:23 ` [U-Boot] [RFC] 0/4] Add Pl330 DMA support Marek Vasut
2016-10-14 13:08 ` Dinh Nguyen
2016-10-14 15:09 ` Marek Vasut
2016-10-14 22:13 ` Dinh Nguyen
2016-10-15 16:43 ` Marek Vasut
2016-10-14 22:10 ` Dinh Nguyen
2016-10-16 15:59 ` Marek Vasut
2016-10-18 15:50 ` Dinh Nguyen
2016-10-18 18:36 ` Marek Vasut
2016-10-29 19:59 ` Marek Vasut
2016-11-01 15:43 ` Dinh Nguyen
2016-11-01 20:09 ` Marek Vasut
2016-11-01 20:39 ` Dinh Nguyen
2016-11-01 20:42 ` Marek Vasut
2016-11-01 20:43 ` Dinh Nguyen
2016-11-02 16:30 ` Dinh Nguyen
2016-11-02 20:47 ` Marek Vasut
2016-11-03 14:21 ` Dinh Nguyen
2016-11-04 20:56 ` Marek Vasut
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=1476288819.2220.30.camel@altera.com \
--to=clsee@altera.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