From: Marc Zyngier <marc.zyngier@arm.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jiang Liu <jiang.liu@linux.intel.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Will Deacon <Will.Deacon@arm.com>,
Yijing Wang <wangyijing@huawei.com>,
Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
Subject: [PATCH 0/6] Introducing per-device MSI domain
Date: Mon, 8 Dec 2014 20:12:17 +0000 [thread overview]
Message-ID: <1418069543-21969-1-git-send-email-marc.zyngier@arm.com> (raw)
MSI-like interrupts are starting to creep out of the PCI world, and
can now be seen into a number of "platform"-type busses. The MSI
domain patches recognise that fact, and start providing a way to
implement this.
Another problem we have to solve is to identify which MSI domain a
device is "connected" to. Currently, PCI gets away with a mixture of
arch-specific callbacks, and a msi_controller structure that can
optionally carry a pointer to an MSI domain. As we add new bus types
and start dealing with topologies that do not map to what PCI does,
this doesn't scale anymore.
This patch series tries to address some of it by providing a basic
link between 'struct device' and an MSI domain. It also adds (yet
another) way for PCI to propagate the domain pointer through the PCI
device hierarchy, provides a method for OF to kickstart the
propagation process, and finally allows the PCI/MSI layer to use that
information. Hopefully this can serve as a model to implement support
for different but types.
Additionally, the last two patches use all the above to remove any
trace of the msi_controller structure from the two GIC interrupt
controllers we use on arm64, so that they solely rely on the above
infrastructure.
This has been tested on arm64 with GICv2m (AMD Seattle) and GICv3 ITS
(FVP model).
Patches are on top of 3.18-rc7 + tip/irq/irq-domain-arm, and available at:
git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/msi_domain
As always, comments most welcome.
M.
Marc Zyngier (6):
device core: Introduce per-device MSI domain pointer
PCI/MSI: add hooks to populate the msi_domain field
PCI/MSI: of: add support for OF-provided msi_domain
PCI/MSI: Let pci_msi_get_domain use struct device's msi_domain
irqchip: GICv2m: Get rid of struct msi_controller
irqchip: gicv3-its: Get rid of struct msi_controller
drivers/irqchip/irq-gic-v2m.c | 26 +++++++++-----------------
drivers/irqchip/irq-gic-v3-its.c | 29 ++++++++++++-----------------
drivers/pci/msi.c | 3 ++-
drivers/pci/of.c | 15 +++++++++++++++
drivers/pci/probe.c | 25 +++++++++++++++++++++++++
include/linux/device.h | 20 ++++++++++++++++++++
include/linux/pci.h | 3 +++
7 files changed, 86 insertions(+), 35 deletions(-)
--
2.1.3
next reply other threads:[~2014-12-08 20:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 20:12 Marc Zyngier [this message]
2014-12-08 20:12 ` [PATCH 1/6] device core: Introduce per-device MSI domain pointer Marc Zyngier
2014-12-08 20:12 ` [PATCH 2/6] PCI/MSI: add hooks to populate the msi_domain field Marc Zyngier
2014-12-09 2:03 ` Yijing Wang
2014-12-09 10:02 ` Marc Zyngier
2014-12-09 11:57 ` Yijing Wang
2014-12-09 12:12 ` Marc Zyngier
2014-12-09 12:24 ` Yijing Wang
2014-12-09 12:47 ` Jiang Liu
2014-12-09 14:03 ` Marc Zyngier
2014-12-09 14:11 ` Jiang Liu
2014-12-09 14:27 ` Marc Zyngier
2014-12-09 14:35 ` Jiang Liu
2014-12-09 14:59 ` Marc Zyngier
2014-12-09 15:42 ` Jiang Liu
2014-12-09 12:57 ` Jiang Liu
2015-01-27 0:40 ` Bjorn Helgaas
2015-01-27 0:43 ` Bjorn Helgaas
2014-12-08 20:12 ` [PATCH 3/6] PCI/MSI: of: add support for OF-provided msi_domain Marc Zyngier
2015-01-27 0:41 ` Bjorn Helgaas
2014-12-08 20:12 ` [PATCH 4/6] PCI/MSI: Let pci_msi_get_domain use struct device's msi_domain Marc Zyngier
2014-12-08 20:12 ` [PATCH 5/6] irqchip: GICv2m: Get rid of struct msi_controller Marc Zyngier
2014-12-08 20:12 ` [PATCH 6/6] irqchip: gicv3-its: " Marc Zyngier
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=1418069543-21969-1-git-send-email-marc.zyngier@arm.com \
--to=marc.zyngier@arm.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=Will.Deacon@arm.com \
--cc=bhelgaas@google.com \
--cc=jiang.liu@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=wangyijing@huawei.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).