From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751981AbcDRIpn (ORCPT ); Mon, 18 Apr 2016 04:45:43 -0400 Received: from foss.arm.com ([217.140.101.70]:60277 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751744AbcDRIpl (ORCPT ); Mon, 18 Apr 2016 04:45:41 -0400 Date: Mon, 18 Apr 2016 09:45:09 +0100 From: Mark Rutland To: Masahiro Yamada Cc: arm@kernel.org, devicetree@vger.kernel.org, Kumar Gala , linux-kernel@vger.kernel.org, Ian Campbell , Rob Herring , Pawel Moll , Will Deacon , Catalin Marinas , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] arm64: dts: uniphier: add /memreserve/ for spin-table release address Message-ID: <20160418084508.GA21438@leverpostej> References: <1460743138-17768-1-git-send-email-yamada.masahiro@socionext.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1460743138-17768-1-git-send-email-yamada.masahiro@socionext.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Apr 16, 2016 at 02:58:58AM +0900, Masahiro Yamada wrote: > As Documentation/arm64/booting.txt says, the cpu-release-addr > location should be reserved. > > Signed-off-by: Masahiro Yamada > --- > > arch/arm64/boot/dts/socionext/uniphier-ph1-ld20.dtsi | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/arch/arm64/boot/dts/socionext/uniphier-ph1-ld20.dtsi b/arch/arm64/boot/dts/socionext/uniphier-ph1-ld20.dtsi > index 651c9d9..90909d2 100644 > --- a/arch/arm64/boot/dts/socionext/uniphier-ph1-ld20.dtsi > +++ b/arch/arm64/boot/dts/socionext/uniphier-ph1-ld20.dtsi > @@ -42,6 +42,8 @@ > * OTHER DEALINGS IN THE SOFTWARE. > */ > > +/memreserve/ 0x80000100 0x00000008; > + Please add a comment above the memreserve to mention what it is protecting. That helps to avoid having this cargo-culted to cases where it is not needed. I take it that the code for the spin-table is not in RAM, and does not need to be protected similarly? Assuming so: Acked-by: Mark Rutland Thanks, Mark. > / { > compatible = "socionext,ph1-ld20"; > #address-cells = <2>; > -- > 1.9.1 > > -- > To unsubscribe from this list: send the line "unsubscribe devicetree" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >