From: Thomas Gleixner <tglx@linutronix.de>
To: enachman@marvell.com, andrew@lunn.ch,
gregory.clement@bootlin.com, sebastian.hesselbarth@gmail.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: enachman@marvell.com
Subject: Re: [PATCH] irqchip/mvebu-gicp: clear pending irqs on init
Date: Tue, 29 Jul 2025 14:10:54 +0200 [thread overview]
Message-ID: <87ldo7jiy9.ffs@tglx> (raw)
In-Reply-To: <20250729084826.3222785-1-enachman@marvell.com>
On Tue, Jul 29 2025 at 11:48, enachman@marvell.com wrote:
> From: Elad Nachman <enachman@marvell.com>
>
> For kexec case, left interrupt might generate spurious
> interrupts in various A7/A8/CN913x interrupt system
> from the I/O SB to the NB.
That's a lot of incomprehensible acronyms. Is any of that relevant for
understanding the problem?
What's a 'left' interrupt?
Just say something like this:
When a kexec'ed kernel boots up, there might be stale unhandled
interrupts pending in the interrupt controller. These are delivered as
spurious interrupts once the boot CPU enables interrupts.
That's clear and sufficient, no?
> Clear all pending interrupts
> when the driver is initialized to prevent these spurious
> interrupts.
> Signed-off-by: Elad Nachman <enachman@marvell.com>
> ---
> drivers/irqchip/irq-mvebu-gicp.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/irqchip/irq-mvebu-gicp.c b/drivers/irqchip/irq-mvebu-gicp.c
> index d3232d6d8dce..0fa21a45d4e1 100644
> --- a/drivers/irqchip/irq-mvebu-gicp.c
> +++ b/drivers/irqchip/irq-mvebu-gicp.c
> @@ -31,6 +31,7 @@ struct mvebu_gicp_spi_range {
>
> struct mvebu_gicp {
> struct mvebu_gicp_spi_range *spi_ranges;
> + void __iomem *base;
Why?
> unsigned int spi_ranges_cnt;
> unsigned int spi_cnt;
> unsigned long *spi_bitmap;
> @@ -236,6 +237,14 @@ static int mvebu_gicp_probe(struct platform_device *pdev)
> return -ENODEV;
> }
>
> + gicp->base = devm_platform_ioremap_resource(pdev, 0);
There is no reason to create a permanent mapping, which is not used
anywhere else. Just map, write, unmap.
> + if (IS_ERR(gicp->base))
> + dev_err(&pdev->dev, "gicp - Cannot ioremap !\n");
So this emits a unspecific error message and then happily
continues. That does not make sense.
As the ioremap failure is not fatal, tell the user what this is about,
i.e. "ioremap() failed. Unable to clear pending interrupts."
or something to that effect.
> + else {
Lacks parenthesis on the if clause for symmetry.
> + for (i = 0; i < 64; i++)
> + writel(i, gicp->base + GICP_CLRSPI_NSR_OFFSET);
> + }
> +
> return msi_create_parent_irq_domain(&info, &gicp_msi_parent_ops) ? 0 : -ENOMEM;
> }
Thanks,
tglx
next prev parent reply other threads:[~2025-07-29 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 8:48 [PATCH] irqchip/mvebu-gicp: clear pending irqs on init enachman
2025-07-29 12:10 ` Thomas Gleixner [this message]
2025-07-29 19:07 ` Markus Elfring
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=87ldo7jiy9.ffs@tglx \
--to=tglx@linutronix.de \
--cc=andrew@lunn.ch \
--cc=enachman@marvell.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.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