From: Rob Herring <robh@kernel.org>
To: Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Sascha Bischoff <sascha.bischoff@arm.com>,
Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH] of/irq: Add msi-parent check to of_msi_xlate()
Date: Thu, 18 Sep 2025 08:55:55 -0500 [thread overview]
Message-ID: <20250918135555.GA1540012-robh@kernel.org> (raw)
In-Reply-To: <20250916091858.257868-1-lpieralisi@kernel.org>
On Tue, Sep 16, 2025 at 11:18:58AM +0200, Lorenzo Pieralisi wrote:
> In some legacy platforms the MSI controller for a PCI host
> bridge is identified by an msi-parent property whose phandle
> points at an MSI controller node with no #msi-cells property,
> that implicitly means #msi-cells == 0.
>
> For such platforms, mapping a device ID and retrieving the
> MSI controller node becomes simply a matter of checking
> whether in the device hierarchy there is an msi-parent property
> pointing at an MSI controller node with such characteristics.
>
> Add a helper function to of_msi_xlate() to check the msi-parent
> property in addition to msi-map and retrieve the MSI controller
> node (with a 1:1 ID deviceID-IN<->deviceID-OUT mapping) to
> provide support for deviceID mapping and MSI controller node
> retrieval for such platforms.
Your line wrapping is a bit short.
I had a look at who is parsing "msi-parent" themselves as that's
typically a recipe for doing it incorrectly ('interrupt-map' anyone).
Can we make iproc_pcie_msi_enable() use this? It's quite ugly reaching
into the GICv3 node...
And perhaps irq-gic-its-msi-parent.c could use this?
And looks like pcie-layerscape-gen4 is leaking a node reference...
>
> Signed-off-by: Lorenzo Pieralisi <lpieralisi@kernel.org>
> Cc: Sascha Bischoff <sascha.bischoff@arm.com>
> Cc: Rob Herring <robh@kernel.org>
> Cc: Marc Zyngier <maz@kernel.org>
> ---
> drivers/of/irq.c | 38 +++++++++++++++++++++++++++++++++++---
> 1 file changed, 35 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/of/irq.c b/drivers/of/irq.c
> index e7c12abd10ab..d0e2dfd0ee28 100644
> --- a/drivers/of/irq.c
> +++ b/drivers/of/irq.c
> @@ -670,6 +670,35 @@ void __init of_irq_init(const struct of_device_id *matches)
> }
> }
>
> +static int of_check_msi_parent(struct device_node *dev_node, struct device_node **msi_node)
> +{
> + struct of_phandle_args msi_spec;
> + int ret;
> +
> + /*
> + * An msi-parent phandle with a missing or == 0 #msi-cells
> + * property identifies a 1:1 ID translation mapping.
> + *
> + * Set the msi controller node if the firmware matches this
> + * condition.
> + */
> + ret = of_parse_phandle_with_optional_args(dev_node, "msi-parent", "#msi-cells",
> + 0, &msi_spec);
> + if (!ret) {
> + if ((*msi_node && *msi_node != msi_spec.np) || msi_spec.args_count != 0)
> + ret = -EINVAL;
> +
> + if (!ret) {
> + /* Return with a node reference held */
> + *msi_node = msi_spec.np;
> + return 0;
> + }
> + of_node_put(msi_spec.np);
> + }
> +
> + return ret;
> +}
> +
> /**
> * of_msi_xlate - map a MSI ID and find relevant MSI controller node
> * @dev: device for which the mapping is to be done.
> @@ -677,7 +706,7 @@ void __init of_irq_init(const struct of_device_id *matches)
> * @id_in: Device ID.
> *
> * Walk up the device hierarchy looking for devices with a "msi-map"
> - * property. If found, apply the mapping to @id_in.
> + * or "msi-parent" property. If found, apply the mapping to @id_in.
> * If @msi_np points to a non-NULL device node pointer, only entries targeting
> * that node will be matched; if it points to a NULL value, it will receive the
> * device node of the first matching target phandle, with a reference held.
> @@ -691,12 +720,15 @@ u32 of_msi_xlate(struct device *dev, struct device_node **msi_np, u32 id_in)
>
> /*
> * Walk up the device parent links looking for one with a
> - * "msi-map" property.
> + * "msi-map" or an "msi-parent" property.
> */
> - for (parent_dev = dev; parent_dev; parent_dev = parent_dev->parent)
> + for (parent_dev = dev; parent_dev; parent_dev = parent_dev->parent) {
> if (!of_map_id(parent_dev->of_node, id_in, "msi-map",
> "msi-map-mask", msi_np, &id_out))
> break;
> + if (!of_check_msi_parent(parent_dev->of_node, msi_np))
> + break;
> + }
> return id_out;
> }
>
> --
> 2.48.0
>
next prev parent reply other threads:[~2025-09-18 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 9:18 [PATCH] of/irq: Add msi-parent check to of_msi_xlate() Lorenzo Pieralisi
2025-09-18 13:55 ` Rob Herring [this message]
2025-09-18 15:21 ` Lorenzo Pieralisi
2025-09-18 19:44 ` Rob Herring
2025-09-19 6:59 ` Lorenzo Pieralisi
2025-09-19 7:18 ` Lorenzo Pieralisi
2025-09-22 10:49 ` Lorenzo Pieralisi
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=20250918135555.GA1540012-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=maz@kernel.org \
--cc=sascha.bischoff@arm.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;
as well as URLs for NNTP newsgroup(s).