mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suzuki K Poulose <Suzuki.Poulose@arm.com>
To: Marc Zyngier <marc.zyngier@arm.com>,
	linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, will.deacon@arm.com,
	mark.rutland@arm.com, peterz@infradead.org,
	Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 2/6] of: Add helper for mapping device node to logical CPU number
Date: Mon, 24 Jul 2017 16:15:01 +0100	[thread overview]
Message-ID: <b0484d86-0c0c-7c7f-6196-7c68c717a219@arm.com> (raw)
In-Reply-To: <ff7f1757-0beb-b87c-8965-d9fb29e6de47@arm.com>

Hi Marc,


On 24/07/17 14:14, Marc Zyngier wrote:
> On 24/07/17 11:29, Suzuki K Poulose 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: Rob Herring <robh+dt@kernel.org>
>> Cc: Mark Rutland <mark.rutland@arm.com>
>> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
>> ---
>>  drivers/of/base.c         | 26 ++++++++++++++++++++++++++
>>  include/linux/of_device.h |  7 +++++++
>>  2 files changed, 33 insertions(+)
>>
>> diff --git a/drivers/of/base.c b/drivers/of/base.c
>> index 686628d..639af23 100644
>> --- a/drivers/of/base.c
>> +++ b/drivers/of/base.c

>> +int of_device_node_get_cpu(struct device_node *cpu_node)
>> +{
>> +	int cpu, thread;
>> +	bool found = false;
>> +	struct device_node *np;
>> +
>> +	for_each_possible_cpu(cpu) {
>> +		np = of_get_cpu_node(cpu, &thread);
>
> nit: Since you don't need the thread here, you can pass NULL instead.
>

Sure, will do that in the next version.


>
> FWIW:
>
> Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
>

Thanks for taking a look.

Suzuki

  reply	other threads:[~2017-07-24 15:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 10:29 [PATCH v2 0/6] perf: Support for ARM DynamIQ Shared Unit PMU Suzuki K Poulose
2017-07-24 10:29 ` [PATCH v2 1/6] perf: Export perf_event_update_userpage Suzuki K Poulose
2017-07-24 10:29 ` [PATCH v2 2/6] of: Add helper for mapping device node to logical CPU number Suzuki K Poulose
2017-07-24 13:14   ` Marc Zyngier
2017-07-24 15:15     ` Suzuki K Poulose [this message]
2017-07-24 16:42   ` Sudeep Holla
2017-07-25  9:27     ` Suzuki K Poulose
2017-07-25  9:49       ` Sudeep Holla
2017-07-24 10:29 ` [PATCH v2 3/6] coresight: of: Use of_device_node_get_cpu helper Suzuki K Poulose
2017-07-25 16:14   ` Mathieu Poirier
2017-07-24 10:29 ` [PATCH v2 4/6] irqchip: gic-v3: " Suzuki K Poulose
2017-07-24 13:15   ` Marc Zyngier
2017-07-24 10:29 ` [PATCH v2 5/6] dt-bindings: Document devicetree binding for ARM DSU PMU Suzuki K Poulose
2017-07-24 10:29 ` [PATCH v2 6/6] perf: ARM DynamIQ Shared Unit PMU support Suzuki K Poulose
2017-07-24 14:50   ` Jonathan Cameron
2017-07-24 15:44     ` Suzuki K Poulose
2017-07-25  8:33       ` 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=b0484d86-0c0c-7c7f-6196-7c68c717a219@arm.com \
    --to=suzuki.poulose@arm.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=peterz@infradead.org \
    --cc=robh+dt@kernel.org \
    --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

all inboxes | Powered by JetHome®