From: Philipp Zabel <p.zabel@pengutronix.de>
To: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Shawn Guo <shawn.guo@linaro.org>,
Richard Zhao <richard.zhao@freescale.com>,
Huang Shijie <shijie8@gmail.com>,
Dong Aisheng <dong.aisheng@linaro.org>,
kernel@pengutronix.de
Subject: [PATCH 0/5] Add device tree support for on-chip SRAM
Date: Fri, 24 Aug 2012 11:17:41 +0200 [thread overview]
Message-ID: <1345799866-19876-1-git-send-email-p.zabel@pengutronix.de> (raw)
These patches add support to configure the on-chip SRAM via device-tree
node and to obtain the resulting genalloc pool from a phandle pointing
at the node.
This allows drivers to allocate SRAM with the genalloc API without
hard-coding the genalloc pool address.
regards
Philipp
---
arch/arm/boot/dts/imx53.dtsi | 5 ++
arch/arm/boot/dts/imx6q.dtsi | 5 ++
arch/arm/plat-mxc/include/mach/iram.h | 41 -----------------
arch/arm/plat-mxc/iram_alloc.c | 81 ++++++++++++++++++++-------------
include/linux/genalloc.h | 14 ++++++
lib/genalloc.c | 77 +++++++++++++++++++++++++++++++
6 files changed, 150 insertions(+), 73 deletions(-)
next reply other threads:[~2012-08-24 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 9:17 Philipp Zabel [this message]
2012-08-24 9:17 ` [PATCH 1/5] ARM i.MX: Switch IRAM allocator to device tree initialization Philipp Zabel
2012-08-24 9:17 ` [PATCH 2/5] ARM i.MX53, i.MX6q: Add IRAM to device tree Philipp Zabel
2012-08-24 9:17 ` [PATCH 3/5] iram_alloc: store the virt and phys mem address in gen_pool chunks Philipp Zabel
2012-08-24 9:17 ` [PATCH 4/5] genalloc: add a global pool list, allow to find pools by phys address Philipp Zabel
2012-08-24 9:17 ` [PATCH 5/5] ARM i.MX: Remove iram_alloc/free, as they are unused in-tree Philipp Zabel
2012-08-24 14:16 ` [PATCH 0/5] Add device tree support for on-chip SRAM 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=1345799866-19876-1-git-send-email-p.zabel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=dong.aisheng@linaro.org \
--cc=grant.likely@secretlab.ca \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=richard.zhao@freescale.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).