From: Rob Herring <robh@kernel.org>
To: "A. Sverdlin" <alexander.sverdlin@siemens.com>
Cc: devicetree@vger.kernel.org,
Saravana Kannan <saravanak@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of/irq: Refuse to of_irq_parse_one() more than one IRQ if #interrupt-cells = <0>
Date: Tue, 11 Mar 2025 12:55:32 -0500 [thread overview]
Message-ID: <20250311175532.GA3869198-robh@kernel.org> (raw)
In-Reply-To: <20250307135231.4080272-1-alexander.sverdlin@siemens.com>
On Fri, Mar 07, 2025 at 02:52:18PM +0100, A. Sverdlin wrote:
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
>
> An #interrupt-cells = <0> property may arguably be a right answer for an
> interrupt controller having just one interrupt and no options to configure.
> There are anyway already existing examples in the tree, both in DTs and in
> the bindings.
The existing examples are broken and hacks to take advantage of Linux
implementation details (IRQCHIP_DECLARE()).
And #interrupt-cells==0 can't work with 'interrupts'.
>
> Now the problem is that of_irq_count() called on an interrupt generating
> device having one of the former controllers as parent would result in an
> endless loop. It's especially unpleasant in the startup where
> of_irq_count() <= ... <= of_platform_default_populate_init() will silently
> hang forever (unless a watchdog bites).
>
> Prevent others from spending the same time on debugging this by refusing to
> parse more than one IRQ for such controllers.
I'll happily take a dtschema patch to warn on 0 cells. Then you can find
the problem at build time. I generally don't think it's the kernel's job
to validate a DT, but if the code can handle something like this then
that's good.
>
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
> ---
> drivers/of/irq.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/of/irq.c b/drivers/of/irq.c
> index 6c843d54ebb11..b3a359c7641d3 100644
> --- a/drivers/of/irq.c
> +++ b/drivers/of/irq.c
> @@ -381,6 +381,13 @@ int of_irq_parse_one(struct device_node *device, int index, struct of_phandle_ar
> goto out;
> }
>
> + if (!intsize && index) {
Why are you checking index?
> + pr_debug("%pOF trying to map IRQ %d in %pOF having #interrupt-cells = <0>\n",
> + device, index, p);
> + res = -EINVAL;
> + goto out;
> + }
> +
> pr_debug(" parent=%pOF, intsize=%d\n", p, intsize);
>
> /* Copy intspec into irq structure */
> --
> 2.48.1
>
next prev parent reply other threads:[~2025-03-11 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 13:52 A. Sverdlin
2025-03-11 17:55 ` Rob Herring [this message]
2025-03-11 18:45 ` Sverdlin, Alexander
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=20250311175532.GA3869198-robh@kernel.org \
--to=robh@kernel.org \
--cc=alexander.sverdlin@siemens.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saravanak@google.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
all inboxes | Powered by JetHome®