From: Dinh Nguyen <dinguyen@altera.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-kernel@vger.kernel.org,
Fabio Estevam <fabio.estevam@freescale.com>,
Matt Porter <mporter@ti.com>,
Dong Aisheng <dong.aisheng@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devicetree-discuss@lists.ozlabs.org,
Rob Herring <rob.herring@calxeda.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Richard Zhao <richard.zhao@freescale.com>,
Javier Martin <javier.martin@vista-silicon.com>,
kernel@pengutronix.de, Huang Shijie <shijie8@gmail.com>
Subject: Re: [PATCH v9 0/4] Add generic driver for on-chip SRAM
Date: Thu, 28 Feb 2013 09:51:58 -0600 [thread overview]
Message-ID: <1362066718.20662.2.camel@linux-builds1> (raw)
In-Reply-To: <1360770402-23091-1-git-send-email-p.zabel@pengutronix.de>
Hi Philipp,
On Wed, 2013-02-13 at 16:46 +0100, Philipp Zabel wrote:
> These patches add support to configure on-chip SRAM via device-tree
> node or platform data and to obtain the resulting genalloc pool from
> the struct device pointer or a phandle pointing at the device tree node.
> This allows drivers to allocate SRAM with the genalloc API without
> hard-coding the genalloc pool pointer.
>
> The on-chip SRAM on i.MX53 and i.MX6q can be registered via device tree
> and changed to use the simple generic SRAM driver:
>
> ocram: ocram@00900000 {
> compatible = "fsl,imx-ocram", "mmio-sram";
> reg = <0x00900000 0x3f000>;
> };
>
> A driver that needs to allocate SRAM buffers, like the video processing
> unit on i.MX53, can retrieve the genalloc pool from a phandle in the
> device tree using of_get_named_gen_pool(node, "iram", 0) from patch 1:
>
> vpu@63ff4000 {
> /* ... */
> iram = <&ocram>;
> };
>
> Changes since v8:
> - The sram driver now matches against the "mmio-sram" compatible string.
> - Removed a whitespace error in the device tree binding documentation.
>
> regards
> Philipp
>
> ---
> Documentation/devicetree/bindings/media/coda.txt | 30 ++++++
> Documentation/devicetree/bindings/misc/sram.txt | 16 +++
> arch/arm/boot/dts/imx53.dtsi | 5 +
> arch/arm/boot/dts/imx6q.dtsi | 6 ++
> drivers/media/platform/Kconfig | 1 -
> drivers/media/platform/coda.c | 45 +++++---
> drivers/misc/Kconfig | 9 ++
> drivers/misc/Makefile | 1 +
> drivers/misc/sram.c | 121 ++++++++++++++++++++++
> include/linux/genalloc.h | 15 +++
> include/linux/platform_data/coda.h | 18 ++++
> lib/genalloc.c | 81 +++++++++++++++
> 12 files changed, 333 insertions(+), 15 deletions(-)
>
Sorry the late comment, with this patch I think you can probably remove:
linux/platform_data/imx-iram.himx-iram.h
mach-imx/iram_alloc.c
I don't see any usage of iram_init except for coda.
Dinh
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss
>
prev parent reply other threads:[~2013-02-28 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 15:46 [PATCH v9 0/4] Add generic driver for on-chip SRAM Philipp Zabel
2013-02-13 15:46 ` [PATCH v9 1/4] genalloc: add devres support, allow to find a managed pool by device Philipp Zabel
2013-02-13 15:46 ` [PATCH v9 2/4] misc: Generic on-chip SRAM allocation driver Philipp Zabel
[not found] ` <1360770402-23091-1-git-send-email-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-02-13 15:46 ` [PATCH v9 3/4] media: coda: use genalloc API Philipp Zabel
2013-02-13 15:46 ` [PATCH v9 4/4] ARM: dts: add sram for imx53 and imx6q Philipp Zabel
2013-02-17 8:08 ` Shawn Guo
2013-02-28 15:51 ` Dinh Nguyen [this message]
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=1362066718.20662.2.camel@linux-builds1 \
--to=dinguyen@altera.com \
--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=richard.zhao@freescale.com \
--cc=rob.herring@calxeda.com \
--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).