From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] Documentation: devicetree: arm: cpus/cpu nodes bindings updates
Date: Wed, 28 Aug 2013 20:45:58 +0100 [thread overview]
Message-ID: <20130828194558.568303E0A6F@localhost> (raw)
In-Reply-To: <1376559743-31848-2-git-send-email-lorenzo.pieralisi@arm.com>
On Thu, 15 Aug 2013 10:42:22 +0100, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> wrote:
> +=====================================
> +cpus and cpu node bindings definition
> +=====================================
> +
> +The ARM architecture, in accordance with the ePAPR, requires the cpus and cpu
> +nodes to be present and contain the properties described below.
> +
> +- cpus node
> +
> + Description: Container of cpu nodes
> +
> + The node name must be "cpus".
> +
> + A cpus node must define the following properties:
> +
> + - #address-cells
> + Usage: required
> + Value type: <u32>
> +
> + Definition depends on ARM architecture version and
> + configuration:
> +
> + # On uniprocessor ARM architectures previous to v7
> + value must be 0, since they have no register
> + providing CPU identification.
Just clued into this point from the other thread; Don't do this.
Uniprocessor should follow the same rules as 32bit or 64bit for the
value of #address-cells, and cpu nodes should have a reg property, even
if it is merely set to '0'.
g.
WARNING: multiple messages have this Message-ID (diff)
From: Grant Likely <grant.likely@secretlab.ca>
To: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Ian Campbell <ian.campbell@citrix.com>,
Pawel Moll <pawel.moll@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Will Deacon <will.deacon@arm.com>,
Rob Herring <rob.herring@calxeda.com>,
Hanjun Guo <hanjun.guo@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Dave Martin <dave.martin@arm.com>
Subject: Re: [PATCH 1/2] Documentation: devicetree: arm: cpus/cpu nodes bindings updates
Date: Wed, 28 Aug 2013 20:45:58 +0100 [thread overview]
Message-ID: <20130828194558.568303E0A6F@localhost> (raw)
In-Reply-To: <1376559743-31848-2-git-send-email-lorenzo.pieralisi@arm.com>
On Thu, 15 Aug 2013 10:42:22 +0100, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> wrote:
> +=====================================
> +cpus and cpu node bindings definition
> +=====================================
> +
> +The ARM architecture, in accordance with the ePAPR, requires the cpus and cpu
> +nodes to be present and contain the properties described below.
> +
> +- cpus node
> +
> + Description: Container of cpu nodes
> +
> + The node name must be "cpus".
> +
> + A cpus node must define the following properties:
> +
> + - #address-cells
> + Usage: required
> + Value type: <u32>
> +
> + Definition depends on ARM architecture version and
> + configuration:
> +
> + # On uniprocessor ARM architectures previous to v7
> + value must be 0, since they have no register
> + providing CPU identification.
Just clued into this point from the other thread; Don't do this.
Uniprocessor should follow the same rules as 32bit or 64bit for the
value of #address-cells, and cpu nodes should have a reg property, even
if it is merely set to '0'.
g.
next prev parent reply other threads:[~2013-08-28 19:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 9:42 [PATCH 0/2] ARM DT cpus/cpu and topology bindings Lorenzo Pieralisi
2013-08-15 9:42 ` [PATCH 1/2] Documentation: devicetree: arm: cpus/cpu nodes bindings updates Lorenzo Pieralisi
2013-08-15 14:32 ` Rob Herring
2013-08-15 15:22 ` Lorenzo Pieralisi
2013-08-19 10:34 ` Afzal Mohammed
2013-09-13 16:57 ` Lorenzo Pieralisi
2013-09-13 16:57 ` Lorenzo Pieralisi
2013-09-13 20:51 ` Rob Herring
2013-09-13 20:51 ` Rob Herring
2013-09-14 7:49 ` Andrew Lunn
2013-09-14 7:49 ` Andrew Lunn
2013-09-16 8:55 ` Lorenzo Pieralisi
2013-09-16 8:55 ` Lorenzo Pieralisi
2013-09-15 8:36 ` Andrew Lunn
2013-09-15 8:36 ` Andrew Lunn
2013-09-16 8:57 ` Lorenzo Pieralisi
2013-09-16 8:57 ` Lorenzo Pieralisi
2013-08-16 23:15 ` Stephen Warren
2013-08-28 19:45 ` Grant Likely [this message]
2013-08-28 19:45 ` Grant Likely
2013-08-15 9:42 ` [PATCH 2/2] Documentation: DT: arm: define CPU topology bindings Lorenzo Pieralisi
2013-09-13 16:39 ` Lorenzo Pieralisi
2013-09-13 16:39 ` Lorenzo Pieralisi
2013-09-13 21:07 ` Rob Herring
2013-09-13 21:07 ` Rob Herring
2013-09-16 9:10 ` Lorenzo Pieralisi
2013-09-16 9:10 ` Lorenzo Pieralisi
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=20130828194558.568303E0A6F@localhost \
--to=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.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.