Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756284Ab3C1PX3 (ORCPT ); Thu, 28 Mar 2013 11:23:29 -0400 Received: from metis.ext.pengutronix.de ([92.198.50.35]:52215 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756116Ab3C1PX2 (ORCPT ); Thu, 28 Mar 2013 11:23:28 -0400 Message-ID: <1364484186.4018.66.camel@pizza.hi.pengutronix.de> Subject: Re: [PATCH v9 RESEND 4/4] ARM: dts: add sram for imx53 and imx6q From: Philipp Zabel To: Shawn Guo Cc: linux-kernel@vger.kernel.org, Arnd Bergmann , Greg Kroah-Hartman , Grant Likely , Rob Herring , Paul Gortmaker , Huang Shijie , Dong Aisheng , Matt Porter , Fabio Estevam , Javier Martin , kernel@pengutronix.de, devicetree-discuss@lists.ozlabs.org Date: Thu, 28 Mar 2013 16:23:06 +0100 In-Reply-To: <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> <20130328142106.GA699@S2101-09.ap.freescale.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4-2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:6f8:1178:2:ca9c:dcff:febd:f1b5 X-SA-Exim-Mail-From: p.zabel@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1076 Lines: 29 Am Donnerstag, den 28.03.2013, 22:22 +0800 schrieb Shawn Guo: > 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. Alright, I'll drop it, then. thanks Philipp -- 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/