From: Marc Zyngier <maz@kernel.org>
To: Stafford Horne <shorne@gmail.com>
Cc: Jonas Bonn <jonas@southpole.se>,
Thomas Gleixner <tglx@linutronix.de>,
Openrisc <openrisc@lists.librecores.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] irqchip: or1k-pic: Undefine mask_ack for level triggered hardware
Date: Tue, 28 Jun 2022 09:25:25 +0100 [thread overview]
Message-ID: <877d512o0a.wl-maz@kernel.org> (raw)
In-Reply-To: <20220628012854.681220-1-shorne@gmail.com>
On Tue, 28 Jun 2022 02:28:54 +0100,
Stafford Horne <shorne@gmail.com> wrote:
>
> The mask_ack operation clears the interrupt by writing to the PICSR
> register. This we don't want for level triggered interrupt because
> it does not actually clear the interrupt on the source hardware.
>
> This was causing issues in qemu with multi core setups where
> interrupts would continue to fire even though they had been cleared in
> PICSR.
>
> Just remove the mask_ack operation.
>
> Signed-off-by: Stafford Horne <shorne@gmail.com>
> ---
> Note,
>
> I currently have this queued with openrisc fixes for 5.19-rcX. If this is ok
> with the IRQ maintainers I would like to have this merged via the OpenRISC
> queue.
>
> drivers/irqchip/irq-or1k-pic.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/irqchip/irq-or1k-pic.c b/drivers/irqchip/irq-or1k-pic.c
> index 49b47e787644..f289ccd95291 100644
> --- a/drivers/irqchip/irq-or1k-pic.c
> +++ b/drivers/irqchip/irq-or1k-pic.c
> @@ -66,7 +66,6 @@ static struct or1k_pic_dev or1k_pic_level = {
> .name = "or1k-PIC-level",
> .irq_unmask = or1k_pic_unmask,
> .irq_mask = or1k_pic_mask,
> - .irq_mask_ack = or1k_pic_mask_ack,
> },
> .handle = handle_level_irq,
> .flags = IRQ_LEVEL | IRQ_NOPROBE,
Acked-by: Marc Zyngier <maz@kernel.org>
Feel free to take this via your tree.
M.
--
Without deviation from the norm, progress is not possible.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Stafford Horne <shorne@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Openrisc <openrisc@lists.librecores.org>,
Jonas Bonn <jonas@southpole.se>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] irqchip: or1k-pic: Undefine mask_ack for level triggered hardware
Date: Tue, 28 Jun 2022 09:25:25 +0100 [thread overview]
Message-ID: <877d512o0a.wl-maz@kernel.org> (raw)
In-Reply-To: <20220628012854.681220-1-shorne@gmail.com>
On Tue, 28 Jun 2022 02:28:54 +0100,
Stafford Horne <shorne@gmail.com> wrote:
>
> The mask_ack operation clears the interrupt by writing to the PICSR
> register. This we don't want for level triggered interrupt because
> it does not actually clear the interrupt on the source hardware.
>
> This was causing issues in qemu with multi core setups where
> interrupts would continue to fire even though they had been cleared in
> PICSR.
>
> Just remove the mask_ack operation.
>
> Signed-off-by: Stafford Horne <shorne@gmail.com>
> ---
> Note,
>
> I currently have this queued with openrisc fixes for 5.19-rcX. If this is ok
> with the IRQ maintainers I would like to have this merged via the OpenRISC
> queue.
>
> drivers/irqchip/irq-or1k-pic.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/irqchip/irq-or1k-pic.c b/drivers/irqchip/irq-or1k-pic.c
> index 49b47e787644..f289ccd95291 100644
> --- a/drivers/irqchip/irq-or1k-pic.c
> +++ b/drivers/irqchip/irq-or1k-pic.c
> @@ -66,7 +66,6 @@ static struct or1k_pic_dev or1k_pic_level = {
> .name = "or1k-PIC-level",
> .irq_unmask = or1k_pic_unmask,
> .irq_mask = or1k_pic_mask,
> - .irq_mask_ack = or1k_pic_mask_ack,
> },
> .handle = handle_level_irq,
> .flags = IRQ_LEVEL | IRQ_NOPROBE,
Acked-by: Marc Zyngier <maz@kernel.org>
Feel free to take this via your tree.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-06-28 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 1:28 [PATCH] irqchip: or1k-pic: Undefine mask_ack for level triggered hardware Stafford Horne
2022-06-28 1:28 ` Stafford Horne
2022-06-28 8:25 ` Marc Zyngier [this message]
2022-06-28 8:25 ` Marc Zyngier
2022-06-28 8:30 ` Stafford Horne
2022-06-28 8:30 ` Stafford Horne
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=877d512o0a.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=jonas@southpole.se \
--cc=linux-kernel@vger.kernel.org \
--cc=openrisc@lists.librecores.org \
--cc=shorne@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.