All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH] xen: get GIC addresses from DT
Date: Fri, 30 Nov 2012 13:15:34 +0000	[thread overview]
Message-ID: <50B8B176.3070206@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1211301209300.5310@kaball.uk.xensource.com>

On 30/11/12 12:25, Stefano Stabellini wrote:
> On Fri, 30 Nov 2012, David Vrabel wrote:
>> On 23/11/12 15:21, Stefano Stabellini wrote:
>>> Get the address of the GIC distributor, cpu, virtual and virtual cpu
>>> interfaces registers from device tree.
>>
>> The original intention of the early DTB parsing was to get the minimum
>> of info needed before the DTB could be translated into a more useful
>> form (similar to what Linux does).
>>
>> Is this something that is still being considered in the long term?  If
>> so, should the GIC be initialized from this translated form, instead of
>> using the early parsing?
> 
> Regardless of the final form of DT parsing in Xen, I think that CPU,
> memory and GIC are the three things that should be parsed early.

Ok.

>>> +bool_t device_tree_node_compatible(const void *fdt, int node, const char *match)
>>> +{
>>> +    int len, l;
>>> +    const void *prop;
>>> +
>>> +    prop = fdt_getprop(fdt, node, "compatible", &len);
>>> +    if ( prop == NULL )
>>> +        return 0;
>>> +
>>> +    while ( len > 0 ) {
>>> +        if ( !strncmp(prop, match, strlen(match)) )
>>> +            return 1;
>>> +        l = strlen(prop) + 1;
>>> +        prop += l;
>>> +        len -= l;
>>> +    }
>>
>> This doesn't look right.  Don't you need to split the prop string on
>> comma boundaries?
> 
> Nope, the compatible string to match is, for example, the entirety of
> "arm,cortex-a15-gic", or alternatively "arm,cortex-a9-gic". Trying to
> match just "cortex-a15-gic" would be incorrect.
> This is what Linux does too.

Yes, you're right. I was misrembering the format.

>>> +    cell = (const u32 *)prop->data;
>>> +    device_tree_get_reg(&cell, address_cells, size_cells, &start, &size);
>>
>> Is this needed?  This cell is reread below.
> 
> Yes, because device_tree_get_reg increments the cell pointer

Perhaps I wasn't clear.  The result of this device_tree_get_reg() is not
used anywhere, and the side effect of advancing cell is also not used.

>>> +
>>> +    cell = (const u32 *)prop->data;
>>> +    reg_cells = address_cells + size_cells;
>>> +    interfaces = fdt32_to_cpu(prop->len) / (reg_cells * sizeof(u32));

David

  parent reply	other threads:[~2012-11-30 13:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 15:21 [PATCH] xen: get GIC addresses from DT Stefano Stabellini
2012-11-29 10:40 ` Ian Campbell
2012-11-30 12:08   ` Stefano Stabellini
2012-11-30 12:18     ` Tim Deegan
2012-11-30 12:19     ` Ian Campbell
2012-11-30 11:26 ` David Vrabel
2012-11-30 12:25   ` Stefano Stabellini
2012-11-30 12:29     ` Ian Campbell
2012-11-30 12:48       ` Stefano Stabellini
2012-11-30 14:02         ` Stefano Stabellini
2012-11-30 14:08           ` Ian Campbell
2012-11-30 14:10             ` Stefano Stabellini
2012-11-30 13:15     ` David Vrabel [this message]
2012-11-30 14:08       ` Stefano Stabellini

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=50B8B176.3070206@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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 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.