From: Josh Cartwright <joshc@codeaurora.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: [PATCH RFC 0/4] reserved-memory regions/CMA in devicetree, again
Date: Wed, 22 Jan 2014 12:58:48 -0600 [thread overview]
Message-ID: <1390417133-6650-1-git-send-email-joshc@codeaurora.org> (raw)
Hey Marek-
What is the current status of the reserved-memory/CMA device tree support
series? It looks like it's stalled out a bit since the revert[2]. Hopefully
this series is a push in the right direction?
---
This set is an adaptation of Marek's original patchset posted here[1],
and then subsequently reverted here[2]. In [3], Grant proposed a new
set of bindings after discussion in Edinburgh.
This is a partially complete implementation of these proposed bindings.
It's functionality is now split into two pieces, the first of which
implements a default/fallback behavior for reserved-memory nodes; that
is, reserved memory nodes describing fixed-address static regions will
be unconditionally reserved, regardless of their intended use. In
addition, it provides an interface for adding additional reserved-memory
types, using a method similar to CLOCKSOURCE_OF_DECLARE().
The second piece uses the above method to provide support for
reserved-memory nodes whose compatible = "shared-dma-pool". It makes
use of CMA when available, and when a describing node has the 'reusable'
property.
There is basic support for dynamic allocation of memory reserved
regions, however, noticeably missing is support for additional
restrictions (use of alignment and alloc-ranges properties).
[1]: http://lkml.kernel.org/g/1377527959-5080-1-git-send-email-m.szyprowski@samsung.com
[2]: http://lkml.kernel.org/g/1381476448-14548-1-git-send-email-m.szyprowski@samsung.com
[3]: http://lkml.kernel.org/g/20131030134702.19B57C402A0@trevor.secretlab.ca
Grant Likely (1):
of: document bindings for reserved-memory nodes
Josh Cartwright (1):
drivers: of: implement reserved-memory handling for dma
Marek Szyprowski (2):
drivers: of: add initialization code for reserved memory
ARM: init: add support for reserved memory defined by device tree
.../bindings/reserved-memory/reserved-memory.txt | 137 +++++++++++++++
arch/arm/mm/init.c | 3 +
drivers/of/Kconfig | 13 ++
drivers/of/Makefile | 2 +
drivers/of/of_reserved_mem.c | 188 +++++++++++++++++++++
drivers/of/of_reserved_mem_dma.c | 178 +++++++++++++++++++
drivers/of/platform.c | 4 +
include/asm-generic/vmlinux.lds.h | 11 ++
include/linux/of_reserved_mem.h | 61 +++++++
9 files changed, 597 insertions(+)
create mode 100644 Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
create mode 100644 drivers/of/of_reserved_mem.c
create mode 100644 drivers/of/of_reserved_mem_dma.c
create mode 100644 include/linux/of_reserved_mem.h
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next reply other threads:[~2014-01-22 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 18:58 Josh Cartwright [this message]
2014-01-22 18:58 ` [PATCH RFC 1/4] drivers: of: add initialization code for reserved memory Josh Cartwright
2014-01-22 18:58 ` [PATCH RFC 2/4] drivers: of: implement reserved-memory handling for dma Josh Cartwright
2014-01-22 18:58 ` [PATCH RFC 4/4] of: document bindings for reserved-memory nodes Josh Cartwright
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=1390417133-6650-1-git-send-email-joshc@codeaurora.org \
--to=joshc@codeaurora.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robh+dt@kernel.org \
/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).