From: Jing Zhang <renyu.zj@linux.alibaba.com>
To: Will Deacon <will@kernel.org>, Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Shuai Xue <xueshuai@linux.alibaba.com>,
Zhuo Song <zhuo.song@linux.alibaba.com>
Subject: Re: [PATCH] perf/arm-cmn: Fix and refactor device mapping resource
Date: Sat, 18 Feb 2023 23:16:17 +0800 [thread overview]
Message-ID: <fffbd8d2-11ad-1c09-6174-76cb13fa5e59@linux.alibaba.com> (raw)
In-Reply-To: <1676535470-120560-1-git-send-email-renyu.zj@linux.alibaba.com>
Hi all,
Do you have any comments on this?:)
Thanks,
Jing
在 2023/2/16 下午4:17, Jing Zhang 写道:
> The devm_platform_ioremap_resource() won't let the platform device
> claim resource when the ACPI companion device has already claimed it.
> If CMN-ANY except CMN600 is ACPI companion device, it will return
> -EBUSY in devm_platform_ioremap_resource(), and the driver cannot be
> successfully installed.
>
> So let ACPI companion device call arm_cmn_acpi_probe and not claim
> resource again. In addition, the arm_cmn_acpi_probe() and
> arm_cmn_of_probe() functions are refactored to make them compatible
> with both CMN600 and CMN-ANY.
>
> Fixes: 61ec1d875812 ("perf/arm-cmn: Demarcate CMN-600 specifics")
> Signed-off-by: Jing Zhang <renyu.zj@linux.alibaba.com>
> ---
> drivers/perf/arm-cmn.c | 57 ++++++++++++++++++++++++++++++++------------------
> 1 file changed, 37 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/perf/arm-cmn.c b/drivers/perf/arm-cmn.c
> index 1deb61b..beb3b37 100644
> --- a/drivers/perf/arm-cmn.c
> +++ b/drivers/perf/arm-cmn.c
> @@ -2206,7 +2206,7 @@ static int arm_cmn_discover(struct arm_cmn *cmn, unsigned int rgn_offset)
> return 0;
> }
>
> -static int arm_cmn600_acpi_probe(struct platform_device *pdev, struct arm_cmn *cmn)
> +static int arm_cmn_acpi_probe(struct platform_device *pdev, struct arm_cmn *cmn)
> {
> struct resource *cfg, *root;
>
> @@ -2214,12 +2214,21 @@ static int arm_cmn600_acpi_probe(struct platform_device *pdev, struct arm_cmn *c
> if (!cfg)
> return -EINVAL;
>
> - root = platform_get_resource(pdev, IORESOURCE_MEM, 1);
> - if (!root)
> - return -EINVAL;
> + /* If ACPI defines more than one resource, such as cmn-600, then there may be
> + * a deviation between ROOTNODEBASE and PERIPHBASE, and ROOTNODEBASE can
> + * be obtained from the second resource. Otherwise, it can be considered that
> + * ROOT NODE BASE is PERIPHBASE. This is compatible with cmn-600 and cmn-any.
> + */
> + if (pdev->num_resources > 1) {
> + root = platform_get_resource(pdev, IORESOURCE_MEM, 1);
> + if (!root)
> + return -EINVAL;
>
> - if (!resource_contains(cfg, root))
> - swap(cfg, root);
> + if (!resource_contains(cfg, root))
> + swap(cfg, root);
> + } else {
> + root = cfg;
> + }
> /*
> * Note that devm_ioremap_resource() is dumb and won't let the platform
> * device claim cfg when the ACPI companion device has already claimed
> @@ -2227,17 +2236,30 @@ static int arm_cmn600_acpi_probe(struct platform_device *pdev, struct arm_cmn *c
> * appropriate name, we don't really need to do it again here anyway.
> */
> cmn->base = devm_ioremap(cmn->dev, cfg->start, resource_size(cfg));
> - if (!cmn->base)
> - return -ENOMEM;
> + if (IS_ERR(cmn->base))
> + return PTR_ERR(cmn->base);
>
> return root->start - cfg->start;
> }
>
> -static int arm_cmn600_of_probe(struct device_node *np)
> +static int arm_cmn_of_probe(struct platform_device *pdev, struct arm_cmn *cmn)
> {
> u32 rootnode;
> + int ret;
> +
> + cmn->base = devm_platform_ioremap_resource(pdev, 0);
> + if (IS_ERR(cmn->base))
> + return PTR_ERR(cmn->base);
>
> - return of_property_read_u32(np, "arm,root-node", &rootnode) ?: rootnode;
> + /* If of_property_read_u32() return EINVAL, it means that device tree has
> + * not define root-node, and root-node will return 0, which is compatible
> + * with cmn-600 and cmn-any.
> + */
> + ret = of_property_read_u32(pdev->dev.of_node, "arm,root-node", &rootnode);
> + if (ret == -EINVAL)
> + return 0;
> +
> + return rootnode;
> }
>
> static int arm_cmn_probe(struct platform_device *pdev)
> @@ -2255,16 +2277,11 @@ static int arm_cmn_probe(struct platform_device *pdev)
> cmn->model = (unsigned long)device_get_match_data(cmn->dev);
> platform_set_drvdata(pdev, cmn);
>
> - if (cmn->model == CMN600 && has_acpi_companion(cmn->dev)) {
> - rootnode = arm_cmn600_acpi_probe(pdev, cmn);
> - } else {
> - rootnode = 0;
> - cmn->base = devm_platform_ioremap_resource(pdev, 0);
> - if (IS_ERR(cmn->base))
> - return PTR_ERR(cmn->base);
> - if (cmn->model == CMN600)
> - rootnode = arm_cmn600_of_probe(pdev->dev.of_node);
> - }
> + if (has_acpi_companion(cmn->dev))
> + rootnode = arm_cmn_acpi_probe(pdev, cmn);
> + else
> + rootnode = arm_cmn_of_probe(pdev, cmn);
> +
> if (rootnode < 0)
> return rootnode;
>
next prev parent reply other threads:[~2023-02-18 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 8:17 Jing Zhang
2023-02-18 15:16 ` Jing Zhang [this message]
2023-03-06 6:18 ` Jing Zhang
2023-03-27 14:05 ` Will Deacon
2023-03-27 14:27 ` Robin Murphy
2023-03-29 9:48 ` Jing Zhang
2023-03-29 10:53 ` Robin Murphy
2023-03-29 11:34 ` Jing Zhang
2025-02-18 5:20 ` YinFengwei
2023-03-29 12:08 ` Robin Murphy
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=fffbd8d2-11ad-1c09-6174-76cb13fa5e59@linux.alibaba.com \
--to=renyu.zj@linux.alibaba.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
--cc=xueshuai@linux.alibaba.com \
--cc=zhuo.song@linux.alibaba.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
all inboxes | Powered by JetHome®