linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: m-karicheri2@ti.com (Murali Karicheri)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: keystone: ecc: add ddr3 ecc interrupt handling
Date: Mon, 22 Jun 2015 16:50:41 -0400	[thread overview]
Message-ID: <55887521.7010708@ti.com> (raw)
In-Reply-To: <558436C1.3050402@oracle.com>

On 06/19/2015 11:35 AM, santosh shilimkar wrote:
> On 6/18/2015 12:09 PM, Vitaly Andrianov wrote:
>> This patch adds ARM L1/L2 ECC handler support and DDR3 ECC interrupt
>> handling for Keystone II devices, the kernel will reboot if the error
>> is 2-bit error for DDR ECC or L1/L2 ECC error.
>>
>> Signed-off-by: Hao Zhang <hzhang@ti.com>
>> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
>> Signed-off-by: Vitaly Andrianov <vitalya@ti.com>
>> ---
>>   arch/arm/mach-keystone/Makefile       |  2 +-
>>   arch/arm/mach-keystone/keystone.c     | 63 ++++++++++++++++++++++++--
>>   arch/arm/mach-keystone/keystone.h     |  1 +
>>   arch/arm/mach-keystone/keystone_ecc.c | 85
>> +++++++++++++++++++++++++++++++++++
>>   arch/arm/mach-keystone/platsmp.c      |  3 +-
>>   5 files changed, 148 insertions(+), 6 deletions(-)
>>   create mode 100644 arch/arm/mach-keystone/keystone_ecc.c
>>

>>
>> @@ -49,6 +54,56 @@ static int keystone_platform_notifier(struct
>> notifier_block *nb,
>>       return NOTIFY_OK;
>>   }
>>
> +RMK. Would like to know if he wish to have below code in
> generic ARM code
>
>> +#define L2_INTERN_ASYNC_ERROR  BIT(30)
>> +
>> +static irqreturn_t arm_l1l2_ecc_err_irq_handler(int irq, void *reg_virt)
>> +{
>> +    int ret = IRQ_NONE;
>> +    u32 status, fault;
>> +
>> +    /* read and clear L2ECTLR CP15 register for L2 ECC error */
>> +    asm("mrc p15, 1, %0, c9, c0, 3" : "=r"(status));
>> +
>> +    if (status & L2_INTERN_ASYNC_ERROR) {
>> +        status &= ~L2_INTERN_ASYNC_ERROR;
>> +        asm("mcr p15, 1, %0, c9, c0, 3" : : "r" (status));
>> +        asm("mcr p15, 0, %0, c5, c1, 0" : "=r" (fault));
>> +        /*
>> +         * Do a machine restart as this is double bit ECC error
>> +         * that can't be corrected
>> +         */
>> +        pr_err("ARM Cortex A15 L1/L2 ECC error, CP15 ADFSR 0x%x\n",
>> +               fault);
>> +        machine_restart(NULL);
>> +        ret = IRQ_HANDLED;
>> +    }
>> +    return ret;
> So your non-double bit errors even though handled returns as IRQ_NONE.

looking at the A15 TRM, I see only single and double bit errors
are documented. There is no discussion about more than 2 bit errors.
Single bit errors don't raise an interrupt. So only case this gets 
called should be for double bit which is handled. So just log an error 
message as below and return IRQ_HANDLED?

pr_err("Unexpected ARM Cortex A15 L1/L2 multi bit error");

Murali

>
>> +}
>> +
>> +static int __init keystone_init_misc(void)


-- 
Murali Karicheri
Linux Kernel, Keystone

  parent reply	other threads:[~2015-06-22 20:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 19:09 [PATCH] ARM: keystone: ecc: add ddr3 ecc interrupt handling Vitaly Andrianov
2015-06-19 15:35 ` santosh shilimkar
2015-06-22 20:23   ` Murali Karicheri
2015-06-22 21:21     ` santosh shilimkar
2015-06-22 20:50   ` Murali Karicheri [this message]
2015-06-22 21:23     ` santosh shilimkar

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=55887521.7010708@ti.com \
    --to=m-karicheri2@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).