From: "Rob Herring (Arm)" <robh@kernel.org>
To: Alireza Sanaee <alireza.sanaee@huawei.com>
Cc: mark.rutland@arm.com, shameerali.kolothum.thodi@huawei.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
jonathan.cameron@huawei.com,
linux-arm-kernel@lists.infradead.org, james.clark@linaro.org,
mike.leach@linaro.org, coresight@lists.linaro.org,
krzk@kernel.org, linuxarm@huawei.com, suzuki.poulose@arm.com,
dianders@chromium.org, ruanjinjie@huawei.com,
linux-perf-users@vger.kernel.org, saravanak@google.com
Subject: Re: [PATCH v3 1/6] of: add infra for finding CPU id from phandle
Date: Sun, 20 Jul 2025 19:30:08 -0500 [thread overview]
Message-ID: <175305780744.3139904.12956973374132329407.robh@kernel.org> (raw)
In-Reply-To: <20250718094848.587-2-alireza.sanaee@huawei.com>
On Fri, 18 Jul 2025 10:48:43 +0100, Alireza Sanaee wrote:
> Get CPU ID from phandle. Some drivers such as coresight, cti-coresight,
> or arm-dsu use this API for finding CPU node in DT. In particular,
> drivers do this by getting the CPU device_node through a phandle and
> then find the CPU ID using of_cpu_node_to_id(). This commit encapsulates
> CPU node finding and improves readability.
>
> The API interface takes three parameters, 1) node, 2) pointer to
> pointer of CPU node, 3) CPU node index. API sets the pointer to the CPU
> node and allows the driver to work with the CPU node, for logging
> purposes for instance.
>
> Signed-off-by: Alireza Sanaee <alireza.sanaee@huawei.com>
> ---
> drivers/of/cpu.c | 49 ++++++++++++++++++++++++++++++++++++++++++++++
> include/linux/of.h | 9 +++++++++
> 2 files changed, 58 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-07-21 0:30 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) [this message]
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 ` [PATCH v3 5/6] coresight: Use of_cpu_phandle_to_id for grabbing CPU ID Alireza Sanaee
2025-07-18 12:59 ` 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=175305780744.3139904.12956973374132329407.robh@kernel.org \
--to=robh@kernel.org \
--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=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=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;
as well as URLs for NNTP newsgroup(s).