From: suravee.suthikulpanit@amd•com (Suravee Suthikulanit)
To: linux-arm-kernel@lists•infradead.org
Subject: [V9 PATCH 2/2] irqchip: gicv2m: Add supports for ARM GICv2m MSI(-X)
Date: Mon, 3 Nov 2014 13:57:36 -0600 [thread overview]
Message-ID: <5457DE30.3010200@amd.com> (raw)
In-Reply-To: <54574FF7.706@arm.com>
On 11/3/2014 3:50 AM, Marc Zyngier wrote:
>> diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
>> >index a99c211..4069eb3 100644
>> >--- a/drivers/irqchip/irq-gic.c
>> >+++ b/drivers/irqchip/irq-gic.c
>> >@@ -46,6 +46,7 @@
>> > #include <asm/smp_plat.h>
>> >
>> > #include "irq-gic-common.h"
>> >+#include "irq-gic-v2m.h"
>> > #include "irqchip.h"
>> >
>> > union gic_base {
>> >@@ -68,6 +69,9 @@ struct gic_chip_data {
>> > #ifdef CONFIG_GIC_NON_BANKED
>> > void __iomem *(*get_base)(union gic_base *);
>> > #endif
>> >+#ifdef CONFIG_ARM_GIC_V2M
>> >+ struct list_head v2m_list;
>> >+#endif
> Can't that be something private to the v2m widget driver? I don't think
> it brings anything to the main GIC driver.
>
Looking at this again, now that we use the hierarchy irqdomain, GIC no
longer needs to be handling with children v2m. I'll remove this altogether.
Suravee
prev parent reply other threads:[~2014-11-03 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 8:26 [V9 PATCH 0/2] irqchip: gic: Introduce ARM GICv2m MSI(-X) support suravee.suthikulpanit at amd.com
2014-10-31 8:26 ` [V9 PATCH 1/2] genirq: Add irq_chip_set_type_parent function suravee.suthikulpanit at amd.com
2014-10-31 8:26 ` [V9 PATCH 2/2] irqchip: gicv2m: Add supports for ARM GICv2m MSI(-X) suravee.suthikulpanit at amd.com
2014-10-31 9:40 ` Thomas Gleixner
2014-11-03 19:57 ` Suravee Suthikulanit
2014-11-03 9:50 ` Marc Zyngier
2014-11-03 14:10 ` Marc Zyngier
2014-11-03 19:57 ` Suravee Suthikulanit
2014-11-03 19:57 ` Suravee Suthikulanit [this message]
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=5457DE30.3010200@amd.com \
--to=suravee.suthikulpanit@amd$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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