Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756300Ab3C1OWV (ORCPT ); Thu, 28 Mar 2013 10:22:21 -0400 Received: from co9ehsobe005.messaging.microsoft.com ([207.46.163.28]:26750 "EHLO co9outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756033Ab3C1OWT (ORCPT ); Thu, 28 Mar 2013 10:22:19 -0400 X-Forefront-Antispam-Report: CIP:70.37.183.190;KIP:(null);UIP:(null);IPV:NLI;H:mail.freescale.net;RD:none;EFVD:NLI X-SpamScore: 1 X-BigFish: VS1(zcb8kz98dI1432Izz1f42h1fc6h1ee6h1de0h1202h1e76h1d1ah1d2ahzzz2dh87h2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1155h) X-FB-DOMAIN-IP-MATCH: fail Date: Thu, 28 Mar 2013 22:22:08 +0800 From: Shawn Guo To: Philipp Zabel CC: , Arnd Bergmann , Greg Kroah-Hartman , Grant Likely , Rob Herring , Paul Gortmaker , Huang Shijie , Dong Aisheng , Matt Porter , Fabio Estevam , Javier Martin , , Subject: Re: [PATCH v9 RESEND 4/4] ARM: dts: add sram for imx53 and imx6q Message-ID: <20130328142106.GA699@S2101-09.ap.freescale.net> References: <1363776767-2635-1-git-send-email-p.zabel@pengutronix.de> <1363776767-2635-5-git-send-email-p.zabel@pengutronix.de> <20130328025422.GH5429@S2101-09.ap.freescale.net> <1364461518.4018.4.camel@pizza.hi.pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <1364461518.4018.4.camel@pizza.hi.pengutronix.de> User-Agent: Mutt/1.5.21 (2010-09-15) X-OriginatorOrg: sigmatel.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 941 Lines: 25 On Thu, Mar 28, 2013 at 10:05:18AM +0100, Philipp Zabel wrote: > > > + > > > + ocram: ocram@f8000000 { > > > + compatible = "fsl,imx-ocram", "mmio-sram"; > > > > We should probably just drop "fsl,imx-ocram". > > > > Shawn > > I thought that in the future somebody might want to implement some i.MX > OCRAM specifics in a different driver, like the L2 cache / OCRAM mode > switching, the timing settings, or the TrustZone bits that are > configurable in the IOMUXC GPR registers. We can add i.MX OCRAM specific compatible when we see that real need. Also, generally we should use a specific chip/osc name rather than "imx" for compatible to specify the particular hardware version. Shawn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/