From: <suravee.suthikulpanit@amd.com>
To: marc.zyngier@arm.com, mark.rutland@arm.com, jason@lakedaemon.net,
tglx@linutronix.de
Cc: devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
Catalin.Marinas@arm.com, liviu.dudau@arm.com,
linux-kernel@vger.kernel.org, Will.Deacon@arm.com,
Harish.Kasiviswanathan@amd.com,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [V9 PATCH 1/2] genirq: Add irq_chip_set_type_parent function
Date: Fri, 31 Oct 2014 03:26:29 -0500 [thread overview]
Message-ID: <1414743990-28421-2-git-send-email-suravee.suthikulpanit@amd.com> (raw)
In-Reply-To: <1414743990-28421-1-git-send-email-suravee.suthikulpanit@amd.com>
From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
Add a helper function to set irq type in parent irq domain.
Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
---
include/linux/irq.h | 1 +
kernel/irq/chip.c | 10 ++++++++++
2 files changed, 11 insertions(+)
diff --git a/include/linux/irq.h b/include/linux/irq.h
index 6159256..e3952fa 100644
--- a/include/linux/irq.h
+++ b/include/linux/irq.h
@@ -440,6 +440,7 @@ extern void irq_chip_ack_parent(struct irq_data *data);
extern void irq_chip_mask_parent(struct irq_data *data);
extern void irq_chip_unmask_parent(struct irq_data *data);
extern void irq_chip_eoi_parent(struct irq_data *data);
+extern int irq_chip_set_type_parent(struct irq_data *data, unsigned int type);
extern int irq_chip_set_affinity_parent(struct irq_data *data,
const struct cpumask *dest, bool force);
extern int irq_chip_retrigger_hierarchy(struct irq_data *data);
diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
index 0ecc270..b24eca3 100644
--- a/kernel/irq/chip.c
+++ b/kernel/irq/chip.c
@@ -847,6 +847,16 @@ void irq_chip_eoi_parent(struct irq_data *data)
data->chip->irq_eoi(data);
}
+int irq_chip_set_type_parent(struct irq_data *data, unsigned int type)
+{
+ data = data->parent_data;
+
+ if (data->chip && data->chip->irq_set_type)
+ return data->chip->irq_set_type(data, type);
+
+ return -ENOSYS;
+}
+
int irq_chip_set_affinity_parent(struct irq_data *data,
const struct cpumask *dest, bool force)
{
--
1.9.3
next prev parent reply other threads:[~2014-10-31 8:26 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
2014-10-31 8:26 ` suravee.suthikulpanit [this message]
2014-10-31 8:26 ` [V9 PATCH 2/2] irqchip: gicv2m: Add supports for ARM GICv2m MSI(-X) suravee.suthikulpanit
2014-10-31 9:40 ` Thomas Gleixner
2014-11-03 19:57 ` Suravee Suthikulanit
2014-11-03 9:50 ` Marc Zyngier
[not found] ` <54574FF7.706-5wv7dgnIgG8@public.gmane.org>
2014-11-03 14:10 ` Marc Zyngier
2014-11-03 19:57 ` Suravee Suthikulanit
2014-11-03 19:57 ` Suravee Suthikulanit
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=1414743990-28421-2-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=liviu.dudau@arm.com \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@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).