From: afzal mohammed <afzal.mohd.ma@gmail.com>
To: linux-c6x-dev@linux-c6x.org, linux-kernel@vger.kernel.org
Cc: Mark Salter <msalter@redhat.com>,
Aurelien Jacquiot <jacquiot.aurelien@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Enrico Weigelt <info@metux.net>,
Kate Stewart <kstewart@linuxfoundation.org>,
Allison Randal <allison@lohutok.net>
Subject: [PATCH 03/18] c6x: replace setup_irq() by request_irq()
Date: Wed, 12 Feb 2020 13:32:54 +0530 [thread overview]
Message-ID: <11cbe657937077b56bd28d277c9b9455a6985501.1581478324.git.afzal.mohd.ma@gmail.com> (raw)
In-Reply-To: <cover.1581478323.git.afzal.mohd.ma@gmail.com>
request_irq() is preferred over setup_irq(). Existing callers of
setup_irq() reached mostly via 'init_IRQ()' & 'time_init()', while
memory allocators are ready by 'mm_init()'.
Per tglx[1], setup_irq() existed in olden days when allocators were not
ready by the time early interrupts were initialized.
Hence replace setup_irq() by request_irq().
Seldom remove_irq() usage has been observed coupled with setup_irq(),
wherever that has been found, it too has been replaced by free_irq().
[1] https://lkml.kernel.org/r/alpine.DEB.2.20.1710191609480.1971@nanos
Signed-off-by: afzal mohammed <afzal.mohd.ma@gmail.com>
---
Since cc'ing cover letter to all maintainers/reviewers would be too
many, refer for cover letter,
https://lkml.kernel.org/r/cover.1581478323.git.afzal.mohd.ma@gmail.com
arch/c6x/platforms/timer64.c | 11 +++--------
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/arch/c6x/platforms/timer64.c b/arch/c6x/platforms/timer64.c
index d98d94303498..ceee34c51d4b 100644
--- a/arch/c6x/platforms/timer64.c
+++ b/arch/c6x/platforms/timer64.c
@@ -165,13 +165,6 @@ static irqreturn_t timer_interrupt(int irq, void *dev_id)
return IRQ_HANDLED;
}
-static struct irqaction timer_iact = {
- .name = "timer",
- .flags = IRQF_TIMER,
- .handler = timer_interrupt,
- .dev_id = &t64_clockevent_device,
-};
-
void __init timer64_init(void)
{
struct clock_event_device *cd = &t64_clockevent_device;
@@ -238,7 +231,9 @@ void __init timer64_init(void)
cd->cpumask = cpumask_of(smp_processor_id());
clockevents_register_device(cd);
- setup_irq(cd->irq, &timer_iact);
+ if (request_irq(cd->irq, timer_interrupt, IRQF_TIMER, "timer",
+ &t64_clockevent_device))
+ pr_err("request_irq() on %s failed\n", "timer");
out:
of_node_put(np);
--
2.24.1
next prev parent reply other threads:[~2020-02-12 8:02 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 8:01 [PATCH 00/18] genirq: Remove setup_irq() afzal mohammed
2020-02-12 8:02 ` [PATCH 01/18] alpha: replace setup_irq() by request_irq() afzal mohammed
2020-02-12 8:02 ` [PATCH 02/18] ARM: " afzal mohammed
2020-02-12 8:10 ` Viresh Kumar
2020-02-12 23:27 ` Alexander Sverdlin
2020-02-12 8:02 ` afzal mohammed [this message]
2020-02-13 17:37 ` [PATCH 03/18] c6x: " Mark Salter
2020-02-12 8:03 ` [PATCH 04/18] hexagon: " afzal mohammed
2020-02-12 8:03 ` [PATCH 05/18] ia64: " afzal mohammed
2020-02-12 8:03 ` [PATCH 06/18] m68k: Replace " afzal mohammed
2020-02-12 22:25 ` Finn Thain
2020-02-13 2:03 ` afzal mohammed
2020-02-13 7:11 ` Greg Ungerer
2020-02-14 13:07 ` afzal mohammed
2020-02-12 8:03 ` [PATCH 07/18] microblaze: " afzal mohammed
2020-02-12 8:04 ` [PATCH 08/18] MIPS: " afzal mohammed
2020-02-12 8:04 ` [PATCH 09/18] parisc: " afzal mohammed
2020-02-12 8:04 ` [PATCH 10/18] powerpc: " afzal mohammed
2020-02-13 10:59 ` Christophe Leroy
2020-02-12 8:04 ` [PATCH 11/18] s390: replace " afzal mohammed
2020-02-12 8:04 ` [PATCH 12/18] sh: " afzal mohammed
2020-02-12 8:05 ` [PATCH 13/18] unicore32: " afzal mohammed
2020-02-12 8:05 ` [PATCH 14/18] x86: Replace " afzal mohammed
2020-02-27 10:49 ` Thomas Gleixner
2020-02-27 11:36 ` afzal mohammed
2020-02-27 13:29 ` Thomas Gleixner
2020-02-27 14:26 ` afzal mohammed
2020-02-12 8:05 ` [PATCH 15/18] xtensa: replace " afzal mohammed
2020-02-12 9:10 ` Max Filippov
2020-02-12 8:05 ` [PATCH 16/18] clocksource: Replace " afzal mohammed
2020-02-20 11:13 ` Daniel Lezcano
2020-02-20 14:48 ` Linus Walleij
2020-02-12 8:05 ` [PATCH 17/18] irqchip: " afzal mohammed
[not found] ` <8e00874d072f32496c2d0da05423bda1cadd6975.1581478324.git.afzal.mohd.ma@gmail. com>
2020-02-13 16:02 ` Paul Cercueil
2020-02-12 8:06 ` [PATCH 18/18] genirq: Remove setup_irq() and remove_irq() afzal mohammed
2020-02-20 14:49 ` Linus Walleij
2020-02-27 10:31 ` [PATCH 00/18] genirq: Remove setup_irq() Thomas Gleixner
2020-02-27 11:07 ` afzal mohammed
2020-03-21 17:43 ` afzal mohammed
2020-03-27 16:08 ` [PATCH 0/6] Kill setup_irq() afzal mohammed
2020-03-27 16:09 ` [PATCH v5 1/6] alpha: Replace setup_irq() by request_irq() afzal mohammed
2020-03-27 16:09 ` [PATCH v5 2/6] c6x: replace " afzal mohammed
2020-03-27 16:09 ` [PATCH v5 3/6] hexagon: " afzal mohammed
2020-03-27 16:10 ` [PATCH v5 4/6] sh: " afzal mohammed
2020-03-27 16:10 ` [PATCH v5 5/6] unicore32: " afzal mohammed
2020-03-27 16:11 ` [PATCH v5 6/6] genirq: Remove setup_irq() and remove_irq() afzal mohammed
2020-04-11 14:10 ` afzal mohammed
2020-03-28 2:48 ` [PATCH 0/6] Kill setup_irq() Brian Cain
2020-03-28 7:32 ` afzal mohammed
2020-04-02 15:03 ` Brian Cain
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=11cbe657937077b56bd28d277c9b9455a6985501.1581478324.git.afzal.mohd.ma@gmail.com \
--to=afzal.mohd.ma@gmail.com \
--cc=allison@lohutok.net \
--cc=info@metux.net \
--cc=jacquiot.aurelien@gmail.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msalter@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;
as well as URLs for NNTP newsgroup(s).