From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 2/8] Add uli1575 pci-bridge sector to MPC8641HPCN dts file.
Date: Sun, 03 Jun 2007 19:12:19 +1000 [thread overview]
Message-ID: <1180861939.31677.15.camel@localhost.localdomain> (raw)
In-Reply-To: <34eddd7ce58e7983017077454d592332@kernel.crashing.org>
On Sun, 2007-06-03 at 10:57 +0200, Segher Boessenkool wrote:
>
> I have no idea what this whole 8259-ack thing is
> so I cannot comment further.
When you get an IRQ on your main PIC (MPIC for example) which happens to
be the cascade to the 8259, you have two ways of retreiving the actual
8259 interrupt source.
One is the "poll" method which goes read IOs on the 8259. The other one
is to generate a PCI interrupt acknowledge cycle on the bus that leads
to the 8259. If your bridges properly forward it all the way to the ISA
bridge, it should "mimminc" the x86 interrupt acknowledge and return the
interrupt number (an INTACK cycle on PCI is pretty much a read from a
broadcast address).
The later is more efficient but the mecanism to generate such cycles is
very much platform specific and was never abstracted in the PCI stack
(possibly because x86 never needs to explicitely do it, it's all
implicit in the x86 bus protocol :-)
So on CHRP, that property in a PHB indicates, when possible, and address
you can ioremap and readb from to generate an INTACK cycle on that bus
and retreive the pending IRQ of any legacy PIC on that segment.
In theory, in fact, MPIC itself, at least the PCI variant of it, is also
supposed to be able to respond to these rather than reading an MMIO
register (remember, MPIC was supposed to be useable on x86 too, though I
don't know if that was never actually implemented). But then, I've never
seen that used or implemented in practice.
Cheers,
Ben.
next prev parent reply other threads:[~2007-06-03 9:12 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 17:48 [PATCH 2/8] Add uli1575 pci-bridge sector to MPC8641HPCN dts file Jon Loeliger
2007-06-01 18:58 ` Segher Boessenkool
2007-06-01 21:45 ` Wade Farnsworth
2007-06-02 8:22 ` Segher Boessenkool
2007-06-02 8:53 ` Gabriel Paubert
2007-06-02 9:01 ` Segher Boessenkool
2007-06-02 19:53 ` Gabriel Paubert
2007-06-02 20:23 ` Segher Boessenkool
2007-06-03 0:01 ` Benjamin Herrenschmidt
2007-06-03 7:41 ` Segher Boessenkool
2007-06-03 8:33 ` Gabriel Paubert
2007-06-03 8:57 ` Segher Boessenkool
2007-06-03 9:12 ` Benjamin Herrenschmidt [this message]
2007-06-03 10:02 ` Segher Boessenkool
2007-06-03 10:10 ` Gabriel Paubert
2007-06-03 11:42 ` Segher Boessenkool
2007-06-03 12:43 ` Gabriel Paubert
2007-06-03 14:42 ` Segher Boessenkool
2007-06-03 18:20 ` Gabriel Paubert
2007-06-03 18:56 ` Segher Boessenkool
2007-06-03 9:07 ` Benjamin Herrenschmidt
2007-06-03 9:59 ` Segher Boessenkool
2007-06-03 14:50 ` Jon Loeliger
2007-06-03 17:27 ` Segher Boessenkool
2007-06-04 20:27 ` Andy Fleming
2007-06-04 22:31 ` Randy Vinson
2007-06-05 19:16 ` Andy Fleming
2007-06-05 20:28 ` Randy Vinson
2007-06-06 7:09 ` Benjamin Herrenschmidt
2007-06-07 16:21 ` Andy Fleming
2007-06-07 16:53 ` Segher Boessenkool
2007-06-07 22:12 ` Benjamin Herrenschmidt
2007-06-08 8:29 ` Segher Boessenkool
2007-06-08 8:32 ` Benjamin Herrenschmidt
2007-06-05 6:05 ` Zang Roy-r61911
2007-06-02 23:52 ` Benjamin Herrenschmidt
2007-06-02 23:51 ` Benjamin Herrenschmidt
2007-06-03 8:59 ` Geert Uytterhoeven
2007-06-04 18:50 ` Jon Loeliger
2007-06-04 19:27 ` Segher Boessenkool
2007-06-01 23:28 ` Benjamin Herrenschmidt
2007-06-01 23:36 ` Jon Loeliger
2007-06-02 0:22 ` Benjamin Herrenschmidt
2007-06-02 8:28 ` Segher Boessenkool
2007-06-02 16:04 ` Jon Loeliger
2007-06-02 20:00 ` Segher Boessenkool
2007-06-02 23:16 ` Benjamin Herrenschmidt
2007-06-03 7:37 ` Segher Boessenkool
2007-06-04 0:16 ` Olof Johansson
2007-06-04 8:18 ` Segher Boessenkool
2007-06-02 8:25 ` Segher Boessenkool
2007-06-02 23:50 ` Benjamin Herrenschmidt
2007-06-03 0:13 ` Gabriel Paubert
2007-06-03 7:42 ` Segher Boessenkool
2007-06-03 7:53 ` Gabriel Paubert
2007-06-04 18:49 ` Jon Loeliger
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=1180861939.31677.15.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.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).