From: Rob Herring <robh@kernel.org>
To: Samuel Holland <samuel.holland@sifive.com>
Cc: Saravana Kannan <saravanak@google.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: property: fw_devlink: Do not use interrupt-parent directly
Date: Tue, 19 Nov 2024 09:41:17 -0600 [thread overview]
Message-ID: <20241119154117.GA1537069-robh@kernel.org> (raw)
In-Reply-To: <20241114195652.3068725-1-samuel.holland@sifive.com>
On Thu, Nov 14, 2024 at 11:56:49AM -0800, Samuel Holland wrote:
> commit 7f00be96f125 ("of: property: Add device link support for
> interrupt-parent, dmas and -gpio(s)") started adding device links for
> the interrupt-parent property. Later, commit f265f06af194 ("of:
> property: Fix fw_devlink handling of interrupts/interrupts-extended")
> added full support for parsing the interrupts and interrupts-extended
> properties, which includes looking up the node of the parent domain.
> This made the handler for the interrupt-parent property redundant.
>
> In fact, creating device links based solely on interrupt-parent is
> problematic, because it can create spurious cycles. A node may have
> this property without itself being an interrupt controller or consumer.
> For example, this property is often present in the root node or a /soc
> bus node to set the default interrupt parent for child nodes. However,
> it is incorrect for the bus to depend on the interrupt controller, as
> some of the bus's childre may not be interrupt consumers at all or may
typo
> have a different interrupt parent.
>
> Resolving these spurious dependency cycles can cause an incorrect probe
> order for interrupt controller drivers. This was observed on a RISC-V
> system with both an APLIC and IMSIC under /soc, where interrupt-parent
> in /soc points to the APLIC, and the APLIC msi-parent points to the
> IMSIC. fw_devlink found three dependency cycles and attempted to probe
> the APLIC before the IMSIC. After applying this patch, there were no
> dependency cycles and the probe order was correct.
>
> Signed-off-by: Samuel Holland <samuel.holland@sifive.com>
I assume this should go to stable? It needs Fixes tags.
Otherwise, the change makes sense to me.
> ---
>
> drivers/of/property.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/of/property.c b/drivers/of/property.c
> index 11b922fde7af..7bd8390f2fba 100644
> --- a/drivers/of/property.c
> +++ b/drivers/of/property.c
> @@ -1213,7 +1213,6 @@ DEFINE_SIMPLE_PROP(iommus, "iommus", "#iommu-cells")
> DEFINE_SIMPLE_PROP(mboxes, "mboxes", "#mbox-cells")
> DEFINE_SIMPLE_PROP(io_channels, "io-channels", "#io-channel-cells")
> DEFINE_SIMPLE_PROP(io_backends, "io-backends", "#io-backend-cells")
> -DEFINE_SIMPLE_PROP(interrupt_parent, "interrupt-parent", NULL)
> DEFINE_SIMPLE_PROP(dmas, "dmas", "#dma-cells")
> DEFINE_SIMPLE_PROP(power_domains, "power-domains", "#power-domain-cells")
> DEFINE_SIMPLE_PROP(hwlocks, "hwlocks", "#hwlock-cells")
> @@ -1359,7 +1358,6 @@ static const struct supplier_bindings of_supplier_bindings[] = {
> { .parse_prop = parse_mboxes, },
> { .parse_prop = parse_io_channels, },
> { .parse_prop = parse_io_backends, },
> - { .parse_prop = parse_interrupt_parent, },
> { .parse_prop = parse_dmas, .optional = true, },
> { .parse_prop = parse_power_domains, },
> { .parse_prop = parse_hwlocks, },
> --
> 2.45.1
>
next prev parent reply other threads:[~2024-11-19 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 19:56 [PATCH] of: property: fw_devlink: Do not use interrupt-parent directly Samuel Holland
2024-11-14 20:24 ` Saravana Kannan
2024-11-15 9:15 ` Marc Zyngier
2024-11-19 15:41 ` Rob Herring [this message]
2024-11-19 16:46 ` Samuel Holland
2024-11-19 17:49 ` Rob Herring
2024-11-20 22:58 ` Samuel Holland
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=20241119154117.GA1537069-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.holland@sifive.com \
--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 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.