From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Alireza Sanaee <alireza.sanaee@huawei.com>
Cc: <devicetree@vger.kernel.org>, <robh@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>,
<mark.rutland@arm.com>, <shameerali.kolothum.thodi@huawei.com>,
<krzk@kernel.org>, <dianders@chromium.org>,
<catalin.marinas@arm.com>, <suzuki.poulose@arm.com>,
<mike.leach@linaro.org>, <james.clark@linaro.org>,
<linux-perf-users@vger.kernel.org>, <coresight@lists.linaro.org>,
<gshan@redhat.com>, <ruanjinjie@huawei.com>,
<saravanak@google.com>
Subject: Re: [PATCH v3 1/7] of: add infra for finding CPU id from phandle
Date: Wed, 28 May 2025 16:54:29 +0100 [thread overview]
Message-ID: <20250528165429.00000d4d@huawei.com> (raw)
In-Reply-To: <20250512080715.82-2-alireza.sanaee@huawei.com>
On Mon, 12 May 2025 09:07:09 +0100
Alireza Sanaee <alireza.sanaee@huawei.com> wrote:
> Get CPU id from phandle. Many drivers get do this by getting hold of CPU
> node first through a phandle and then find the CPU ID using the relevant
> function. This commit encapsulates cpu node finding and improves
> readability.
>
> The API interface requires two parameters, 1) node, 2) pointer to CPU
> node. API sets the pointer to the CPU node and allows the driver to play
> with the CPU itself, for logging purposes for instance.
>
> Signed-off-by: Alireza Sanaee <alireza.sanaee@huawei.com>
> ---
> drivers/of/cpu.c | 29 +++++++++++++++++++++++++++++
> include/linux/of.h | 9 +++++++++
> 2 files changed, 38 insertions(+)
>
> diff --git a/drivers/of/cpu.c b/drivers/of/cpu.c
> index 5214dc3d05ae..fba17994fc20 100644
> --- a/drivers/of/cpu.c
> +++ b/drivers/of/cpu.c
> @@ -173,6 +173,35 @@ int of_cpu_node_to_id(struct device_node *cpu_node)
> }
> EXPORT_SYMBOL(of_cpu_node_to_id);
>
> +/**
> + * of_cpu_phandle_to_id: Get the logical CPU number for a given device_node
> + *
> + * @node: Pointer to the device_node containing CPU phandle.
> + * @cpu_np: Pointer to the device_node for CPU.
> + * @cpu_idx: The index of the CPU in the list of CPUs.
> + *
> + * Return: The logical CPU number of the given CPU device_node or -ENODEV if
> + * the CPU is not found, or if the node is NULL, it returns -1. On success,
> + * cpu_np will always point to the retrieved CPU device_node with refcount
> + * incremented, use of_node_put() on it when done.
> + */
> +int of_cpu_phandle_to_id(const struct device_node *node,
> + struct device_node **cpu_np,
> + uint8_t cpu_idx)
> +{
> + if (!node)
> + return -1;
> +
> + *cpu_np = of_parse_phandle(node, "cpu", 0);
> + if (!*cpu_np)
> + *cpu_np = of_parse_phandle(node, "cpus", cpu_idx);
> + if (!*cpu_np)
> + return -ENODEV;
Indent has gone a bit crazy here.
> +
> + return of_cpu_node_to_id(*cpu_np);
> +}
> +EXPORT_SYMBOL(of_cpu_phandle_to_id);
> +
> /**
> * of_get_cpu_state_node - Get CPU's idle state node at the given index
> *
> diff --git a/include/linux/of.h b/include/linux/of.h
> index eaf0e2a2b75c..194f1cb0f6c6 100644
> --- a/include/linux/of.h
> +++ b/include/linux/of.h
> @@ -360,6 +360,8 @@ extern const void *of_get_property(const struct device_node *node,
> extern struct device_node *of_get_cpu_node(int cpu, unsigned int *thread);
> extern struct device_node *of_cpu_device_node_get(int cpu);
> extern int of_cpu_node_to_id(struct device_node *np);
> +extern int of_cpu_phandle_to_id(const struct device_node *np,
> + struct device_node **cpu_np, uint8_t cpu_idx);
> extern struct device_node *of_get_next_cpu_node(struct device_node *prev);
> extern struct device_node *of_get_cpu_state_node(const struct device_node *cpu_node,
> int index);
> @@ -662,6 +664,13 @@ static inline int of_cpu_node_to_id(struct device_node *np)
> return -ENODEV;
> }
>
> +static inline int of_cpu_phandle_to_id(const struct device_node *np,
> + struct device_node **cpu_np,
> + uint8_t cpu_idx)
> +{
> + return -ENODEV;
> +}
> +
> static inline struct device_node *of_get_next_cpu_node(struct device_node *prev)
> {
> return NULL;
next prev parent reply other threads:[~2025-05-28 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 8:07 [PATCH v3 0/7] DT: Enable sharing resources for SMT threads Alireza Sanaee
2025-05-12 8:07 ` [PATCH v3 1/7] of: add infra for finding CPU id from phandle Alireza Sanaee
2025-05-28 15:54 ` Jonathan Cameron [this message]
2025-05-12 8:07 ` [PATCH v3 2/7] arch_topology: update CPU map to use the new API Alireza Sanaee
2025-05-12 8:07 ` [PATCH v3 3/7] coresight: cti: Use of_cpu_phandle_to_id for grabbing CPU id Alireza Sanaee
2025-05-12 8:07 ` [PATCH v3 4/7] coresight: " Alireza Sanaee
2025-05-12 8:07 ` [PATCH v3 5/7] perf/arm-dsu: refactor cpu id retrieval via new API of_cpu_phandle_to_id Alireza Sanaee
2025-05-12 8:07 ` [PATCH v3 6/7] arm64: of: handle multiple threads in ARM cpu node Alireza Sanaee
2025-05-12 8:07 ` [PATCH v3 7/7] of: of_cpu_phandle_to_id to support SMT threads Alireza Sanaee
2025-06-06 14:18 ` Rob Herring
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=20250528165429.00000d4d@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alireza.sanaee@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=gshan@redhat.com \
--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 \
--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).