linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] ARM: dts: add device_type prop to cpu nodes on Calxeda platforms
Date: Sun, 30 Dec 2012 10:15:02 -0600	[thread overview]
Message-ID: <1356884107-30991-2-git-send-email-robherring2@gmail.com> (raw)
In-Reply-To: <1356884107-30991-1-git-send-email-robherring2@gmail.com>

From: Rob Herring <rob.herring@calxeda.com>

While device_type is considered deprecated, it is still needed for tools
like lshw to identify cpu nodes.

Signed-off-by: Rob Herring <rob.herring@calxeda.com>
---
 arch/arm/boot/dts/ecx-2000.dts |    4 ++++
 arch/arm/boot/dts/highbank.dts |    4 ++++
 2 files changed, 8 insertions(+)

diff --git a/arch/arm/boot/dts/ecx-2000.dts b/arch/arm/boot/dts/ecx-2000.dts
index 46477ac..139b40c 100644
--- a/arch/arm/boot/dts/ecx-2000.dts
+++ b/arch/arm/boot/dts/ecx-2000.dts
@@ -32,6 +32,7 @@
 
 		cpu at 0 {
 			compatible = "arm,cortex-a15";
+			device_type = "cpu";
 			reg = <0>;
 			clocks = <&a9pll>;
 			clock-names = "cpu";
@@ -39,6 +40,7 @@
 
 		cpu at 1 {
 			compatible = "arm,cortex-a15";
+			device_type = "cpu";
 			reg = <1>;
 			clocks = <&a9pll>;
 			clock-names = "cpu";
@@ -46,6 +48,7 @@
 
 		cpu at 2 {
 			compatible = "arm,cortex-a15";
+			device_type = "cpu";
 			reg = <2>;
 			clocks = <&a9pll>;
 			clock-names = "cpu";
@@ -53,6 +56,7 @@
 
 		cpu at 3 {
 			compatible = "arm,cortex-a15";
+			device_type = "cpu";
 			reg = <3>;
 			clocks = <&a9pll>;
 			clock-names = "cpu";
diff --git a/arch/arm/boot/dts/highbank.dts b/arch/arm/boot/dts/highbank.dts
index a9ae5d3..81e0bfa 100644
--- a/arch/arm/boot/dts/highbank.dts
+++ b/arch/arm/boot/dts/highbank.dts
@@ -32,6 +32,7 @@
 
 		cpu at 0 {
 			compatible = "arm,cortex-a9";
+			device_type = "cpu";
 			reg = <0>;
 			next-level-cache = <&L2>;
 			clocks = <&a9pll>;
@@ -40,6 +41,7 @@
 
 		cpu at 1 {
 			compatible = "arm,cortex-a9";
+			device_type = "cpu";
 			reg = <1>;
 			next-level-cache = <&L2>;
 			clocks = <&a9pll>;
@@ -48,6 +50,7 @@
 
 		cpu at 2 {
 			compatible = "arm,cortex-a9";
+			device_type = "cpu";
 			reg = <2>;
 			next-level-cache = <&L2>;
 			clocks = <&a9pll>;
@@ -56,6 +59,7 @@
 
 		cpu at 3 {
 			compatible = "arm,cortex-a9";
+			device_type = "cpu";
 			reg = <3>;
 			next-level-cache = <&L2>;
 			clocks = <&a9pll>;
-- 
1.7.10.4

  reply	other threads:[~2012-12-30 16:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-30 16:15 [PATCH 0/6] highbank fixes for 3.8 Rob Herring
2012-12-30 16:15 ` Rob Herring [this message]
2012-12-30 16:15 ` [PATCH 2/6] ARM: dts: fix highbank cpu mpidr values Rob Herring
2013-01-06  2:10   ` Shawn Guo
2012-12-30 16:15 ` [PATCH 3/6] ARM: highbank: fix typos with hignbank in power request functions Rob Herring
2012-12-30 16:15 ` [PATCH 4/6] ARM: highbank: fix secondary boot and hotplug Rob Herring
2012-12-30 16:15 ` [PATCH 5/6] ARM: highbank: add a power request clear Rob Herring
2012-12-30 16:15 ` [PATCH 6/6] ARM: highbank: save and restore L2 cache and GIC on suspend Rob Herring
2013-01-02 20:39 ` [PATCH 0/6] highbank fixes for 3.8 Olof Johansson

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=1356884107-30991-2-git-send-email-robherring2@gmail.com \
    --to=robherring2@gmail.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 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).