From mboxrd@z Thu Jan 1 00:00:00 1970 From: jszhang@marvell.com (Jisheng Zhang) Date: Tue, 21 Jul 2015 22:50:06 +0800 Subject: [PATCH 1/2] arm64: dts: Add dts files for Marvell Berlin4CT SoC In-Reply-To: <20150721143426.GC10595@leverpostej> References: <1437488279-2088-1-git-send-email-jszhang@marvell.com> <1437488279-2088-2-git-send-email-jszhang@marvell.com> <20150721143426.GC10595@leverpostej> Message-ID: <20150721225006.04c3d071@xhacker> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Dear Mark, Thanks a lot for so quick review! On Tue, 21 Jul 2015 15:34:26 +0100 Mark Rutland wrote: > Hi, > > > +/dts-v1/; > > + > > +/memreserve/ 0x00000000 0x01000000; > > What's this reservation for? This is reserved for some firmwares' usage. > > Given you're using PSCI I can't see why we'd expect the kernel to map > but not use some memory. Is it acceptable that we make memory start at 0x01000000 instead of reservation? > > > + > > +#include "berlin4ct.dtsi" > > + > > +/ { > > + model = "MARVELL BG4CT DMP BOARD"; > > + compatible = "marvell,berlin4ct-dmp", "marvell,berlin4ct", "marvell,berlin"; > > + > > + chosen { > > + bootargs = "earlyprintk"; > > + stdout-path = "serial0:115200n8"; > > + }; > > You shouldn't need those bootargs; "earlyprintk" does nothing on arm64. will fix in a newer version > > [...] > > > + gic: interrupt-controller at 901000 { > > + compatible = "arm,gic-400"; > > + #interrupt-cells = <3>; > > + interrupt-controller; > > + reg = <0x901000 0x1000>, > > + <0x902000 0x1000>, > > + <0x904000 0x2000>, > > + <0x906000 0x2000>; > > + interrupts = ; > > + }; > > + > > I believe the size of the cpu interface (the second reg entry) should be > 0x2000, as GICC_DIR is at offset 0x1000. Oh, Yes! Thanks for pointing this out. > > Otherwise this looks fine. > > Thanks, > Mark.