[PATCH 2/8] Add uli1575 pci-bridge sector to MPC8641HPCN dts file.
paubert at iram.es
Sun Jun 3 18:33:39 EST 2007
On Sun, Jun 03, 2007 at 09:41:33AM +0200, Segher Boessenkool wrote:
> >>Oh what the hell, I'm too curious... "pnpPNP,0" it is.
> >>>I believe that "8259" should appear somewhere because of the
> >>>"8259-interrupt-acknowledge" property (defined in CHRP bindings)
> >>>which you can have on the parent bridge to speed up interrupt
> >>>vector acquisition.
> >>You're not CHRP so you have nothing to do with the CHRP
> >Still, you are close to CHRP
> Not at all, the rest of the device interrupt subsystem
> is very different, too.
Given how well you agree, I understand how other people
might get a bit confused ;-)
This said, I'm looking at device trees right now, and I can understand
that interrupt-parent of the 8259 is &mpic in mpc8641_hpcn.dts, but
I don't understand at all why it is &pci1 on the mpc85??cds.dts.
But the definition of the ISA bridge in these files is very strange to
start with: I've never seen an ISA bridge with only an interrupt controller
on it, no interrupts are connected to it and its reg property is
almost certainly wrong. Maybe it is an example of things that should
not be done.
> >and the CHRP bindings do apply :-)
At least the 8259-interrupt-acknowledge property of the bus
on which the ISA bridge is found should keep its name. It's what
the kernel uses.
It just seems odd to call the chip iic (for ISA interrupt controller
I suppose) on one side and 8259 on the other. Naming consistency
Technically the 8259-interrupt-acknowledge is not a very fortunate
name choise since it is an a 8259 like chip (or an ISA bridge
for the matter) that has to claim the interrupt acknowledge
cycles, but it is what happens in practice.
> >the 8259
> >should thus be chrp,iic :-) It's even documented that way in
> >booting-without-of.txt iirc.
More information about the Linuxppc-dev