From: Jan-Bernd Themann <ossthema@de.ibm.com>
To: Sebastien Dugue <sebastien.dugue@bull.net>
Cc: Thomas Q Klein <TKLEIN@de.ibm.com>,
tinytim@us.ibm.com, Linux-rt <linux-rt-users@vger.kernel.org>,
Jan-Bernd Themann <THEMANN@de.ibm.com>,
netdev@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
jean-pierre.dion@bull.net, linux-ppc <linuxppc-dev@ozlabs.org>,
Benjamin Herrenschmidt <bherren@au1.ibm.com>,
Hoang-Nam Nguyen <HNGUYEN@de.ibm.com>,
Christoph Raisch <RAISCH@de.ibm.com>,
gilles.carry@ext.bull.net
Subject: Re: [PATCH HACK] powerpc: quick hack to get a functional eHEA with hardirq preemption, eHCA is close
Date: Tue, 23 Sep 2008 17:43:23 +0200 [thread overview]
Message-ID: <200809231743.23828.ossthema@de.ibm.com> (raw)
In-Reply-To: <20080918143146.77db81d5@bull.net>
Hi,
I think these are the "functional" changes that need to be included in
the ibmebus driver. We'll add a RT flag in the final version to enable
these changes only for RT-Linux for now.
Ben, can you / your team look into the implementation
of the set_irq_type functionality needed for XICS?
Regards,
Jan-Bernd & Christoph
diff -Nurp b/arch/powerpc/kernel/ibmebus.c a/arch/powerpc/kernel/ibmebus.c
--- b/arch/powerpc/kernel/ibmebus.c 2008-09-22 00:29:55.000000000 +0200
+++ a/arch/powerpc/kernel/ibmebus.c 2008-09-23 12:04:53.000000000 +0200
@@ -216,12 +216,16 @@ int ibmebus_request_irq(u32 ist, irq_han
unsigned long irq_flags, const char *devname,
void *dev_id)
{
+ int ret;
unsigned int irq = irq_create_mapping(NULL, ist);
if (irq == NO_IRQ)
return -EINVAL;
- return request_irq(irq, handler, irq_flags, devname, dev_id);
+ ret = request_irq(irq, handler, irq_flags, devname, dev_id);
+ set_irq_type(irq, IRQ_TYPE_EDGE_RISING);
+
+ return ret;
}
EXPORT_SYMBOL(ibmebus_request_irq);
next prev parent reply other threads:[~2008-09-23 15:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 8:04 [PATCH HACK] powerpc: quick hack to get a functional eHEA with hardirq preemption Sebastien Dugue
2008-09-15 12:17 ` Jan-Bernd Themann
2008-09-15 12:35 ` Thomas Klein
2008-09-15 13:13 ` Sebastien Dugue
2008-09-16 11:59 ` Anton Vorontsov
2008-09-16 12:22 ` Sebastien Dugue
2008-09-18 7:53 ` Christoph Raisch
2008-09-18 9:27 ` Sebastien Dugue
2008-09-18 10:42 ` [PATCH HACK] powerpc: quick hack to get a functional eHEA with hardirq preemption, eHCA is close Christoph Raisch
2008-09-18 12:31 ` Sebastien Dugue
2008-09-23 15:43 ` Jan-Bernd Themann [this message]
2008-09-24 9:58 ` [PATCH HACK] powerpc: quick hack to get a functional eHEA with hardirq preemption Milton Miller
2008-09-24 10:17 ` Benjamin Herrenschmidt
2008-09-24 11:02 ` Milton Miller
2008-09-24 21:14 ` Benjamin Herrenschmidt
2008-09-25 7:31 ` Sebastien Dugue
2008-09-24 12:35 ` Sebastien Dugue
2008-09-24 21:15 ` Benjamin Herrenschmidt
2008-09-25 7:18 ` Sebastien Dugue
2008-09-25 7:22 ` Benjamin Herrenschmidt
2008-09-25 7:42 ` Sebastien Dugue
2008-09-25 8:36 ` Benjamin Herrenschmidt
2008-09-25 8:39 ` Sebastien Dugue
2008-09-24 12:30 ` Sebastien Dugue
2008-09-24 16:42 ` Milton Miller
2008-09-24 21:16 ` Benjamin Herrenschmidt
2008-09-25 3:56 ` Milton Miller
2008-09-25 8:45 ` Sebastien Dugue
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=200809231743.23828.ossthema@de.ibm.com \
--to=ossthema@de.ibm.com \
--cc=HNGUYEN@de.ibm.com \
--cc=RAISCH@de.ibm.com \
--cc=THEMANN@de.ibm.com \
--cc=TKLEIN@de.ibm.com \
--cc=bherren@au1.ibm.com \
--cc=gilles.carry@ext.bull.net \
--cc=jean-pierre.dion@bull.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=sebastien.dugue@bull.net \
--cc=tinytim@us.ibm.com \
/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).