From: Yinghai Lu <yinghai@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>, Tony Luck <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>
Subject: [PATCH 3/8] irq: Use irq_alloc_desc_at instead of irq_reserve_irq
Date: Thu, 1 May 2014 16:18:17 -0700 [thread overview]
Message-ID: <1398986302-30455-4-git-send-email-yinghai@kernel.org> (raw)
In-Reply-To: <1398986302-30455-1-git-send-email-yinghai@kernel.org>
irq_reserve_irq actually only set bit allocated_irq, and it is not really
"reserve" and cause confusion.
For !CONFIG_SPARSE_IRQ path, irq_alloc_desc_at() will only set bit
in allocated_irq.
We can use that instead, kill one irq_reserve_irq() calling.
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
---
kernel/irq/chip.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
index 6397df2..aff7481 100644
--- a/kernel/irq/chip.c
+++ b/kernel/irq/chip.c
@@ -28,8 +28,13 @@
int irq_set_chip(unsigned int irq, struct irq_chip *chip)
{
unsigned long flags;
- struct irq_desc *desc = irq_get_desc_lock(irq, &flags, 0);
+ struct irq_desc *desc;
+
+#ifndef CONFIG_SPARSE_IRQ
+ irq_alloc_desc_at(irq, 0);
+#endif
+ desc = irq_get_desc_lock(irq, &flags, 0);
if (!desc)
return -EINVAL;
@@ -38,12 +43,7 @@ int irq_set_chip(unsigned int irq, struct irq_chip *chip)
desc->irq_data.chip = chip;
irq_put_desc_unlock(desc, flags);
- /*
- * For !CONFIG_SPARSE_IRQ make the irq show up in
- * allocated_irqs. For the CONFIG_SPARSE_IRQ case, it is
- * already marked, and this call is harmless.
- */
- irq_reserve_irq(irq);
+
return 0;
}
EXPORT_SYMBOL(irq_set_chip);
--
1.8.4.5
next prev parent reply other threads:[~2014-05-01 23:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 23:18 [PATCH 0/8] irq: core changes for x86 ioapic hotplug Yinghai Lu
2014-05-01 23:18 ` [PATCH 1/8] x86, irq: Remove not needed irq_reserve_irqs calling Yinghai Lu
2014-05-01 23:18 ` [PATCH 2/8] sh, irq: Remove irq_reserve_irq calling Yinghai Lu
2014-05-02 2:38 ` Simon Horman
2014-05-02 15:19 ` Sergei Shtylyov
2014-05-01 23:18 ` Yinghai Lu [this message]
2014-05-01 23:18 ` [PATCH 4/8] s390: Mark bits in allocated_irqs in general code Yinghai Lu
2014-05-01 23:18 ` [PATCH 5/8] irq: Kill irq_reserve_irq/irq_reserve_irqs Yinghai Lu
2014-05-01 23:18 ` [PATCH 6/8] irq: Add new reserved_irqs clear/mark functions Yinghai Lu
2014-05-02 10:50 ` Thomas Gleixner
2014-05-01 23:18 ` [PATCH 7/8] irq: Add irq_alloc_reserved_desc() Yinghai Lu
2014-05-01 23:18 ` [PATCH 8/8] irq: Do not free unallocated irq descriptors Yinghai Lu
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=1398986302-30455-4-git-send-email-yinghai@kernel.org \
--to=yinghai@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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