From: Rob Herring <robh@kernel.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Will Deacon <will.deacon@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH v4 2/6] of: Add helper for mapping device node to logical CPU number
Date: Mon, 7 Aug 2017 18:33:15 -0500 [thread overview]
Message-ID: <CAL_JsqLuvHwnrVKfS34T8xmBMx0x-0Y6VkaYCa7rtGi8fjS_kw@mail.gmail.com> (raw)
In-Reply-To: <1502099560-6267-3-git-send-email-suzuki.poulose@arm.com>
On Mon, Aug 7, 2017 at 4:52 AM, Suzuki K Poulose <suzuki.poulose@arm.com> wrote:
> Add a helper to map a device node to a logical CPU number to avoid
> duplication. Currently this is open coded in different places (e.g
> gic-v3, coresight). The helper tries to map device node to a "possible"
> logical CPU id, which may not be online yet. It is the responsibility
> of the user to make sure that the CPU is online. The helper uses
> of_get_cpu_node() which uses arch specific backends to match the phyiscal
> ids.
>
> Cc: devicetree@vger.kernel.org
> Cc: Frank Rowand <frowand.list@gmail.com>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Sudeep Holla <sudeep.holla@arm.com>
> Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
> ---
> Changes since V3:
> - Renamed the helper to of_cpu_node_to_id(), suggested by Rob
> - Return -ENODEV on failure than nr_cpus_id
> ---
> drivers/of/base.c | 26 ++++++++++++++++++++++++++
> include/linux/of.h | 7 +++++++
> 2 files changed, 33 insertions(+)
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2017-08-07 23:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 9:52 [PATCH v4 0/6] perf: Support for ARM DynamIQ Shared Unit PMU Suzuki K Poulose
2017-08-07 9:52 ` [PATCH v4 1/6] perf: Export perf_event_update_userpage Suzuki K Poulose
2017-08-07 9:52 ` [PATCH v4 2/6] of: Add helper for mapping device node to logical CPU number Suzuki K Poulose
2017-08-07 23:33 ` Rob Herring [this message]
2017-08-07 9:52 ` [PATCH v4 3/6] coresight: of: Use of_cpu_node_to_id helper Suzuki K Poulose
2017-08-08 9:18 ` kbuild test robot
2017-08-08 9:41 ` Suzuki K Poulose
2017-08-07 9:52 ` [PATCH v4 4/6] irqchip: gic-v3: " Suzuki K Poulose
2017-08-07 9:52 ` [PATCH v4 5/6] dt-bindings: Document devicetree binding for ARM DSU PMU Suzuki K Poulose
2017-08-07 9:52 ` [PATCH v4 6/6] perf: ARM DynamIQ Shared Unit PMU support Suzuki K Poulose
2017-08-08 10:57 ` kbuild test robot
2017-08-08 10:58 ` Suzuki K Poulose
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=CAL_JsqLuvHwnrVKfS34T8xmBMx0x-0Y6VkaYCa7rtGi8fjS_kw@mail.gmail.com \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=peterz@infradead.org \
--cc=sudeep.holla@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=will.deacon@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).