From: Grant Likely <grant.likely@secretlab.ca>
To: Andrew Morton <akpm@linux-foundation.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <rob.herring@calxeda.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Shawn Guo <shawn.guo@linaro.org>,
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 2/4] misc: Generic on-chip SRAM allocation driver
Date: Mon, 15 Apr 2013 14:50:47 +0100 [thread overview]
Message-ID: <20130415135047.315D43E0AA8@localhost> (raw)
In-Reply-To: <20130327152723.723cd65e884413df405abe2d@linux-foundation.org>
On Wed, 27 Mar 2013 15:27:23 -0700, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Wed, 20 Mar 2013 11:52:45 +0100 Philipp Zabel <p.zabel@pengutronix.de> wrote:
>
> > This driver requests and remaps a memory region as configured in the
> > device tree. It serves memory from this region via the genalloc API.
> > It optionally enables the SRAM clock.
> >
> > Other drivers can retrieve the genalloc pool from a phandle pointing
> > to this drivers' device node in the device tree.
> >
> > The allocation granularity is hard-coded to 32 bytes for now,
> > to make the SRAM driver useful for the 6502 remoteproc driver.
> > There is overhead for bigger SRAMs, where only a much coarser
> > allocation granularity is needed: At 32 bytes minimum allocation
> > size, a 256 KiB SRAM needs a 1 KiB bitmap to track allocations.
> >
> > Documentation/devicetree/bindings/misc/sram.txt | 16 +++
> > drivers/misc/Kconfig | 9 ++
> > drivers/misc/Makefile | 1 +
> > drivers/misc/sram.c | 121 +++++++++++++++++++++++
>
> drivers/misc/sram.c is a pretty generic-sounding thing. Is it really
> Linux's One True SRAM driver? How many different sorts of sram devices
> do we expect this can be used with? If I don't use DT?
>
> In other words, perhaps this should have a more specific and accurate
> name?
Well, it is SRAM. Not a whole lot of variation there, and all the driver
does is allow bits of it to be carved up so that multiple device drivers
don't step on each other's toes. I think that is pretty generic. If
some SRAM comes along that is sufficiently different that it requires a
different driver, then I'm pretty confident saying it would be the
oddball, not this driver, and so would need the more specific name.
All the users at the moment are DT platforms. When a non-DT user comes
along, it won't be a problem to add a non-DT binding. In the mean time I
wouldn't borrow trouble about it.
g.
next prev parent reply other threads:[~2013-04-15 13:50 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 [this message]
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
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=20130415135047.315D43E0AA8@localhost \
--to=grant.likely@secretlab.ca \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dong.aisheng@linaro.org \
--cc=fabio.estevam@freescale.com \
--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=p.zabel@pengutronix.de \
--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).