From: Michael Ellerman <michael@ellerman.id.au>
To: Laurent Pinchart <laurentp@cse-semaphore.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Interrupt handling documentation
Date: Wed, 12 Mar 2008 11:51:28 +1100 [thread overview]
Message-ID: <1205283088.7544.8.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <200803111158.48540.laurentp@cse-semaphore.com>
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
On Tue, 2008-03-11 at 11:58 +0100, Laurent Pinchart wrote:
> Hi everybody,
>
> is there any documentation describing interrupt handling for the powerpc
> architecture ? I'm writing a driver for a cascaded interrupt controller and
> the only source of information I found was the code.
I don't think there's much documentation.
You might want to look at arch/powerpc/platforms/cell/axon_msi.c, it's a
reasonably simple example of how to setup an irq_host and so on - well I
think so :D
> I'm particularly interested in information about irq hosts (allocation and
> initialisation, especially the map and unmap callbacks) and irq chaining.
> Different drivers seem to implement cascaded irqs differently (for instance
> arch/powerpc/sysdev/uic.c uses setup_irq to register the cascaded irq
> handler, while arch/powerpc/platforms/82xx/pq2ads-pci-pic.c uses
> set_irq_chained_handler) so I'm a bit lost here.
uic.c uses set_irq_chained_handler() now, so that probably answers that
question. I don't think it makes all that much difference if you set it
up by hand, but set_irq_chained_handler() is the neat way to do it.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-12 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 10:58 Interrupt handling documentation Laurent Pinchart
2008-03-12 0:51 ` Michael Ellerman [this message]
2008-03-13 13:56 ` Laurent Pinchart
2008-03-17 16:13 ` Laurent Pinchart
2008-03-17 20:44 ` Benjamin Herrenschmidt
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=1205283088.7544.8.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--cc=laurentp@cse-semaphore.com \
--cc=linuxppc-dev@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).