public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/5] 8xxx: Add 'ecc' command
Date: Sat, 24 Oct 2009 16:14:25 -0500	[thread overview]
Message-ID: <4AE36E31.2060800@xes-inc.com> (raw)
In-Reply-To: <392188CC-DD39-4918-BF1D-2D92F3A70B2A@kernel.crashing.org>

Kumar Gala wrote:
> 
> On Oct 22, 2009, at 7:39 PM, Peter Tyser wrote:
> 
>> Add a new 'ecc' command to interact with the 85xx and 86xx DDR ECC
>> registers.  The 'ecc' command can inject data/ECC errors to simulate
>> errors and provides an 'info' subcommand which displays ECC error
>> information such as failure address, read vs expected data/ECC,
>> physical signal which failed, single-bit error count, and multiple bit
>> error occurrence.  An example of the 'ecc info' command follows:
>>
>> WARNING: ECC error in DDR Controller 0
>>        Addr:   0x0_01001000
>>        Data:   0x00000001_00000000     ECC:    0x00
>>        Expect: 0x00000000_00000000     ECC:    0x00
>>        Net:    DATA32
>>        Syndrome: 0xce
>>        Single-Bit errors: 0x40
>>        Attrib: 0x30112001
>>        Detect: 0x80000004 (MME, SBE)
>>
>> Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
>> Signed-off-by: John Schmoller <jschmoller@xes-inc.com>
>> ---
>> This code was tested on a 8572, 8640, and P2020.  A board with a
>> 32-bit data bus was not tested however.
>>
>> cpu/mpc8xxx/ddr/Makefile     |    2 +
>> cpu/mpc8xxx/ddr/ecc.c        |  371 
>> ++++++++++++++++++++++++++++++++++++++++++
>> include/asm-ppc/immap_85xx.h |    4 +
>> include/asm-ppc/immap_86xx.h |    3 +
>> 4 files changed, 380 insertions(+), 0 deletions(-)
>> create mode 100644 cpu/mpc8xxx/ddr/ecc.c
>>
>> diff --git a/cpu/mpc8xxx/ddr/Makefile b/cpu/mpc8xxx/ddr/Makefile
>> index cb7f856..f073779 100644
>> --- a/cpu/mpc8xxx/ddr/Makefile
>> +++ b/cpu/mpc8xxx/ddr/Makefile
>> @@ -22,6 +22,8 @@ COBJS-$(CONFIG_FSL_DDR3)    += main.o util.o 
>> ctrl_regs.o options.o \
>>                    lc_common_dimm_params.o
>> COBJS-$(CONFIG_FSL_DDR3)    += ddr3_dimm_params.o
>>
>> +COBJS-$(CONFIG_DDR_ECC_CMD)    += ecc.o
> 
> Should this be CONFIG_FSL_DDR_ECC_CMD ?

I leaned towards CONFIG_DDR_ECC_CMD to prevent polluting the CONFIG_ 
namespace.  We could add a new CONFIG_FSL_DDR_ECC_CMD, 
CONFIG_AVR32_DDR_ECC_CMD, etc, but I think (CONFIG_MPC85xx + 
CONFIG_DDR_ECC_CMD), (CONFIG_AVR32 + CONFIG_DDR_ECC_CMD), etc 
accomplishes the same thing, but only adds 1 new CONFIG_DDR_ECC_CMD 
config option.  Doesn't really matter to me either way though...

Peter

  reply	other threads:[~2009-10-24 21:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23  0:39 [U-Boot] [PATCH 1/5] 8xxx: Add 'ecc' command Peter Tyser
2009-10-23  0:39 ` [U-Boot] [PATCH 2/5] Add check for ECC errors during SDRAM POST and mtest Peter Tyser
2009-10-23  0:39 ` [U-Boot] [PATCH 3/5] xes: Enable the 'ecc' command Peter Tyser
2009-11-23 22:35   ` Wolfgang Denk
2009-11-24  4:36     ` Peter Tyser
2009-10-23  0:39 ` [U-Boot] [PATCH 4/5] xes: Enable memory POST Peter Tyser
2009-10-23  0:39 ` [U-Boot] [PATCH 5/5] xes: Enable ECC error checks during SDRAM POST and mtest Peter Tyser
2009-10-24 15:41 ` [U-Boot] [PATCH 1/5] 8xxx: Add 'ecc' command Kumar Gala
2009-10-24 21:14   ` Peter Tyser [this message]
2009-10-24 17:21 ` Wolfgang Denk
2009-10-24 21:30   ` Peter Tyser
2009-10-24 21:37     ` Wolfgang Denk
2009-10-24 21:43       ` Peter Tyser

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=4AE36E31.2060800@xes-inc.com \
    --to=ptyser@xes-inc.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