From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
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 v7 1/5] driver core: Introduce device_{add,remove}_of_node()
Date: Wed, 19 Feb 2025 15:59:01 +0000 [thread overview]
Message-ID: <20250219155901.000009e4@huawei.com> (raw)
In-Reply-To: <20250204073501.278248-2-herve.codina@bootlin.com>
On Tue, 4 Feb 2025 08:34:56 +0100
Herve Codina <herve.codina@bootlin.com> wrote:
> An of_node can be set to a device using device_set_node().
> This function cannot prevent any of_node and/or fwnode overwrites.
>
> When adding an of_node on an already present device, the following
> operations need to be done:
> - Attach the of_node if no of_node were already attached
> - Attach the of_node as a fwnode if no fwnode were already attached
>
> This is the purpose of device_add_of_node().
> device_remove_of_node() reverts the operations done by
> device_add_of_node().
>
> Signed-off-by: Herve Codina <herve.codina@bootlin.com>
A few passing comments. Not suggestions to actually change anything
at this stage though. Maybe a potential follow up if you think it's
a good idea.
> ---
> drivers/base/core.c | 61 ++++++++++++++++++++++++++++++++++++++++++
> include/linux/device.h | 2 ++
> 2 files changed, 63 insertions(+)
>
> diff --git a/drivers/base/core.c b/drivers/base/core.c
> index 5a1f05198114..d1b044af64de 100644
> --- a/drivers/base/core.c
> +++ b/drivers/base/core.c
> @@ -5170,6 +5170,67 @@ void set_secondary_fwnode(struct device *dev, struct fwnode_handle *fwnode)
> }
> EXPORT_SYMBOL_GPL(set_secondary_fwnode);
>
> +/**
> + * device_remove_of_node - Remove an of_node from a device
> + * @dev: device whose device-tree node is being removed
> + */
> +void device_remove_of_node(struct device *dev)
> +{
> + dev = get_device(dev);
> + if (!dev)
> + return;
Maybe use
struct device *d __free(put_device) = get_device(dev);
if (!d->of_node);
return;
Not a reason to respin though!
> +
> + if (!dev->of_node)
> + goto end;
> +
> + if (dev->fwnode == of_fwnode_handle(dev->of_node))
> + dev->fwnode = NULL;
> +
> + of_node_put(dev->of_node);
> + dev->of_node = NULL;
> +
> +end:
> + put_device(dev);
> +}
> +EXPORT_SYMBOL_GPL(device_remove_of_node);
> +
> +/**
> + * device_add_of_node - Add an of_node to an existing device
> + * @dev: device whose device-tree node is being added
> + * @of_node: of_node to add
> + *
> + * Return: 0 on success or error code on failure.
> + */
> +int device_add_of_node(struct device *dev, struct device_node *of_node)
> +{
> + int ret;
> +
> + if (!of_node)
> + return -EINVAL;
> +
> + dev = get_device(dev);
Likewise could use __free() magic here as well for slight simpliciations.
> + if (!dev)
> + return -EINVAL;
> +
> + if (dev->of_node) {
> + dev_err(dev, "Cannot replace node %pOF with %pOF\n",
> + dev->of_node, of_node);
> + ret = -EBUSY;
> + goto end;
> + }
> +
> + dev->of_node = of_node_get(of_node);
> +
> + if (!dev->fwnode)
> + dev->fwnode = of_fwnode_handle(of_node);
> +
> + ret = 0;
> +end:
> + put_device(dev);
> + return ret;
> +}
> +EXPORT_SYMBOL_GPL(device_add_of_node);
> +
> /**
> * device_set_of_node_from_dev - reuse device-tree node of another device
> * @dev: device whose device-tree node is being set
> diff --git a/include/linux/device.h b/include/linux/device.h
> index 80a5b3268986..1244e5892292 100644
> --- a/include/linux/device.h
> +++ b/include/linux/device.h
> @@ -1191,6 +1191,8 @@ int device_online(struct device *dev);
> void set_primary_fwnode(struct device *dev, struct fwnode_handle *fwnode);
> void set_secondary_fwnode(struct device *dev, struct fwnode_handle *fwnode);
> void device_set_node(struct device *dev, struct fwnode_handle *fwnode);
> +int device_add_of_node(struct device *dev, struct device_node *of_node);
> +void device_remove_of_node(struct device *dev);
> void device_set_of_node_from_dev(struct device *dev, const struct device *dev2);
>
> static inline struct device_node *dev_of_node(struct device *dev)
next prev parent reply other threads:[~2025-02-19 15:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 7:34 [PATCH v7 0/5] Add support for the PCI host bridge device-tree node creation Herve Codina
2025-02-04 7:34 ` [PATCH v7 1/5] driver core: Introduce device_{add,remove}_of_node() Herve Codina
2025-02-19 8:27 ` Greg Kroah-Hartman
2025-02-19 15:59 ` Jonathan Cameron [this message]
2025-02-20 8:12 ` Herve Codina
2025-02-04 7:34 ` [PATCH v7 2/5] PCI: of: Use device_{add,remove}_of_node() to attach of_node to existing device Herve Codina
2025-02-04 7:34 ` [PATCH v7 3/5] PCI: of_property: Add support for NULL pdev in of_pci_set_address() Herve Codina
2025-02-04 7:34 ` [PATCH v7 4/5] PCI: of_property: Constify parameter in of_pci_get_addr_flags() Herve Codina
2025-02-04 7:35 ` [PATCH v7 5/5] PCI: of: Create device-tree PCI host bridge node Herve Codina
2025-02-19 17:39 ` Bjorn Helgaas
2025-02-20 8:25 ` Herve Codina
2025-02-21 0:07 ` Bjorn Helgaas
2025-02-21 8:34 ` Herve Codina
2025-02-21 18:19 ` Bjorn Helgaas
2025-02-19 8:24 ` [PATCH v7 0/5] Add support for the PCI host bridge device-tree node creation Herve Codina
2025-02-19 8:28 ` Greg Kroah-Hartman
2025-02-19 17:34 ` Bjorn Helgaas
2025-02-19 20:46 ` Rob Herring
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=20250219155901.000009e4@huawei.com \
--to=jonathan.cameron@huawei.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox