linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: linuxppc-embedded@ozlabs.org
Subject: [PATCH] ppc32: ppc4xx_pic - add acknowledge when enabling level-sensitive IRQ
Date: Sun, 3 Apr 2005 21:17:28 -0700	[thread overview]
Message-ID: <20050404041728.GB9575@gate.ebshome.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 701 bytes --]

Andrew,

this patch adds interrupt acknowledge to the PPC4xx PIC enable_irq 
implementation for level-sensitive IRQ sources. This helps in cases 
when enable/disable_irq is used in interrupt handlers for hardware, 
which requires IRQ acknowledge to be issued from non-interrupt context 
(e.g. when actual ACK in device needs an I2C transaction). For such 
strange hardware, interrupt handler disables IRQ and defers actual ACK 
to some other context. When this happens, IRQ is enabled again. For 
level-sensitive sources we get spurious triggering right after IRQ 
is enabled. This patch fixes this.
Suggested by Tolunay Orkun <listmember@orkun.us>.

Signed-off-by: Eugene Surovegin <ebs@ebshome.net>

[-- Attachment #2: ppc4xx_pic_ack_on_enable.diff --]
[-- Type: text/plain, Size: 613 bytes --]

===== arch/ppc/syslib/ppc4xx_pic.c 1.15 vs edited =====
--- 1.15/arch/ppc/syslib/ppc4xx_pic.c	2005-03-04 22:41:17 -08:00
+++ edited/arch/ppc/syslib/ppc4xx_pic.c	2005-04-03 12:00:55 -07:00
@@ -41,7 +41,10 @@
 #define UIC_HANDLERS(n)							\
 static void ppc4xx_uic##n##_enable(unsigned int irq)			\
 {									\
-	ppc_cached_irq_mask[n] |= IRQ_MASK_UIC##n(irq);			\
+	u32 mask = IRQ_MASK_UIC##n(irq);				\
+	if (irq_desc[irq].status & IRQ_LEVEL)				\
+		mtdcr(DCRN_UIC_SR(UIC##n), mask);			\
+	ppc_cached_irq_mask[n] |= mask;					\
 	mtdcr(DCRN_UIC_ER(UIC##n), ppc_cached_irq_mask[n]);		\
 }									\
 									\

                 reply	other threads:[~2005-04-04  4:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20050404041728.GB9575@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=linuxppc-embedded@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).