40p: use OR gate to wire up raven PCI interrupts
commitf40b83a4e31ae1b56ae5494cf7dc8b015975ac4a
authorMark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Sat, 8 Sep 2018 09:08:19 +0000 (8 10:08 +0100)
committerDavid Gibson <david@gibson.dropbear.id.au>
Tue, 25 Sep 2018 01:12:25 +0000 (25 11:12 +1000)
tree0407900e274fa054fee3c1444445d87ab81fa503
parent55a2290254192d828b9464acb175fb0dc24c7035
40p: use OR gate to wire up raven PCI interrupts

According to the PReP specification section 6.1.6 "System Interrupt
Assignments", all PCI interrupts are routed via IRQ 15.

Instead of mapping each PCI IRQ separately, we introduce an OR gate within the
raven PCI host bridge and then wire the single output of the OR gate to the
interrupt controller.

Note that whilst the (now deprecated) PReP machine still exists we still need
to preserve the old IRQ routing. This is done by adding a new "is-legacy-prep"
property to the raven PCI host bridge which is set to true for the PReP
machine.

Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Reviewed-by: Hervé Poussineau <hpoussin@reactos.org>
Tested-by: Hervé Poussineau <hpoussin@reactos.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
hw/pci-host/prep.c
hw/ppc/prep.c