From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] Documentation: devicetree: arm: cpus/cpu nodes bindings updates
Date: Mon, 16 Sep 2013 21:28:16 +0200 [thread overview]
Message-ID: <52375BD0.9030303@free-electrons.com> (raw)
In-Reply-To: <1379330464-27917-2-git-send-email-lorenzo.pieralisi@arm.com>
On 16/09/2013 13:21, 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.
>
> Main changes:
> - adds 64-bit bindings
> - define usage of #address-cells
> - defines behaviour on pre and post v7 uniprocessor systems
> - adds ARM 11MPcore specific reg property definition
>
For the Marvell (EBU) related part
Acked-by:Gregory CLEMENT <gregory.clement@free-electrons.com>
I would like to point that pj4b could be split in two flavors:
pj4b (currently used by Armada 370) and pj4b-mp (currently used
by Armada XP). The motivation for a such split would be for the errata
fix which can be different between pj4b and pj4b_mp. As we can
detect them at runtime, we don't need it from the device tree.
So we can live with a single pj4b binding.
Regards,
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Gregory CLEMENT <gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
Benjamin Herrenschmidt
<benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>,
Nicolas Pitre
<nicolas.pitre-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Dave Martin <dave.martin-5wv7dgnIgG8@public.gmane.org>,
Vincent Guittot
<vincent.guittot-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Hanjun Guo <hanjun.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>
Subject: Re: [PATCH v2 1/2] Documentation: devicetree: arm: cpus/cpu nodes bindings updates
Date: Mon, 16 Sep 2013 21:28:16 +0200 [thread overview]
Message-ID: <52375BD0.9030303@free-electrons.com> (raw)
In-Reply-To: <1379330464-27917-2-git-send-email-lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>
On 16/09/2013 13:21, 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.
>
> Main changes:
> - adds 64-bit bindings
> - define usage of #address-cells
> - defines behaviour on pre and post v7 uniprocessor systems
> - adds ARM 11MPcore specific reg property definition
>
For the Marvell (EBU) related part
Acked-by:Gregory CLEMENT <gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
I would like to point that pj4b could be split in two flavors:
pj4b (currently used by Armada 370) and pj4b-mp (currently used
by Armada XP). The motivation for a such split would be for the errata
fix which can be different between pj4b and pj4b_mp. As we can
detect them at runtime, we don't need it from the device tree.
So we can live with a single pj4b binding.
Regards,
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-09-16 19:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 11:21 [PATCH v2 0/2] ARM DT cpus/cpu and topology bindings Lorenzo Pieralisi
2013-09-16 11:21 ` Lorenzo Pieralisi
2013-09-16 11:21 ` [PATCH v2 1/2] Documentation: devicetree: arm: cpus/cpu nodes bindings updates Lorenzo Pieralisi
2013-09-16 11:21 ` Lorenzo Pieralisi
2013-09-16 13:32 ` Jason Cooper
2013-09-16 13:32 ` Jason Cooper
2013-09-16 19:28 ` Gregory CLEMENT [this message]
2013-09-16 19:28 ` Gregory CLEMENT
2013-09-25 16:12 ` Mark Rutland
2013-09-25 16:12 ` Mark Rutland
2013-09-16 11:21 ` [PATCH v2 2/2] Documentation: DT: arm: define CPU topology bindings Lorenzo Pieralisi
2013-09-16 11:21 ` Lorenzo Pieralisi
2013-09-24 16:01 ` [PATCH v2 0/2] ARM DT cpus/cpu and " Lorenzo Pieralisi
2013-09-24 16:01 ` Lorenzo Pieralisi
2013-09-25 13:50 ` Rob Herring
2013-09-25 13:50 ` Rob Herring
2013-09-26 10:02 ` Lorenzo Pieralisi
2013-09-26 10:02 ` Lorenzo Pieralisi
2013-09-26 21:42 ` Rob Herring
2013-09-26 21:42 ` Rob Herring
2013-09-27 14:51 ` Lorenzo Pieralisi
2013-09-27 14:51 ` 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=52375BD0.9030303@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--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.