From: Bjorn Helgaas <helgaas@kernel.org>
To: Herve Codina <herve.codina@bootlin.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>, Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@google.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Lizhi Hou <lizhi.hou@amd.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-pci@vger.kernel.org,
Allan Nielsen <allan.nielsen@microchip.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Steen Hegelund <steen.hegelund@microchip.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v8 2/5] PCI: of: Use device_{add,remove}_of_node() to attach of_node to existing device
Date: Fri, 28 Feb 2025 14:58:55 -0600 [thread overview]
Message-ID: <20250228205855.GA67436@bhelgaas> (raw)
In-Reply-To: <20250224141356.36325-3-herve.codina@bootlin.com>
On Mon, Feb 24, 2025 at 03:13:52PM +0100, Herve Codina wrote:
> The commit 407d1a51921e ("PCI: Create device tree node for bridge")
> creates of_node for PCI devices. The newly created of_node is attached
> to an existing device. This is done setting directly pdev->dev.of_node
> in the code.
>
> Even if pdev->dev.of_node cannot be previously set, this doesn't handle
> the fwnode field of the struct device. Indeed, this field needs to be
> set if it hasn't already been set.
>
> device_{add,remove}_of_node() have been introduced to handle this case.
I guess another way to say this is:
- If dev->of_node has already been set, it is an error and we want
to do nothing. The error is impossible in this case because
of_pci_make_dev_node() returns early if dev->of_node has been set.
- Otherwise, we want to set dev->of_node (just as we previously
did), and
- if dev->fwnode has not been set, we want to set that too.
So the whole point of this is to set dev->fwnode, which we didn't do
before. But has np->fwnode been set to anything? Maybe it's buried
somewhere inside of_changeset_create_node(), but I didn't see it.
I can't tell if this actually *does* anything. And if it does, all
the above is basically C code translated into English, so it doesn't
tell us *why* this is useful, which is what I try to put in the merge
commit log.
> Use them instead of the direct setting.
>
> Signed-off-by: Herve Codina <herve.codina@bootlin.com>
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> ---
> drivers/pci/of.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/of.c b/drivers/pci/of.c
> index 7a806f5c0d20..fb5e6da1ead0 100644
> --- a/drivers/pci/of.c
> +++ b/drivers/pci/of.c
> @@ -653,8 +653,8 @@ void of_pci_remove_node(struct pci_dev *pdev)
> np = pci_device_to_OF_node(pdev);
> if (!np || !of_node_check_flag(np, OF_DYNAMIC))
> return;
> - pdev->dev.of_node = NULL;
>
> + device_remove_of_node(&pdev->dev);
> of_changeset_revert(np->data);
> of_changeset_destroy(np->data);
> of_node_put(np);
> @@ -711,11 +711,18 @@ void of_pci_make_dev_node(struct pci_dev *pdev)
> goto out_free_node;
>
> np->data = cset;
> - pdev->dev.of_node = np;
> +
> + ret = device_add_of_node(&pdev->dev, np);
> + if (ret)
> + goto out_revert_cset;
> +
> kfree(name);
>
> return;
>
> +out_revert_cset:
> + np->data = NULL;
> + of_changeset_revert(cset);
> out_free_node:
> of_node_put(np);
> out_destroy_cset:
> --
> 2.48.1
>
next prev parent reply other threads:[~2025-02-28 20:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 14:13 [PATCH v8 0/5] Add support for the PCI host bridge device-tree node creation Herve Codina
2025-02-24 14:13 ` [PATCH v8 1/5] driver core: Introduce device_{add,remove}_of_node() Herve Codina
2025-02-24 14:13 ` [PATCH v8 2/5] PCI: of: Use device_{add,remove}_of_node() to attach of_node to existing device Herve Codina
2025-02-28 20:58 ` Bjorn Helgaas [this message]
2025-03-03 9:42 ` Herve Codina
2025-02-24 14:13 ` [PATCH v8 3/5] PCI: of_property: Add support for NULL pdev in of_pci_set_address() Herve Codina
2025-02-24 14:13 ` [PATCH v8 4/5] PCI: of_property: Constify parameter in of_pci_get_addr_flags() Herve Codina
2025-02-24 14:13 ` [PATCH v8 5/5] PCI: of: Create device-tree PCI host bridge node Herve Codina
2025-02-28 21:21 ` Bjorn Helgaas
2025-03-03 9:49 ` Herve Codina
2025-06-11 8:26 ` Claudiu Beznea
2025-06-11 14:56 ` Herve Codina
2025-06-13 13:36 ` Claudiu Beznea
2025-06-17 7:00 ` Herve Codina
2025-06-18 10:42 ` Claudiu Beznea
2025-02-27 17:36 ` [PATCH v8 0/5] Add support for the PCI host bridge device-tree node creation Bjorn Helgaas
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=20250228205855.GA67436@bhelgaas \
--to=helgaas@kernel.org \
--cc=allan.nielsen@microchip.com \
--cc=bhelgaas@google.com \
--cc=dakr@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=herve.codina@bootlin.com \
--cc=horatiu.vultur@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lizhi.hou@amd.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=steen.hegelund@microchip.com \
--cc=thomas.petazzoni@bootlin.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.