From: Julien Grall <julien.grall@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xenproject.org
Cc: stefano.stabellini@citrix.com
Subject: Re: [PATCH 2/8] xen/arm: Retrieve the correct number of cells when building dom0 DT
Date: Mon, 28 Sep 2015 16:25:24 +0100 [thread overview]
Message-ID: <56095BE4.9010400@citrix.com> (raw)
In-Reply-To: <1443453563.25250.272.camel@citrix.com>
On 28/09/15 16:19, Ian Campbell wrote:
> On Mon, 2015-09-28 at 15:59 +0100, Julien Grall wrote:
>> Hi Ian,
>>
>> On 25/09/15 17:01, Ian Campbell wrote:
>>> On Tue, 2015-09-22 at 18:47 +0100, Julien Grall wrote:
>>>> The function dt_n_*_cells will retrieve the number of cells for a
>>>> given
>>>> node. Those numbers may not be correct to use for the child "reg"
>>>> property if the parent is passed.
>>>
>>> I think a clearer way to express this is that the functions return the
>>> number of cells to use for a reg property in the given node, and so
>>> they
>>> will naturally not necessarily return the right number if you give them
>>> some other node (whether that's the parent or some other node
>>> entirely).
>>
>> I will rework this part into:
>>
>> "The function dt_n_*_cells return the number of cells to use for a reg
>> property in a given node. So those numbers won't be correct if the
>> parent of a give node is passed."
>
> ^n
>
>>
>>>
>>>> This is fine today because the parent is always the root node which
>>>> means there is no upper parent.
>>>>
>>>> Introduce new helpers dt_child_n_*_cells to retrieve the number of
>>>> cells for the address and size that can be used to create the "reg"
>>>> property of a child of a given parent.
>>>
>>> "of the immediate child of a given"
>>>
>>> maybe?
>>
>> I'm not sure to see why "immediate" is necessary here. A child is always
>> immediate, otherwise it would be grandchild or else.
>
> Sadly it's not as unambiguous as that in this kind of context, child could
> be taken to mean "somewhere below".
I will add the "immediate" to remove the ambiguity.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-09-28 15:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 17:47 [PATCH 0/8] xen/arm: gic-v2: Detect automatically aliased GIC400 Julien Grall
2015-09-22 17:47 ` [PATCH 1/8] xen/arm: gic: Make clear the GIC node is passed to make_hwdom_dt_node Julien Grall
2015-09-25 15:48 ` Ian Campbell
2015-09-28 14:49 ` Julien Grall
2015-09-22 17:47 ` [PATCH 2/8] xen/arm: Retrieve the correct number of cells when building dom0 DT Julien Grall
2015-09-25 16:01 ` Ian Campbell
2015-09-28 14:59 ` Julien Grall
2015-09-28 15:19 ` Ian Campbell
2015-09-28 15:25 ` Julien Grall [this message]
2015-09-22 17:47 ` [PATCH 3/8] xen/arm: Fix comment coding style in handle_node in domain_build.c Julien Grall
2015-09-25 16:03 ` Ian Campbell
2015-09-25 16:48 ` Ian Campbell
2015-09-22 17:47 ` [PATCH 4/8] xen/arm: Warn when a device tree path will be re-used by Xen Julien Grall
2015-09-25 16:10 ` Ian Campbell
2015-09-28 15:44 ` Julien Grall
2015-09-28 15:55 ` Ian Campbell
2015-09-28 16:05 ` Julien Grall
2015-09-28 17:46 ` Julien Grall
2015-09-22 17:47 ` [PATCH 5/8] xen/arm: vgic-v2: Drop cbase from arch_domain Julien Grall
2015-09-25 16:11 ` Ian Campbell
2015-09-22 17:47 ` [PATCH 6/8] xen/arm: gic: Check the size of the CPU and vCPU interface retrieved from DT Julien Grall
2015-09-25 16:19 ` Ian Campbell
2015-09-28 16:29 ` Julien Grall
2015-09-22 17:47 ` [PATCH 7/8] xen/arm: gic-v2: Detect automatically aliased GIC400 Julien Grall
2015-09-25 16:26 ` Ian Campbell
2015-09-28 18:07 ` Julien Grall
2015-09-29 10:51 ` Ian Campbell
2015-09-22 17:47 ` [PATCH 8/8] xen/arm: platform: Drop the quirks callback Julien Grall
2015-09-25 16:27 ` Ian Campbell
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=56095BE4.9010400@citrix.com \
--to=julien.grall@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.