From: <suravee.suthikulpanit@amd.com>
To: <marc.zyngier@arm.com>, <mark.rutland@arm.com>, <jason@lakedaemon.net>
Cc: <pawel.moll@arm.com>, <Catalin.Marinas@arm.com>,
<Will.Deacon@arm.com>, <tglx@linutronix.de>,
<Harish.Kasiviswanathan@amd.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <devicetree@vger.kernel.org>,
Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
Subject: [PATCH 0/2 V4] irqchip: gic: Introduce ARM GICv2m MSI(-X) support
Date: Wed, 13 Aug 2014 10:00:39 -0500 [thread overview]
Message-ID: <1407942041-3291-1-git-send-email-suravee.suthikulpanit@amd.com> (raw)
From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
This patch set introduces support for MSI(-X) in GICv2m specification,
which is implemented in some variation of GIC400.
This depends on and has been tested with the V7 of"Add support for PCI in AArch64"
(https://lkml.org/lkml/2014/3/14/320).
Changes in V4:
* Rebase to git://git.infradead.org/users/jcooper/linux.git irqchip/core
* Remove patch 2 from previous version
* Merge patch 1 and 3 from previous version
* Reworks the GICv2m initialization based on Marc Zyngier review comments.
* Introduce "v2m" subnode in GIC binding
* Moves the "struct msi_chip" from "struct gic_chip_data" to "struct v2m_data".
Suravee Suthikulpanit (2):
irqchip: gic: Add supports for ARM GICv2m MSI(-X)
irqchip: gicv2m: Add support for multiple MSI for ARM64 GICv2m
Documentation/devicetree/bindings/arm/gic.txt | 32 +++
arch/arm64/include/asm/msi.h | 15 ++
arch/arm64/kernel/Makefile | 1 +
arch/arm64/kernel/msi.c | 57 +++++
drivers/irqchip/Kconfig | 7 +
drivers/irqchip/Makefile | 1 +
drivers/irqchip/irq-gic-v2m.c | 294 ++++++++++++++++++++++++++
drivers/irqchip/irq-gic.c | 75 ++++---
drivers/irqchip/irq-gic.h | 48 +++++
9 files changed, 500 insertions(+), 30 deletions(-)
create mode 100644 arch/arm64/include/asm/msi.h
create mode 100644 arch/arm64/kernel/msi.c
create mode 100644 drivers/irqchip/irq-gic-v2m.c
create mode 100644 drivers/irqchip/irq-gic.h
--
1.9.0
next reply other threads:[~2014-08-13 15:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 15:00 suravee.suthikulpanit [this message]
2014-08-13 15:00 ` [PATCH 1/2 V4] irqchip: gic: Add supports for ARM GICv2m MSI(-X) suravee.suthikulpanit
2014-08-14 2:56 ` Jingoo Han
2014-08-28 9:15 ` Suravee Suthikulpanit
2014-08-14 17:55 ` Mark Rutland
2014-08-28 9:03 ` Suravee Suthikulpanit
2014-09-08 23:05 ` Suravee Suthikulpanit
2014-09-09 11:03 ` Mark Rutland
2014-08-15 14:03 ` Marc Zyngier
2014-08-28 8:59 ` Suravee Suthikulpanit
2014-09-05 16:15 ` Marc Zyngier
2014-08-13 15:00 ` [PATCH 2/2 V4] irqchip: gicv2m: Add support for multiple MSI for ARM64 GICv2m suravee.suthikulpanit
2014-08-15 13:31 ` Marc Zyngier
2014-08-15 14:53 ` Suravee Suthikulanit
2014-08-15 15:08 ` 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=1407942041-3291-1-git-send-email-suravee.suthikulpanit@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=Catalin.Marinas@arm.com \
--cc=Harish.Kasiviswanathan@amd.com \
--cc=Will.Deacon@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=tglx@linutronix.de \
/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).