From: Marc Zyngier <marc.zyngier@arm.com>
To: Benoit Cousson <bcousson@baylibre.com>,
Tony Lindgren <tony@atomide.com>, Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Jason Cooper <jason@lakedaemon.net>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: [PATCH v6 1/7] genirq: Add irqchip_set_wake_parent
Date: Wed, 11 Mar 2015 15:43:43 +0000 [thread overview]
Message-ID: <1426088629-15377-2-git-send-email-marc.zyngier@arm.com> (raw)
In-Reply-To: <1426088629-15377-1-git-send-email-marc.zyngier@arm.com>
This proves to be useful with stacked domains, when the current
domain doesn't implement wake-up, but expect the parent to do so.
Acked-by: Tony Lindgren <tony@atomide.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
---
include/linux/irq.h | 1 +
kernel/irq/chip.c | 16 ++++++++++++++++
2 files changed, 17 insertions(+)
diff --git a/include/linux/irq.h b/include/linux/irq.h
index d09ec7a..3057c48 100644
--- a/include/linux/irq.h
+++ b/include/linux/irq.h
@@ -460,6 +460,7 @@ extern void irq_chip_eoi_parent(struct irq_data *data);
extern int irq_chip_set_affinity_parent(struct irq_data *data,
const struct cpumask *dest,
bool force);
+extern int irq_chip_set_wake_parent(struct irq_data *data, unsigned int on);
#endif
/* Handling of unhandled and spurious interrupts: */
diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
index 6f1c7a5..eb9a4ea 100644
--- a/kernel/irq/chip.c
+++ b/kernel/irq/chip.c
@@ -948,6 +948,22 @@ int irq_chip_retrigger_hierarchy(struct irq_data *data)
return -ENOSYS;
}
+
+/**
+ * irq_chip_set_wake_parent - Set/reset wake-up on the parent interrupt
+ * @data: Pointer to interrupt specific data
+ * @on: Whether to set or reset the wake-up capability of this irq
+ *
+ * Conditional, as the underlying parent chip might not implement it.
+ */
+int irq_chip_set_wake_parent(struct irq_data *data, unsigned int on)
+{
+ data = data->parent_data;
+ if (data->chip->irq_set_wake)
+ return data->chip->irq_set_wake(data, on);
+
+ return -ENOSYS;
+}
#endif
/**
--
2.1.4
next prev parent reply other threads:[~2015-03-11 15:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 15:43 [PATCH v6 0/7] irqchip: Move OMAP{4,5}/DRA7 to use stacked domains Marc Zyngier
2015-03-11 15:43 ` Marc Zyngier [this message]
2015-03-11 15:43 ` [PATCH v6 2/7] irqchip: crossbar: convert dra7 crossbar to " Marc Zyngier
2015-03-11 15:43 ` [PATCH v6 3/7] DT: update ti,irq-crossbar binding Marc Zyngier
2015-03-11 15:43 ` [PATCH v6 4/7] irqchip: GIC: get rid of routable domain Marc Zyngier
2015-03-11 15:43 ` [PATCH v6 5/7] DT: arm,gic: kill arm,routable-irqs Marc Zyngier
2015-03-11 15:43 ` [PATCH v6 6/7] DT: omap4/5: add binding for the wake-up generator Marc Zyngier
2015-03-11 15:43 ` [PATCH v6 7/7] ARM: omap: convert wakeupgen to stacked domains Marc Zyngier
2015-03-13 15:40 ` [PATCH v6 0/7] irqchip: Move OMAP{4,5}/DRA7 to use " Tony Lindgren
2015-03-13 17:25 ` Jason Cooper
2015-03-13 17:38 ` Tony Lindgren
2015-03-13 17:49 ` Marc Zyngier
2015-03-15 1:22 ` Jason Cooper
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=1426088629-15377-2-git-send-email-marc.zyngier@arm.com \
--to=marc.zyngier@arm.com \
--cc=bcousson@baylibre.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=tglx@linutronix.de \
--cc=tony@atomide.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