Thread (2 messages) read the whole thread 2 messages, 2 authors, 2016-02-19

Re: [PATCH 1/4] arm64: Broadcom Vulcan support

From: Mark Rutland <hidden>
Date: 2016-02-17 17:16:17
Also in: linux-arm-kernel

Hi,

On Sun, Feb 14, 2016 at 12:16:32AM +0530, Jayachandran C wrote:
From: Zi Shen Lim <zlim-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
+	compatible = "brcm,vulcan-eval", "brcm,vulcan";
You use "brcm,vulcan" as the compatible string for both the platform and
the CPU nodes. You need different strings.
+
+	memory {
+		device_type = "memory";
+		reg = <0x00000000 0x80000000 0x0 0x80000000>,  /* 2G @ 2G  */
+		      <0x00000008 0x80000000 0x0 0x80000000>;  /* 2G @ 34G */
+	};
+/memreserve/ 0x80000000 0x00010000;
What is this for?
+
+/ {
+	model = "Broadcom Vulcan";
+	compatible = "brcm,vulcan";
As above, it doesn't make sense to have the same compatible string for
both the platform as a whole and the CPU.
+			device_type = "cpu";
+			compatible = "brcm,vulcan", "arm,armv8";
+			reg = <0x0 0x0>;
+			enable-method = "psci";
+		};
Thanks,
Mark.
--
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help