From: Alireza Sanaee <alireza.sanaee@huawei.com>
To: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <jonathan.cameron@huawei.com>, <coresight@lists.linaro.org>,
<dianders@chromium.org>, <james.clark@linaro.org>,
<krzk@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-perf-users@vger.kernel.org>, <linuxarm@huawei.com>,
<mark.rutland@arm.com>, <mike.leach@linaro.org>,
<robh@kernel.org>, <ruanjinjie@huawei.com>,
<saravanak@google.com>, <shameerali.kolothum.thodi@huawei.com>,
<suzuki.poulose@arm.com>
Subject: [PATCH v3 5/6] coresight: Use of_cpu_phandle_to_id for grabbing CPU ID
Date: Fri, 18 Jul 2025 10:48:47 +0100 [thread overview]
Message-ID: <20250718094848.587-6-alireza.sanaee@huawei.com> (raw)
In-Reply-To: <20250718094848.587-1-alireza.sanaee@huawei.com>
Use the newly created API (of_cpu_phandle_to_id) to grab CPU ID.
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
Signed-off-by: Alireza Sanaee <alireza.sanaee@huawei.com>
---
drivers/hwtracing/coresight/coresight-platform.c | 15 +--------------
1 file changed, 1 insertion(+), 14 deletions(-)
diff --git a/drivers/hwtracing/coresight/coresight-platform.c b/drivers/hwtracing/coresight/coresight-platform.c
index 0db64c5f4995..95d46ea08936 100644
--- a/drivers/hwtracing/coresight/coresight-platform.c
+++ b/drivers/hwtracing/coresight/coresight-platform.c
@@ -167,20 +167,7 @@ of_coresight_get_output_ports_node(const struct device_node *node)
static int of_coresight_get_cpu(struct device *dev)
{
- int cpu;
- struct device_node *dn;
-
- if (!dev->of_node)
- return -ENODEV;
-
- dn = of_parse_phandle(dev->of_node, "cpu", 0);
- if (!dn)
- return -ENODEV;
-
- cpu = of_cpu_node_to_id(dn);
- of_node_put(dn);
-
- return cpu;
+ return of_cpu_phandle_to_id(dev->of_node, NULL, 0);
}
/*
--
2.43.0
next prev parent reply other threads:[~2025-07-18 10:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 9:48 [PATCH v3 0/6] Refactoring finding CPU phandles in DT Alireza Sanaee
2025-07-18 9:48 ` [PATCH v3 1/6] of: add infra for finding CPU id from phandle Alireza Sanaee
2025-07-18 11:10 ` Jonathan Cameron
2025-07-21 0:30 ` Rob Herring (Arm)
2025-07-18 9:48 ` [PATCH v3 2/6] arch_topology: drop the use of cpu_node in the pr_info Alireza Sanaee
2025-07-18 11:12 ` Jonathan Cameron
2025-07-18 9:48 ` [PATCH v3 3/6] arch_topology: update CPU map to use of_cpu_phandle_to_id Alireza Sanaee
2025-07-18 11:14 ` Jonathan Cameron
2025-07-18 9:48 ` [PATCH v3 4/6] coresight: cti: Use of_cpu_phandle_to_id for grabbing CPU id Alireza Sanaee
2025-07-18 11:14 ` Jonathan Cameron
2025-07-18 9:48 ` Alireza Sanaee [this message]
2025-07-18 12:59 ` [PATCH v3 5/6] coresight: Use of_cpu_phandle_to_id for grabbing CPU ID Mike Leach
2025-07-18 9:48 ` [PATCH v3 6/6] perf/arm-dsu: refactor cpu id retrieval via new API of_cpu_phandle_to_id Alireza Sanaee
2025-07-18 11:15 ` Jonathan Cameron
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=20250718094848.587-6-alireza.sanaee@huawei.com \
--to=alireza.sanaee@huawei.com \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=james.clark@linaro.org \
--cc=jonathan.cameron@huawei.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=robh@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=saravanak@google.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=suzuki.poulose@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