public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@saftware.de>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] 3/3 handle level triggered irqs on dbox2 (2.4.22-pre6)
Date: 19 Jul 2003 15:36:28 +0200	[thread overview]
Message-ID: <1058621788.585.29.camel@localhost> (raw)
In-Reply-To: <1058620870.585.15.camel@localhost>

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

This one is for components of the dbox2 which cannot be set up to do
edge triggered irqs because no documentation is available. #ifdef
CONFIG_DBOX2 is put around it because other boards don't seem to need
it. Is there a better way to handle level based interrupts?

[-- Attachment #2: linux-2.4.22-pre6-dbox2-irq.diff --]
[-- Type: text/x-patch, Size: 524 bytes --]

diff -Naur linux-2.4.22-pre6/arch/ppc/kernel/irq.c linux-2.4.22-pre6-dbox2/arch/ppc/kernel/irq.c
--- linux-2.4.22-pre6/arch/ppc/kernel/irq.c	2003-06-13 16:51:31.000000000 +0200
+++ linux-2.4.22-pre6-dbox2/arch/ppc/kernel/irq.c	2003-07-15 09:16:34.000000000 +0200
@@ -507,6 +507,14 @@
 		else if (irq_desc[irq].handler->enable)
 			irq_desc[irq].handler->enable(irq);
 	}
+	
+#ifdef CONFIG_DBOX2
+	if (action) {
+	    if (action->flags & SA_ONESHOT)
+		disable_irq_nosync(irq);
+	}
+#endif
+
 	spin_unlock(&desc->lock);
 }
 

      parent reply	other threads:[~2003-07-19 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-19 13:21 [PATCH] 1/3 Support mpc823 board dbox2 (2.4.22-pre6) Andreas Oberritter
2003-07-19 13:30 ` [PATCH] 2/3 Support mpc8xx watchdog of " Andreas Oberritter
2003-07-19 13:36 ` Andreas Oberritter [this message]

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=1058621788.585.29.camel@localhost \
    --to=obi@saftware.de \
    --cc=linux-kernel@vger.kernel.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