Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752011AbeAJUTi (ORCPT + 1 other); Wed, 10 Jan 2018 15:19:38 -0500 Received: from gate2.alliedtelesis.co.nz ([202.36.163.20]:53987 "EHLO gate2.alliedtelesis.co.nz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751779AbeAJUTd (ORCPT ); Wed, 10 Jan 2018 15:19:33 -0500 From: Chris Packham To: Gregory CLEMENT CC: "jlu@pengutronix.de" , "linux@armlinux.org.uk" , "bp@alien8.de" , "linux-arm-kernel@lists.infradead.org" , "linux-edac@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Jason Cooper , "Andrew Lunn" , Sebastian Hesselbarth , Rob Herring , "Mark Rutland" , "devicetree@vger.kernel.org" Subject: Re: [PATCH 2/3] ARM: dts: mvebu: add sdram controller node to Armada-38x Thread-Topic: [PATCH 2/3] ARM: dts: mvebu: add sdram controller node to Armada-38x Thread-Index: AQHTie1uQDIML3Ip8U6UIXhV+Wghtg== Date: Wed, 10 Jan 2018 20:19:30 +0000 Message-ID: <5aa9a523e86e4607a14265790d105168@svr-chch-ex1.atlnz.lc> References: <20180108223158.21930-1-chris.packham@alliedtelesis.co.nz> <20180108223158.21930-3-chris.packham@alliedtelesis.co.nz> <87tvvu6ro6.fsf@free-electrons.com> Accept-Language: en-NZ, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [2001:df5:b000:22:3a2c:4aff:fe70:2b02] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On 10/01/18 21:31, Gregory CLEMENT wrote: > Hi Chris, > > On mar., janv. 09 2018, Chris Packham wrote: > >> The Armada-38x uses an SDRAM controller that is compatible with the >> Armada-XP. The key difference is the width of the bus (XP is 64/32, 38x >> is 32/16). The SDRAM controller registers are the same between the two >> SoCs. >> >> Signed-off-by: Chris Packham >> --- >> arch/arm/boot/dts/armada-38x.dtsi | 5 +++++ >> 1 file changed, 5 insertions(+) >> >> diff --git a/arch/arm/boot/dts/armada-38x.dtsi b/arch/arm/boot/dts/armada-38x.dtsi >> index 00ff549d4e39..6d34c5ec178f 100644 >> --- a/arch/arm/boot/dts/armada-38x.dtsi >> +++ b/arch/arm/boot/dts/armada-38x.dtsi >> @@ -138,6 +138,11 @@ >> #size-cells = <1>; >> ranges = <0 MBUS_ID(0xf0, 0x01) 0 0x100000>; >> >> + sdramc@1400 { > > Could you add a label? Thanks to this it would be possible to > enable/disable it at board level in a esay way. > Sure. Any suggestions for a name better than "sdramc:"? It's probably worth adding the same label to armada-xp.dtsi and armada-xp-98dx3236.dtsi. >> + compatible = "marvell,armada-xp-sdram-controller"; >> + reg = <0x1400 0x500>; > > What about adding status = "disabled" ? > > Thanks to this we can enable it at board level only if we really want > it, it would avoid nasty regression on boards that don't need it, if an > issue occurs. Unless you are sure that it is completely safe to enable > it for everyone. The EDAC driver (which is default n) will not probe the device if ECC has not been enabled so that should be safe. Other than the EDAC driver the only other code that looks at this is in arch/arm/mach-mvebu/pm.c and it almost seems like an omission that this code is not active on armada-38x. The armada-38x platforms I have access to don't use suspend/resume so I can't verify this.