From: Suzuki.Poulose@arm.com (Suzuki K Poulose)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 3/6] coresight: of: Use of_cpu_node_to_id helper
Date: Tue, 10 Oct 2017 10:38:11 +0100 [thread overview]
Message-ID: <4518662b-01ce-30fd-a9ea-c517b2d1c5ff@arm.com> (raw)
In-Reply-To: <20171009025842.GA3146@leoy-linaro>
On 09/10/17 03:58, Leo Yan wrote:
> Hi Suzuki,
>
> On Fri, Oct 06, 2017 at 11:36:07AM +0100, Suzuki K Poulose wrote:
>> Reuse the new generic helper, of_cpu_node_to_id() to map a
>> given CPU phandle to a logical CPU number.
>>
>> Cc: Leo Yan <leo.yan@linaro.org>
>> Acked-by: Mathieu Poirier <mathieu.poirier@linaro.org>
>> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
>
> Tested-by: Leo Yan <leo.yan@linaro.org>
>
> BTW, I think the function get_cpu_for_node() in the file
> arch/arm64/kernel/topology.c we also can refactor with the same
> function, just reminding for this.
>
Leo,
Thanks for the testing and the pointer. Yes we can move that to
use the new helper. On another take, I found that the arm_pmu
can also use it for pmu_parse_irq_affinity(). I will add
them to the series.
Cheers
Suzuki
next prev parent reply other threads:[~2017-10-10 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 10:36 [PATCH v7 0/6] perf: Support for ARM DynamIQ Shared Unit Suzuki K Poulose
2017-10-06 10:36 ` [PATCH v7 1/6] perf: Export perf_event_update_userpage Suzuki K Poulose
2017-10-06 10:36 ` [PATCH v7 2/6] of: Add helper for mapping device node to logical CPU number Suzuki K Poulose
2017-10-06 10:36 ` [PATCH v7 3/6] coresight: of: Use of_cpu_node_to_id helper Suzuki K Poulose
2017-10-09 2:58 ` Leo Yan
2017-10-10 9:38 ` Suzuki K Poulose [this message]
2017-10-06 10:36 ` [PATCH v7 4/6] irqchip: gic-v3: " Suzuki K Poulose
2017-10-06 10:36 ` [PATCH v7 5/6] dt-bindings: Document devicetree binding for ARM DSU PMU Suzuki K Poulose
2017-10-06 10:36 ` [PATCH v7 6/6] perf: ARM DynamIQ Shared Unit PMU support 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=4518662b-01ce-30fd-a9ea-c517b2d1c5ff@arm.com \
--to=suzuki.poulose@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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