From: Laura Abbott <labbott@redhat.com>
To: Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
Andrew Andrianov <andrew@ncrmnt.org>,
arve@android.com, Riley Andrews <riandrews@android.com>
Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>, Tom Gall <tom.gall@linaro.org>,
romlem@google.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, Colin Cross <ccross@google.com>,
Bryan Huntsman <bryanh@codeaurora.org>,
John Stultz <john.stultz@linaro.org>,
Chen Feng <puck.chen@hisilicon.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 1/3] devicetree: bindings for Ion
Date: Tue, 30 Aug 2016 17:04:27 -0700 [thread overview]
Message-ID: <1472601869-19469-2-git-send-email-labbott@redhat.com> (raw)
In-Reply-To: <1472601869-19469-1-git-send-email-labbott@redhat.com>
This adds a base set of devicetree bindings for the Ion memory
manager. This supports setting up the generic set of heaps and
their properties.
Signed-off-by: Laura Abbott <labbott@redhat.com>
---
drivers/staging/android/ion/devicetree.txt | 51 ++++++++++++++++++++++++++++++
1 file changed, 51 insertions(+)
create mode 100644 drivers/staging/android/ion/devicetree.txt
diff --git a/drivers/staging/android/ion/devicetree.txt b/drivers/staging/android/ion/devicetree.txt
new file mode 100644
index 0000000..16871527
--- /dev/null
+++ b/drivers/staging/android/ion/devicetree.txt
@@ -0,0 +1,51 @@
+Ion Memory Manager
+
+Ion is a memory manager that allows for sharing of buffers via dma-buf.
+Ion allows for different types of allocation via an abstraction called
+a 'heap'. A heap represents a specific type of memory. Each heap has
+a different type. There can be multiple instances of the same heap
+type.
+
+Specific heap instances are tied to heap IDs. Heap IDs are not to be specified
+in the devicetree.
+
+Required properties for Ion
+
+- compatible: "linux,ion" PLUS a compatible property for the device
+
+All child nodes of a linux,ion node are interpreted as heaps
+
+required properties for heaps
+
+- compatible: compatible string for a heap type PLUS a compatible property
+for the specific instance of the heap. Current heap types
+-- linux,ion-heap-system
+-- linux,ion-heap-system-contig
+-- linux,ion-heap-carveout
+-- linux,ion-heap-chunk
+-- linux,ion-heap-dma
+-- linux,ion-heap-custom
+
+Optional properties
+- memory-region: A phandle to a memory region. Required for DMA heap type
+(see reserved-memory.txt for details on the reservation)
+
+Example:
+
+ ion {
+ compatbile = "hisilicon,ion", "linux,ion";
+
+ ion-system-heap {
+ compatbile = "hisilicon,system-heap", "linux,ion-heap-system"
+ };
+
+ ion-camera-region {
+ compatible = "hisilicon,camera-heap", "linux,ion-heap-dma"
+ memory-region = <&camera_region>;
+ };
+
+ ion-fb-region {
+ compatbile = "hisilicon,fb-heap", "linux,ion-heap-dma"
+ memory-region = <&fb_region>;
+ };
+ }
--
2.7.4
next prev parent reply other threads:[~2016-08-31 0:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 0:04 [PATCHv3 0/3] Devicetree bindings for Ion Laura Abbott
2016-08-31 0:04 ` Laura Abbott [this message]
2016-09-12 18:57 ` [PATCHv3 1/3] devicetree: " Frank Rowand
2016-08-31 0:04 ` [PATCHv3 2/3] staging: ion: Add files for parsing the devicetree Laura Abbott
2016-08-31 0:04 ` [PATCHv3 3/3] staging: android: ion: Convert hi6220 to common platform Laura Abbott
2016-09-12 10:22 ` [PATCHv3 0/3] Devicetree bindings for Ion Greg Kroah-Hartman
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=1472601869-19469-2-git-send-email-labbott@redhat.com \
--to=labbott@redhat.com \
--cc=andrew@ncrmnt.org \
--cc=arnd@arndb.de \
--cc=arve@android.com \
--cc=bryanh@codeaurora.org \
--cc=ccross@google.com \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=puck.chen@hisilicon.com \
--cc=riandrews@android.com \
--cc=robh+dt@kernel.org \
--cc=romlem@google.com \
--cc=sumit.semwal@linaro.org \
--cc=tom.gall@linaro.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).