All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>,
	Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
	xen-devel@lists.xenproject.org
Cc: vijaya.kumar@caviumnetworks.com
Subject: Re: [PATCH] xen/arm: Correctly read the GICv3 Re-Distributor stride
Date: Wed, 30 Sep 2015 12:11:44 +0100	[thread overview]
Message-ID: <560BC370.5030900@citrix.com> (raw)
In-Reply-To: <1443611055.16718.184.camel@citrix.com>

On 30/09/15 12:04, Ian Campbell wrote:
> On Wed, 2015-09-30 at 11:54 +0100, Shameerali Kolothum Thodi wrote:
>> The GICv3 driver read a 32 bit value for the re-distributor stride, but
>> the dts binding is a two-cell property.
> 
> The binding doc I have says:
> 
> - redistributor-stride : If using padding pages, specifies the stride
>   of consecutive redistributors. Must be a multiple of 64kB.
> 
> i.e. it doesn't say anything about the size. The _example_ is 2 cells, but
> I don't think that is normative.
> 
> Unless you can point to a bindings update which specifies strictly two
> cells then I think the right answer is the use dt_read_number.

FWIW Linux is using of_property_read_u64 to get the stride. It has
always been the case and I don't understand how we end up to use
dt_property_u32 in Xen as we port the driver from Linux...

So before using dt_read_number in Xen, I would rather check if the DT
binding is not clear enough or the Linux drivers doesn't respect the
binding.

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-09-30 11:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 10:54 [PATCH] xen/arm: Correctly read the GICv3 Re-Distributor stride Shameerali Kolothum Thodi
2015-09-30 11:04 ` Ian Campbell
2015-09-30 11:11   ` Julien Grall [this message]
2015-09-30 11:29   ` Shameerali Kolothum Thodi
2015-09-30 13:30     ` Ian Campbell
2015-09-30 11:06 ` 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=560BC370.5030900@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=vijaya.kumar@caviumnetworks.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.