From: Robin Murphy <robin.murphy@arm.com>
To: "Rob Herring (Arm)" <robh@kernel.org>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu: Use of_property_present()
Date: Thu, 1 Aug 2024 10:58:52 +0100 [thread overview]
Message-ID: <c9e7107e-f1fd-4a22-be6d-45eef392f76b@arm.com> (raw)
In-Reply-To: <20240731191312.1710417-6-robh@kernel.org>
On 2024-07-31 8:12 pm, Rob Herring (Arm) wrote:
> Use of_property_present() to test for property presence rather than
> of_(find|get)_property(). This is part of a larger effort to remove
> callers of of_find_property() and similar functions. of_find_property()
> leaks the DT struct property and data pointers which is a problem for
> dynamically allocated nodes which may be freed.
Reviewed-by: Robin Murphy <robin.murphy@arm.com>
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---
> drivers/iommu/fsl_pamu_domain.c | 4 +---
> drivers/iommu/of_iommu.c | 2 +-
> 2 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iommu/fsl_pamu_domain.c b/drivers/iommu/fsl_pamu_domain.c
> index e9d2bff4659b..30be786bff11 100644
> --- a/drivers/iommu/fsl_pamu_domain.c
> +++ b/drivers/iommu/fsl_pamu_domain.c
> @@ -416,14 +416,12 @@ static struct iommu_group *fsl_pamu_device_group(struct device *dev)
>
> static struct iommu_device *fsl_pamu_probe_device(struct device *dev)
> {
> - int len;
> -
> /*
> * uboot must fill the fsl,liodn for platform devices to be supported by
> * the iommu.
> */
> if (!dev_is_pci(dev) &&
> - !of_get_property(dev->of_node, "fsl,liodn", &len))
> + !of_property_present(dev->of_node, "fsl,liodn"))
> return ERR_PTR(-ENODEV);
>
> return &pamu_iommu;
> diff --git a/drivers/iommu/of_iommu.c b/drivers/iommu/of_iommu.c
> index 78d61da75257..e7a6a1611d19 100644
> --- a/drivers/iommu/of_iommu.c
> +++ b/drivers/iommu/of_iommu.c
> @@ -214,7 +214,7 @@ void of_iommu_get_resv_regions(struct device *dev, struct list_head *list)
> * that represent reservations in the IOVA space, which are regions that should
> * not be mapped.
> */
> - if (of_find_property(it.node, "reg", NULL)) {
> + if (of_property_present(it.node, "reg")) {
> err = of_address_to_resource(it.node, 0, &phys);
> if (err < 0) {
> dev_err(dev, "failed to parse memory region %pOF: %d\n",
next prev parent reply other threads:[~2024-08-01 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 19:12 Rob Herring (Arm)
2024-08-01 9:58 ` Robin Murphy [this message]
2024-09-03 19:20 ` Rob Herring
2024-09-04 9:31 ` Joerg Roedel
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=c9e7107e-f1fd-4a22-be6d-45eef392f76b@arm.com \
--to=robin.murphy@arm.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=will@kernel.org \
/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®