From: Lubomir Rintel <lkundrak@v3.sk>
To: Russell King <linux@armlinux.org.uk>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Lubomir Rintel <lkundrak@v3.sk>,
Rob Herring <robh@kernel.org>
Subject: [PATCH v4 1/5] dt-bindings: reserved-memory: Add binding for Armada framebuffer
Date: Wed, 28 Aug 2019 09:59:34 +0200 [thread overview]
Message-ID: <20190828075938.318028-2-lkundrak@v3.sk> (raw)
In-Reply-To: <20190828075938.318028-1-lkundrak@v3.sk>
This is the binding for memory that is set aside for allocation of Marvell
Armada framebuffer objects.
Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
Reviewed-by: Rob Herring <robh@kernel.org>
---
Changes since v2:
- Collected the Reviewed-by tag
Changes since v1:
- Moved from bindings/display/armada/
- Removed the marvell,dove-framebuffer string
- Added to the MAINTAINERS entry
.../marvell,armada-framebuffer.txt | 22 +++++++++++++++++++
MAINTAINERS | 1 +
2 files changed, 23 insertions(+)
create mode 100644 Documentation/devicetree/bindings/reserved-memory/marvell,armada-framebuffer.txt
diff --git a/Documentation/devicetree/bindings/reserved-memory/marvell,armada-framebuffer.txt b/Documentation/devicetree/bindings/reserved-memory/marvell,armada-framebuffer.txt
new file mode 100644
index 0000000000000..ab243e2bad454
--- /dev/null
+++ b/Documentation/devicetree/bindings/reserved-memory/marvell,armada-framebuffer.txt
@@ -0,0 +1,22 @@
+Marvell Armada framebuffer reserved memory
+==========================================
+
+Memory set aside for allocation of Marvell Armada framebuffer objects.
+
+Required properties:
+
+ - compatible: must be "marvell,armada-framebuffer"
+
+Please refer to Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
+for common reserved memory binding usage.
+
+Example:
+
+ reserved-memory {
+ display_reserved: framebuffer {
+ compatible = "marvell,armada-framebuffer";
+ size = <0x02000000>;
+ alignment = <0x02000000>;
+ no-map;
+ };
+ };
diff --git a/MAINTAINERS b/MAINTAINERS
index 9cbcf167bdd08..3d824ecf96229 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9621,6 +9621,7 @@ T: git git://git.armlinux.org.uk/~rmk/linux-arm.git drm-armada-fixes
F: drivers/gpu/drm/armada/
F: include/uapi/drm/armada_drm.h
F: Documentation/devicetree/bindings/display/armada/
+F: Documentation/devicetree/bindings/reserved-memory/marvell,armada-framebuffer.txt
MARVELL ARMADA 3700 PHY DRIVERS
M: Miquel Raynal <miquel.raynal@bootlin.com>
--
2.21.0
next prev parent reply other threads:[~2019-08-28 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 7:59 [PATCH v4 0/5] dt-bindings: improve the Armada DRM bindings Lubomir Rintel
2019-08-28 7:59 ` Lubomir Rintel [this message]
2019-08-28 7:59 ` [PATCH v4 2/5] dt-bindings: display: armada: Rename the binding doc file Lubomir Rintel
2019-08-28 7:59 ` [PATCH v4 3/5] dt-bindings: display: armada: Improve the LCDC documentation Lubomir Rintel
2019-08-28 7:59 ` [PATCH v4 4/5] dt-bindings: display: armada: Add more compatible strings Lubomir Rintel
2019-08-28 7:59 ` [PATCH v4 5/5] dt-bindings: display: armada: Document bus-width property Lubomir Rintel
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=20190828075938.318028-2-lkundrak@v3.sk \
--to=lkundrak@v3.sk \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=robh@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).