From: Chuansheng Liu <chuansheng.liu@intel.com>
To: tglx@linutronix.de, joro@8bytes.org
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] x86, io_apic: Adding the flag IRQCHIP_SKIP_SET_WAKE
Date: Tue, 12 Mar 2013 01:55:11 +0800 [thread overview]
Message-ID: <1363024511.31506.62.camel@cliu38-desktop-build> (raw)
In-Reply-To: <1363024396.31506.60.camel@cliu38-desktop-build>
Currently for an ioapic chip irq, if we call irq_set_irq_wake()
we will get the ENXIO returning error, but some drivers need the
wake-up interrupts pending mechanism.
Here adding the flag IRQCHIP_SKIP_SET_WAKE instead of emtpy callback.
Signed-off-by: liu chuansheng <chuansheng.liu@intel.com>
---
arch/x86/kernel/apic/io_apic.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
index 9ed796c..7d0baf7 100644
--- a/arch/x86/kernel/apic/io_apic.c
+++ b/arch/x86/kernel/apic/io_apic.c
@@ -2520,6 +2520,7 @@ static struct irq_chip ioapic_chip __read_mostly = {
.irq_eoi = ack_apic_level,
.irq_set_affinity = native_ioapic_set_affinity,
.irq_retrigger = ioapic_retrigger_irq,
+ .flags = IRQCHIP_SKIP_SET_WAKE,
};
static inline void init_IO_APIC_traps(void)
--
1.7.0.4
next prev parent reply other threads:[~2013-03-11 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 17:53 [PATCH 0/3] genirq: Do not consider the irqs with disabling and IRQF_NO_SUSPEND Chuansheng Liu
2013-03-11 17:55 ` Chuansheng Liu [this message]
2013-03-11 17:57 ` [PATCH 2/3] " Chuansheng Liu
2013-03-11 21:24 ` Thomas Gleixner
2013-03-12 0:21 ` Liu, Chuansheng
2013-03-12 9:58 ` [PATCH 2/3] genirq: Do not consider the irqs with IRQF_NO_SUSPEND in check_wakeup_irqs() Chuansheng Liu
2013-03-14 0:26 ` Liu, Chuansheng
2013-03-11 17:59 ` [PATCH 3/3] genirq: Give warning in case calling irq_set_irq_wake with _NO_SUSPEND flag Chuansheng Liu
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=1363024511.31506.62.camel@cliu38-desktop-build \
--to=chuansheng.liu@intel.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®