From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Connecting to "PCI command write" interrupt on 4xx platforms
Date: Fri, 31 Oct 2008 07:15:12 +1100 [thread overview]
Message-ID: <1225397712.8004.173.camel@pasglop> (raw)
In-Reply-To: <200810301158.46686.matthias.fuchs@esd-electronics.com>
On Thu, 2008-10-30 at 11:58 +0100, Matthias Fuchs wrote:
> I need to connect to the "PCI command write" interrupt on a 440EPx
> platform. This is UIC0/int#5.
>
> Where should I add this interrupt in the DT? To the PCI node? In this
> case it will collide with the
> PCI interrupts.
>
> My application is a 440EPx on a PCI addon card. So the PCI node is
> disabled in the DT.
>
> Is there a way to get an interrupt number for request_irq() without
> querying the DT?
What is this interrupt precisely ? What emits it ? If it's coming from
the actual PCI bridge, then you can stick an interrupts property in the
PCI host bridge node in the DT just fine.
Cheers,
Ben.
next prev parent reply other threads:[~2008-10-30 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 10:58 Connecting to "PCI command write" interrupt on 4xx platforms Matthias Fuchs
2008-10-30 20:15 ` Benjamin Herrenschmidt [this message]
2008-11-03 9:10 ` Matthias Fuchs
2008-11-03 10:57 ` Benjamin Herrenschmidt
2008-11-03 11:54 ` Stefan Roese
2008-11-03 13:40 ` Matthias Fuchs
2008-11-03 13:45 ` Matthias Fuchs
2008-11-03 20:19 ` Benjamin Herrenschmidt
2008-11-04 5:19 ` Stefan Roese
2008-11-04 6:16 ` Benjamin Herrenschmidt
2008-11-04 11:17 ` Matthias Fuchs
2008-11-04 21:29 ` Benjamin Herrenschmidt
2008-11-05 20:32 ` Matthias Fuchs
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=1225397712.8004.173.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matthias.fuchs@esd-electronics.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).