qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, patches@apm.com, agraf@suse.de,
	christoffer.dall@linaro.org,
	Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
Subject: [Qemu-devel] [v2 0/2] Generic PCIe host bridge INTx determination for INTx routing
Date: Thu, 30 Apr 2015 17:22:48 +0530	[thread overview]
Message-ID: <1430394771-19617-1-git-send-email-pranavkumar@linaro.org> (raw)

This patch adds a routine for GPEX to implement PCI bus specific function pointer 
"route_intx_to_irq" which is used during INTx routing.

ChangeLog:

V2:
- Drop a patch about adding an API to get irq number from qemu_irq
- Store a GPEX INTx information from board specific code (virt.c)
V1:
- Initial patchset
- https://lists.gnu.org/archive/html/qemu-devel/2015-04/msg01986.html

Pranavkumar Sawargaonkar (2):
  pci: GPEX: Add a function to determine interrupt number for INTx
    routing
  arm: hw: virt: Store information about GPEX legacy interrupt numbers

 hw/arm/virt.c              |  4 ++++
 hw/pci-host/gpex.c         | 12 ++++++++++++
 include/hw/pci-host/gpex.h |  1 +
 3 files changed, 17 insertions(+)

-- 
1.9.1

             reply	other threads:[~2015-04-30 11:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 11:52 Pranavkumar Sawargaonkar [this message]
2015-04-30 11:52 ` [Qemu-devel] [v2 1/2] pci: GPEX: Add a function to determine interrupt number for INTx routing Pranavkumar Sawargaonkar
2015-04-30 11:52 ` [Qemu-devel] [v2 2/2] arm: hw: virt: Store information about GPEX legacy interrupt numbers Pranavkumar Sawargaonkar
2015-09-18 16:22 ` [Qemu-devel] [v2 0/2] Generic PCIe host bridge INTx determination for INTx routing Peter Maydell

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=1430394771-19617-1-git-send-email-pranavkumar@linaro.org \
    --to=pranavkumar@linaro.org \
    --cc=agraf@suse.de \
    --cc=christoffer.dall@linaro.org \
    --cc=patches@apm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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).