From: Philipp Zabel <p.zabel@pengutronix.de>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Huang Shijie <shijie8@gmail.com>,
Dong Aisheng <dong.aisheng@linaro.org>,
Matt Porter <mporter@ti.com>,
Fabio Estevam <fabio.estevam@freescale.com>,
Javier Martin <javier.martin@vista-silicon.com>,
kernel@pengutronix.de, devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH v9 RESEND 4/4] ARM: dts: add sram for imx53 and imx6q
Date: Thu, 28 Mar 2013 16:23:06 +0100 [thread overview]
Message-ID: <1364484186.4018.66.camel@pizza.hi.pengutronix.de> (raw)
In-Reply-To: <20130328142106.GA699@S2101-09.ap.freescale.net>
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
next prev parent reply other threads:[~2013-03-28 15:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 10:52 [PATCH v9 RESEND 0/4] Add generic driver for on-chip SRAM Philipp Zabel
2013-03-20 10:52 ` [PATCH v9 RESEND 1/4] genalloc: add devres support, allow to find a managed pool by device Philipp Zabel
2013-03-22 12:47 ` Michal Simek
[not found] ` <1363776767-2635-1-git-send-email-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-03-20 10:52 ` [PATCH v9 RESEND 2/4] misc: Generic on-chip SRAM allocation driver Philipp Zabel
2013-03-22 12:47 ` Michal Simek
2013-03-27 22:27 ` Andrew Morton
2013-03-28 7:42 ` Michal Simek
2013-03-28 10:52 ` Philipp Zabel
2013-04-15 13:50 ` Grant Likely
2013-03-20 10:52 ` [PATCH v9 RESEND 3/4] media: coda: use genalloc API Philipp Zabel
2013-03-28 1:15 ` Shawn Guo
2013-03-20 10:52 ` [PATCH v9 RESEND 4/4] ARM: dts: add sram for imx53 and imx6q Philipp Zabel
2013-03-27 22:29 ` Andrew Morton
2013-03-28 1:16 ` Shawn Guo
2013-03-28 2:54 ` Shawn Guo
2013-03-28 9:05 ` Philipp Zabel
2013-03-28 14:22 ` Shawn Guo
2013-03-28 15:23 ` Philipp Zabel [this message]
2013-03-22 12:49 ` [PATCH v9 RESEND 0/4] Add generic driver for on-chip SRAM Michal Simek
2013-03-27 8:33 ` Philipp Zabel
2013-03-27 12:00 ` Shawn Guo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1364484186.4018.66.camel@pizza.hi.pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=arnd@arndb.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dong.aisheng@linaro.org \
--cc=fabio.estevam@freescale.com \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=javier.martin@vista-silicon.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@ti.com \
--cc=paul.gortmaker@windriver.com \
--cc=rob.herring@calxeda.com \
--cc=shawn.guo@linaro.org \
--cc=shijie8@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).