From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Alireza Sanaee <alireza.sanaee@huawei.com>
Cc: <krzk@kernel.org>, <robh@kernel.org>,
<coresight@lists.linaro.org>, <devicetree@vger.kernel.org>,
<dianders@chromium.org>, <james.clark@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>, <linuxarm@huawei.com>,
<mark.rutland@arm.com>, <mike.leach@linaro.org>,
<ruanjinjie@huawei.com>, <saravanak@google.com>,
<shameerali.kolothum.thodi@huawei.com>
Subject: Re: [PATCH v2 4/5] coresight: Use of_cpu_phandle_to_id for grabbing CPU id
Date: Fri, 11 Jul 2025 10:30:44 +0100 [thread overview]
Message-ID: <20250711103044.000024f0@huawei.com> (raw)
In-Reply-To: <20250708151502.561-5-alireza.sanaee@huawei.com>
On Tue, 8 Jul 2025 16:15:01 +0100
Alireza Sanaee <alireza.sanaee@huawei.com> wrote:
> Use the newly created API to grab CPU id.
>
> Signed-off-by: Alireza Sanaee <alireza.sanaee@huawei.com>
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
We could just squash this to the call site, however it is in
an if / else if with the much larger acpi equivalent call so
probably worth keeping this trivial helper.
> ---
> 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);
> }
>
> /*
next prev parent reply other threads:[~2025-07-11 10:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 15:14 [PATCH v2 0/5] Refactoring finding CPU phandles in DT Alireza Sanaee
2025-07-08 15:14 ` [PATCH v2 1/5] of: add infra for finding CPU id from phandle Alireza Sanaee
2025-07-11 9:17 ` Jonathan Cameron
2025-07-11 9:35 ` Jonathan Cameron
2025-07-08 15:14 ` [PATCH v2 2/5] arch_topology: update CPU map to use the new API Alireza Sanaee
2025-07-11 9:25 ` Jonathan Cameron
2025-07-08 15:15 ` [PATCH v2 3/5] coresight: cti: Use of_cpu_phandle_to_id for grabbing CPU id Alireza Sanaee
2025-07-11 9:28 ` Jonathan Cameron
2025-07-11 15:55 ` Mike Leach
2025-07-11 16:08 ` Jonathan Cameron
2025-07-11 16:08 ` Jonathan Cameron
2025-07-08 15:15 ` [PATCH v2 4/5] coresight: " Alireza Sanaee
2025-07-11 9:30 ` Jonathan Cameron [this message]
2025-07-08 15:15 ` [PATCH v2 5/5] perf/arm-dsu: refactor cpu id retrieval via new API of_cpu_phandle_to_id Alireza Sanaee
2025-07-11 9:36 ` 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=20250711103044.000024f0@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alireza.sanaee@huawei.com \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=james.clark@linaro.org \
--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 \
/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.