linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matthew McClintock <msm@freescale.com>
To: <linuxppc-dev@lists.ozlabs.org>, <kumar.gala@freescale.com>
Subject: [PATCH 1/5] powerpc/85xx: issue 15 EOI after core reset for FSL CoreNet devices
Date: Wed, 26 Oct 2011 13:13:17 -0500	[thread overview]
Message-ID: <1319652797-28017-1-git-send-email-msm@freescale.com> (raw)
In-Reply-To: <08F58B37-0825-4C07-91B3-1040A7E70528@freescale.com>

This is listed as a requirement for Freescale CoreNet based devices  (e.g
p4080ds with MPIC v4.x) after issuing a core reset to properly clear pending
interrupts.

Signed-off-by: Matthew McClintock <msm@freescale.com>
---
v2: Updated commit message

 arch/powerpc/sysdev/mpic.c |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/arch/powerpc/sysdev/mpic.c b/arch/powerpc/sysdev/mpic.c
index 9678081..f5b83f0 100644
--- a/arch/powerpc/sysdev/mpic.c
+++ b/arch/powerpc/sysdev/mpic.c
@@ -1748,6 +1748,7 @@ void mpic_reset_core(int cpu)
 	struct mpic *mpic = mpic_primary;
 	u32 pir;
 	int cpuid = get_hard_smp_processor_id(cpu);
+	int i;
 
 	/* Set target bit for core reset */
 	pir = mpic_read(mpic->gregs, MPIC_INFO(GREG_PROCESSOR_INIT));
@@ -1759,6 +1760,12 @@ void mpic_reset_core(int cpu)
 	pir &= ~(1 << cpuid);
 	mpic_write(mpic->gregs, MPIC_INFO(GREG_PROCESSOR_INIT), pir);
 	mpic_read(mpic->gregs, MPIC_INFO(GREG_PROCESSOR_INIT));
+
+	/* Perform 15 EOI on each reset core to clear pending interrupts */
+	for (i = 0; i < 15; i++) {
+		_mpic_write(mpic->reg_type, &mpic->cpuregs[cpuid],
+				      MPIC_CPU_EOI, 0);
+	}
 }
 #endif /* CONFIG_SMP */
 
-- 
1.7.6.1

  reply	other threads:[~2011-10-26 18:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25 22:54 [PATCH 1/5] powerpc/85xx: issue 15 EOI after core reset Matthew McClintock
2011-10-25 22:54 ` [PATCH 2/5] powerpc/fsl_booke: Fix comment in head_fsl_booke.S Matthew McClintock
2011-11-03 18:00   ` Kumar Gala
2011-10-25 22:54 ` [PATCH 3/5] powerpc/85xx: Make kexec to interate over online cpus Matthew McClintock
2011-11-03 18:00   ` Kumar Gala
2011-10-25 22:54 ` [PATCH 4/5] powerpc/85xx: use physical cpu from device tree Matthew McClintock
2011-10-25 22:54 ` [PATCH 5/5] powerpc/setup_{32, 64}.c: remove unneeded boot_cpuid{, _phys} Matthew McClintock
2011-11-25  3:41   ` Benjamin Herrenschmidt
2011-11-29  4:24     ` [PATCH v2] " Matthew McClintock
2011-12-16  3:12       ` Benjamin Herrenschmidt
2011-12-16  3:29         ` McClintock Matthew-B29882
2011-12-16  3:35           ` Benjamin Herrenschmidt
2011-12-16  3:42             ` McClintock Matthew-B29882
2011-12-16 21:29             ` Scott Wood
2011-12-16 22:09               ` Benjamin Herrenschmidt
2011-12-20 18:44               ` McClintock Matthew-B29882
2011-12-20 19:27                 ` Scott Wood
2011-10-26  3:16 ` [PATCH 1/5] powerpc/85xx: issue 15 EOI after core reset Kumar Gala
2011-10-26 18:13   ` Matthew McClintock [this message]
2011-10-26 18:30     ` [PATCH 1/5] powerpc/85xx: issue 15 EOI after core reset for FSL CoreNet devices Segher Boessenkool
2011-10-26 18:33   ` [PATCH v3 " Matthew McClintock
2011-10-26 18:46     ` [PATCH v4 " Matthew McClintock
2011-11-03 18:00       ` Kumar Gala

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=1319652797-28017-1-git-send-email-msm@freescale.com \
    --to=msm@freescale.com \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.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).