From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/2] ARM: DT: kernel: DT cpu node bindings update
Date: Mon, 15 Apr 2013 13:26:02 -0600 [thread overview]
Message-ID: <516C544A.4090107@wwwdotorg.org> (raw)
In-Reply-To: <1366042402-8987-3-git-send-email-lorenzo.pieralisi@arm.com>
On 04/15/2013 10:13 AM, Lorenzo Pieralisi wrote:
> In order to extend the current cpu nodes bindings to newer CPUs
> inclusive of AArch64 and to update support for older ARM CPUs this
> patch updates device tree documentation for the cpu nodes bindings.
>
> diff --git a/Documentation/devicetree/bindings/arm/cpus.txt b/Documentation/devicetree/bindings/arm/cpus.txt
> http://devicetree.org
>
> -For the ARM architecture every CPU node must contain the following properties:
> -
...
> +with updates for 32-bit and 64-bit ARM systems provided in this document.
> +
> +In the bindings below:
That's a slightly odd change, since it removes the statement that a cpus
node must exist, and "in the bindings below" is not idiomatic for DT
binding definitions.
Perhaps replace that last list with:
The ARM architecture requires the following properties in the cpus and
cpu nodes contain the properties described below.
> +- square brackets define bitfields, eg reg[7:0] value of the bitfield in
> + the reg property contained in bits 7 down to 0
Isn't that standard enough it's not even worth mentioning? If it is,
it's certainly not something that should be mentioned in the part of the
document that describes which properties are requried.
> + - #address-cells
> + Usage: required
"Usage" sounds more like what it's used for. "Presence" seems better to me.
> + # On ARM architecture versions >= 7 based 32-bit
> + systems this property is required and matches the
Perhaps "On 32-bit ARMv7 or later systems, this property ..."
> + # On ARM v8 64-bit systems, where the reg property
Should there be an explicit note here re: 32-bit SW running on a 64-bit
system?
Perhaps "on ARMv8 systems running 32-bit or 64- bit software, the reg
property ..."
> + is made up of two cells to accomodate the 64-bit
> + MPDIR_EL1 register this property is required and
> + matches:
s/matches/must contain/
> + - enable-method
> + Usage: required on ARM 64-bit systems, optional on ARM 32-bit
> + systems
> + Value type: <string>
> + Definition: On ARM 64-bit systems must be "spin-table" [1].
Can that be an integer instead? with dtc+cpp support, that shouldn't
hurt the eyes too much any more.
> + - cpu-release-addr
> + Usage: required on ARM 64-bit systems, optional on ARM 32-bit
> + systems
> + Value type: <prop-encoded-array>
> + Definition: On ARM 64-bit systems must be a two cell
> + property identifying a 64-bit zero-initialised
> + memory location [1].
Presumably that property is required, or not, based on the value of
enable-method, not based on the ARM architecture or bit-size?
> +[1] ARM Linux kernel documentation
> + Documentation/devicetree/bindings/arm64/booting.txt
Is referencing Linux-specific documentation from a supposedly
OS-agnostic DT binding definition a good idea?
next prev parent reply other threads:[~2013-04-15 19:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 16:13 [RFC PATCH 0/2] ARM: DT cpu bindings updates Lorenzo Pieralisi
2013-04-15 16:13 ` [RFC PATCH 1/2] ARM: DT: kernel: move temporary cpu map stack array to static data Lorenzo Pieralisi
2013-04-15 16:13 ` [RFC PATCH 2/2] ARM: DT: kernel: DT cpu node bindings update Lorenzo Pieralisi
2013-04-15 19:26 ` Stephen Warren [this message]
2013-04-16 10:45 ` Lorenzo Pieralisi
2013-04-16 15:57 ` Stephen Warren
2013-04-16 16:21 ` Benjamin Herrenschmidt
2013-04-16 14:30 ` Dave Martin
2013-04-17 9:14 ` Mark Rutland
2013-04-17 15:14 ` Stephen Warren
2013-04-17 16:02 ` Nicolas Pitre
2013-04-17 16:23 ` Stephen Warren
2013-04-17 16:36 ` Nicolas Pitre
2013-04-17 16:56 ` Dave Martin
2013-04-17 16:24 ` Benjamin Herrenschmidt
2013-04-18 12:40 ` Grant Likely
2013-04-16 2:41 ` Simon Horman
2013-04-16 11:00 ` Lorenzo Pieralisi
2013-04-17 9:35 ` Nicolas Ferre
2013-04-17 11:44 ` Lorenzo Pieralisi
2013-04-17 9:48 ` Arnd Bergmann
2013-04-17 11:02 ` 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=516C544A.4090107@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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 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).