From: Alvise Rigo <a.rigo@virtualopensystems.com>
To: qemu-devel@nongnu.org, rob.herring@linaro.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
tech@virtualopensystems.com,
Alvise Rigo <a.rigo@virtualopensystems.com>
Subject: [Qemu-devel] [RFC PATCH 5/8] generic_pci: create own map irq function
Date: Fri, 11 Jul 2014 09:21:07 +0200 [thread overview]
Message-ID: <1405063270-18902-6-git-send-email-a.rigo@virtualopensystems.com> (raw)
In-Reply-To: <1405063270-18902-1-git-send-email-a.rigo@virtualopensystems.com>
Allocate MAX_PCI_DEVICES IRQs for the pci_generic device. For now we
assume that at every PCI slot corresponds an interrupt line: this also
seems what the kernel code does when parsing the interrupt mapping from
the device tree. At the moment there isn't a structure that keeps track
of the IRQ mapping; it will be added later by a patch of this series.
Signed-off-by: Alvise Rigo <a.rigo@virtualopensystems.com>
---
hw/arm/virt.c | 10 ++++++----
hw/pci-host/generic-pci.c | 15 ++++++++++++---
include/hw/pci-host/pci_generic.h | 4 +++-
3 files changed, 21 insertions(+), 8 deletions(-)
diff --git a/hw/arm/virt.c b/hw/arm/virt.c
index c93152f..a433902 100644
--- a/hw/arm/virt.c
+++ b/hw/arm/virt.c
@@ -41,6 +41,7 @@
#include "exec/address-spaces.h"
#include "qemu/bitops.h"
#include "qemu/error-report.h"
+#include "hw/pci-host/pci_generic.h"
/* Number of external interrupt lines to configure the GIC with */
@@ -359,6 +360,7 @@ static void create_pci_host(const VirtBoardInfo *vbi, qemu_irq *pic)
SysBusDevice *busdev;
uint32_t gic_phandle;
char *nodename;
+ int i;
hwaddr cfg_base = vbi->memmap[VIRT_PCI_CFG].base;
hwaddr cfg_size = vbi->memmap[VIRT_PCI_CFG].size;
hwaddr io_base = vbi->memmap[VIRT_PCI_IO].base;
@@ -397,10 +399,10 @@ static void create_pci_host(const VirtBoardInfo *vbi, qemu_irq *pic)
sysbus_mmio_map(busdev, 0, cfg_base); /* PCI config */
sysbus_mmio_map(busdev, 1, io_base); /* PCI I/O */
sysbus_mmio_map(busdev, 2, mem_base); /* PCI memory window */
- sysbus_connect_irq(busdev, 0, pic[4]);
- sysbus_connect_irq(busdev, 1, pic[5]);
- sysbus_connect_irq(busdev, 2, pic[6]);
- sysbus_connect_irq(busdev, 3, pic[7]);
+
+ for ( i = 0; i < MAX_PCI_DEVICES; i++) {
+ sysbus_connect_irq(busdev, i, pic[vbi->irqmap[VIRT_PCI_CFG] + i]);
+ }
pci_bus = (PCIBus *)qdev_get_child_bus(dev, "pci");
pci_create_simple(pci_bus, -1, "pci-ohci");
diff --git a/hw/pci-host/generic-pci.c b/hw/pci-host/generic-pci.c
index 8733c67..75aae45 100644
--- a/hw/pci-host/generic-pci.c
+++ b/hw/pci-host/generic-pci.c
@@ -65,18 +65,27 @@ static void pci_generic_host_init(Object *obj)
qdev_set_parent_bus(DEVICE(&s->pci_dev), BUS(&s->pci_bus));
}
+static int generic_pci_map_irq_fn(PCIDevice *pci_dev, int pin)
+{
+ if (!pin) {
+ return PCI_SLOT(pci_dev->devfn);
+ }
+
+ hw_error("generic_pci: only one pin per device supported.");
+}
+
static void pci_generic_host_realize(DeviceState *dev, Error **errp)
{
PCIVPBState *s = PCI_GEN(dev);
SysBusDevice *sbd = SYS_BUS_DEVICE(dev);
int i;
- for (i = 0; i < 4; i++) {
+ for (i = 0; i < MAX_PCI_DEVICES; i++) {
sysbus_init_irq(sbd, &s->irq[i]);
}
- pci_bus_irqs(&s->pci_bus, pci_generic_set_irq, pci_swizzle_map_irq_fn,
- s->irq, 4);
+ pci_bus_irqs(&s->pci_bus, pci_generic_set_irq, generic_pci_map_irq_fn,
+ s->irq, MAX_PCI_DEVICES);
/* Our memory regions are:
* 0 : PCI config window
diff --git a/include/hw/pci-host/pci_generic.h b/include/hw/pci-host/pci_generic.h
index 46e4cb8..2367d80 100644
--- a/include/hw/pci-host/pci_generic.h
+++ b/include/hw/pci-host/pci_generic.h
@@ -5,10 +5,12 @@
#include "hw/pci/pci_bus.h"
#include "hw/pci/pci_host.h"
+#define MAX_PCI_DEVICES 10
+
typedef struct {
PCIHostState parent_obj;
- qemu_irq irq[4];
+ qemu_irq irq[MAX_PCI_DEVICES];
MemoryRegion mem_config;
/* Containers representing the PCI address spaces */
MemoryRegion pci_io_space;
--
1.9.1
next prev parent reply other threads:[~2014-07-11 7:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 7:21 [Qemu-devel] [RFC PATCH 0/8] Add Generic PCI host device update Alvise Rigo
2014-07-11 7:21 ` [Qemu-devel] [RFC PATCH 1/8] mach-virt: move GIC inside mach-virt structure Alvise Rigo
2014-07-11 7:21 ` [Qemu-devel] [RFC PATCH 2/8] mach-virt: improve PCI memory topology definition Alvise Rigo
2014-07-11 7:21 ` [Qemu-devel] [RFC PATCH 3/8] QEMUMachine: finalize_dt function Alvise Rigo
2014-07-11 7:21 ` [Qemu-devel] [RFC PATCH 4/8] generic_pci: create header file Alvise Rigo
2014-07-11 7:21 ` Alvise Rigo [this message]
2014-07-11 7:21 ` [Qemu-devel] [RFC PATCH 6/8] generic_pci: generate dt node after devices init Alvise Rigo
2014-11-05 12:26 ` Claudio Fontana
2014-11-06 10:27 ` alvise rigo
2014-07-11 7:21 ` [Qemu-devel] [RFC PATCH 7/8] generic_pci: realize device with machine data Alvise Rigo
2014-07-11 7:21 ` [Qemu-devel] [RFC PATCH 8/8] generic_pci: add interrupt map structures Alvise Rigo
2014-07-11 9:09 ` [Qemu-devel] [RFC PATCH 0/8] Add Generic PCI host device update Peter Maydell
2014-07-11 9:28 ` Alvise Rigo
2014-07-13 14:28 ` Rob Herring
2014-09-09 16:35 ` Claudio Fontana
2014-09-10 7:31 ` alvise rigo
2014-11-05 10:23 ` Claudio Fontana
2014-11-05 11:09 ` alvise rigo
2014-11-07 15:40 ` Claudio Fontana
2014-11-10 10:00 ` alvise rigo
2014-11-11 3:24 ` Ming Lei
2014-11-11 4:22 ` Ming Lei
2014-11-11 10:26 ` Claudio Fontana
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=1405063270-18902-6-git-send-email-a.rigo@virtualopensystems.com \
--to=a.rigo@virtualopensystems.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rob.herring@linaro.org \
--cc=tech@virtualopensystems.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).