xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: stefano.stabellini@eu.citrix.com, patches@linaro.org,
	xen-devel@lists.xen.org
Subject: Re: [PATCH v2 5/6] xen/arm: Dissociate logical and hardware CPU ID
Date: Tue, 17 Sep 2013 16:18:30 +0100	[thread overview]
Message-ID: <523872C6.2020206@linaro.org> (raw)
In-Reply-To: <1379430493.11304.133.camel@hastur.hellion.org.uk>

On 09/17/2013 04:08 PM, Ian Campbell wrote:
> On Tue, 2013-09-17 at 16:02 +0100, Julien Grall wrote:
>> On 09/17/2013 03:39 PM, Ian Campbell wrote:
>>> On Wed, 2013-09-11 at 12:59 +0100, Julien Grall wrote:
>>>
>>>> +    dt_for_each_child_node( cpus, cpu )
>>>> +    {
>>>> +        u32 hwid;
>>>> +
>>>> +        if ( !dt_device_type_is_equal(cpu, "cpu") )
>>>> +            continue;
>>>
>>> This could eventually use dt_find_node_by_type which I added in my start
>>> of day rework. I would assume your patch will go in first so I'll try
>>> and remember to do that when I rebase...
>>
>> cpu node must be under /cpus.
> 
> Must it? Documentation/devicetree/bindings/arm/cpus.txt doesn't mention
> that.

In Documentation/devicetree/booting-without-of.txt:
 b) The /cpus node

  This node is the parent of all individual CPU nodes. It doesn't
  have any specific requirements, though it's generally good practice
  to have at least:

               #address-cells = <00000001>
               #size-cells    = <00000000>

  This defines that the "address" for a CPU is a single cell, and has
  no meaningful size. This is not necessary but the kernel will assume
  that format when reading the "reg" properties of a CPU node, see
  below

> But if it were required then wouldn't it be invalid to have a node with
> type cpu outside that subtree? IOW looking up by type would still be OK.
> FYI this is what arm64 Linux does.

On arm32 Linux it's only looks in /cpus :).
I'm fine to replace this loop with dt_find_node_by_type.
Will you take care of this change, or do I need to add your patch on my
series and modify the code?

>>  dt_find_node_by_type will look at all the
>> nodes (not only the child) so we can't replace by this call.


-- 
Julien Grall

  reply	other threads:[~2013-09-17 15:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 11:59 [PATCH v2 0/6] Dissociate logical and gic/hardware CPU ID Julien Grall
2013-09-11 11:59 ` [PATCH v2 1/6] xen/arm: use cpumask_t to describe cpu mask in gic_route_dt_irq Julien Grall
2013-09-11 11:59 ` [PATCH v2 2/6] xen/arm: Initialize correctly IRQ routing Julien Grall
2013-09-11 11:59 ` [PATCH v2 3/6] xen/arm: gic: Use the correct CPU ID Julien Grall
2013-09-17 14:36   ` Ian Campbell
2013-09-17 15:04     ` Julien Grall
2013-09-11 11:59 ` [PATCH v2 4/6] xen/arm: Fix assert in send_SGI_one Julien Grall
2013-09-11 11:59 ` [PATCH v2 5/6] xen/arm: Dissociate logical and hardware CPU ID Julien Grall
2013-09-17 14:39   ` Ian Campbell
2013-09-17 15:02     ` Julien Grall
2013-09-17 15:08       ` Ian Campbell
2013-09-17 15:18         ` Julien Grall [this message]
2013-09-17 15:25           ` Ian Campbell
2013-09-11 11:59 ` [PATCH v2 6/6] xen/arm: Use the hardware ID to boot correctly secondary cpus Julien Grall

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=523872C6.2020206@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=patches@linaro.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).