From: Michal Simek <michal.simek@xilinx.com>
To: Robert Hancock <robert.hancock@calian.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
"git@xilinx.com" <git@xilinx.com>,
"monstr@monstr.eu" <monstr@monstr.eu>
Cc: "maz@kernel.org" <maz@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"stefan.asserhall@xilinx.com" <stefan.asserhall@xilinx.com>
Subject: Re: [PATCH] irqchip: xilinx: Enable generic irq multi handler
Date: Fri, 4 Mar 2022 07:58:17 +0100 [thread overview]
Message-ID: <92ca12e2-9efd-702e-6940-7fcdc873da7b@xilinx.com> (raw)
In-Reply-To: <32881b5e94487845874b78dd36bbb5edec683e75.camel@calian.com>
On 3/3/22 18:01, Robert Hancock wrote:
> On Thu, 2022-03-03 at 17:11 +0100, Michal Simek wrote:
>> Register default arch handler via driver instead of directly pointing to
>> xilinx intc controller. This patch makes architecture code more generic.
>>
>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>> Reviewed-by: Stefan Asserhall <stefan.asserhall@xilinx.com>
>> ---
>>
>> arch/microblaze/Kconfig | 2 ++
>> arch/microblaze/include/asm/irq.h | 3 ---
>> arch/microblaze/kernel/irq.c | 16 +---------------
>> drivers/irqchip/irq-xilinx-intc.c | 22 +++++++++++++++++++++-
>> 4 files changed, 24 insertions(+), 19 deletions(-)
>>
>> diff --git a/arch/microblaze/Kconfig b/arch/microblaze/Kconfig
>> index 59798e43cdb0..da568e981604 100644
>> --- a/arch/microblaze/Kconfig
>> +++ b/arch/microblaze/Kconfig
>> @@ -45,6 +45,8 @@ config MICROBLAZE
>> select SET_FS
>> select ZONE_DMA
>> select TRACE_IRQFLAGS_SUPPORT
>> + select GENERIC_IRQ_MULTI_HANDLER
>> + select HANDLE_DOMAIN_IRQ
>>
>> # Endianness selection
>> choice
>> diff --git a/arch/microblaze/include/asm/irq.h
>> b/arch/microblaze/include/asm/irq.h
>> index 0a28e80bbab0..cb6ab55d1d01 100644
>> --- a/arch/microblaze/include/asm/irq.h
>> +++ b/arch/microblaze/include/asm/irq.h
>> @@ -11,7 +11,4 @@
>> struct pt_regs;
>> extern void do_IRQ(struct pt_regs *regs);
>>
>> -/* should be defined in each interrupt controller driver */
>> -extern unsigned int xintc_get_irq(void);
>> -
>> #endif /* _ASM_MICROBLAZE_IRQ_H */
>> diff --git a/arch/microblaze/kernel/irq.c b/arch/microblaze/kernel/irq.c
>> index 903dad822fad..1f8cb4c4f74f 100644
>> --- a/arch/microblaze/kernel/irq.c
>> +++ b/arch/microblaze/kernel/irq.c
>> @@ -20,27 +20,13 @@
>> #include <linux/irqchip.h>
>> #include <linux/of_irq.h>
>>
>> -static u32 concurrent_irq;
>> -
>> void __irq_entry do_IRQ(struct pt_regs *regs)
>> {
>> - unsigned int irq;
>> struct pt_regs *old_regs = set_irq_regs(regs);
>> trace_hardirqs_off();
>>
>> irq_enter();
>> - irq = xintc_get_irq();
>> -next_irq:
>> - BUG_ON(!irq);
>> - generic_handle_irq(irq);
>> -
>> - irq = xintc_get_irq();
>> - if (irq != -1U) {
>> - pr_debug("next irq: %d\n", irq);
>> - ++concurrent_irq;
>> - goto next_irq;
>> - }
>> -
>> + handle_arch_irq(regs);
>> irq_exit();
>> set_irq_regs(old_regs);
>> trace_hardirqs_on();
>> diff --git a/drivers/irqchip/irq-xilinx-intc.c b/drivers/irqchip/irq-xilinx-
>> intc.c
>> index 356a59755d63..c6710190c152 100644
>> --- a/drivers/irqchip/irq-xilinx-intc.c
>> +++ b/drivers/irqchip/irq-xilinx-intc.c
>> @@ -110,7 +110,7 @@ static struct irq_chip intc_dev = {
>> .irq_mask_ack = intc_mask_ack,
>> };
>>
>> -unsigned int xintc_get_irq(void)
>> +static unsigned int xintc_get_irq(void)
>> {
>> unsigned int irq = -1;
>> u32 hwirq;
>> @@ -164,6 +164,25 @@ static void xil_intc_irq_handler(struct irq_desc *desc)
>> chained_irq_exit(chip, desc);
>> }
>>
>> +static u32 concurrent_irq;
>
> Not sure what this variable is for? It seems to be incremented, but never read.
I used this when I was checking how irqs are working and how many concurrent_irq
I am getting. It was read via debugger not via any linux interface.
Thanks,
Michal
next prev parent reply other threads:[~2022-03-04 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 16:11 [PATCH] irqchip: xilinx: Enable generic irq multi handler Michal Simek
2022-03-03 17:01 ` Robert Hancock
2022-03-04 6:58 ` Michal Simek [this message]
2022-03-03 17:24 ` Marc Zyngier
2022-03-04 7:51 ` Michal Simek
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=92ca12e2-9efd-702e-6940-7fcdc873da7b@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=git@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=monstr@monstr.eu \
--cc=robert.hancock@calian.com \
--cc=stefan.asserhall@xilinx.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