From: robertcnelson@gmail.com (Robert Nelson)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 3/6] Documentation: dt: add bindings for ti bb2d
Date: Thu, 17 Nov 2016 20:44:33 -0600 [thread overview]
Message-ID: <20161118024436.13447-3-robertcnelson@gmail.com> (raw)
In-Reply-To: <20161118024436.13447-1-robertcnelson@gmail.com>
From: Gowtham Tammana <g-tammana@ti.com>
Add documentation for device tree bindings description for
2D GPU blitter module present in Texas Instruments family of SoCs.
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
---
Documentation/devicetree/bindings/gpu/ti-bb2d.txt | 27 +++++++++++++++++++++++
1 file changed, 27 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpu/ti-bb2d.txt
diff --git a/Documentation/devicetree/bindings/gpu/ti-bb2d.txt b/Documentation/devicetree/bindings/gpu/ti-bb2d.txt
new file mode 100644
index 0000000..af47488
--- /dev/null
+++ b/Documentation/devicetree/bindings/gpu/ti-bb2d.txt
@@ -0,0 +1,27 @@
+* Texas Instruments BB2D blitter module
+
+This binding describes the 2D BitBlit (BB2D) graphics accelerator
+subsystem based on the GC320 core from Vivante Corporation available
+in Texas Instruments SoCs.
+
+Required properties:
+ - compatible: value should take the following format:
+ "ti,<soc>-bb2d", "vivante,<gpuversion>"
+ accepted values:
+ (a) "ti,dra7-bb2d", "vivante,gc320" for TI DRA7xx / AM57x
+
+ - reg : base address and length of BB2D IP registers
+ - interrupts : BB2D interrupt line number
+ - ti,hwmods : name of the hwmod associated with BB2D module
+ - clocks : handle to BB2D functional clock
+ - clock-names : fclk
+
+Example for DRA7x SoC:
+ bb2d: bb2d at 59000000 {
+ compatible = "ti,dra7-bb2d", "vivante,gc320";
+ reg = <0x59000000 0x0700>;
+ interrupts = <GIC_SPI 120 IRQ_TYPE_LEVEL_HIGH>;
+ ti,hwmods = "bb2d";
+ clocks = <&dpll_core_h24x2_ck>;
+ clock-names = "fclk";
+ };
--
2.10.2
next prev parent reply other threads:[~2016-11-18 2:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 2:44 [RFC 1/6] drm/etnaviv: add binding for the gc320 found in ti socs Robert Nelson
2016-11-18 2:44 ` [RFC 2/6] drm/etnaviv: allow building etnaviv on omap devices Robert Nelson
2016-11-18 2:52 ` Nishanth Menon
2016-11-18 16:33 ` Rob Herring
2016-11-19 11:58 ` Joshua Clayton
2016-11-20 11:43 ` Russell King - ARM Linux
2016-11-18 2:44 ` Robert Nelson [this message]
2016-11-18 2:54 ` [RFC 3/6] Documentation: dt: add bindings for ti bb2d Nishanth Menon
2016-11-18 2:44 ` [RFC 4/6] ARM: dts: dra7: add entry for bb2d module Robert Nelson
2016-11-18 10:59 ` Lucas Stach
2016-11-18 13:56 ` Nishanth Menon
2016-11-18 2:44 ` [RFC 5/6] ARM: dts: dra7: add vivante " Robert Nelson
2016-11-18 10:55 ` Lucas Stach
2016-11-18 2:44 ` [RFC 6/6] ARM: dts: am57xx-beagle-x15-common: enable etnaviv Robert Nelson
2016-11-18 2:56 ` Nishanth Menon
2016-11-18 3:44 ` Robert Nelson
2016-11-18 4:15 ` Nishanth Menon
2016-11-18 4:26 ` Robert Nelson
2016-11-18 4:34 ` Nishanth Menon
2016-11-18 16:42 ` Rob Herring
2016-11-18 2:51 ` [RFC 1/6] drm/etnaviv: add binding for the gc320 found in ti socs Robert Nelson
2016-11-18 2:53 ` Nishanth Menon
2016-11-18 12:13 ` Russell King - ARM Linux
2016-11-18 13:34 ` Lucas Stach
2016-11-18 15:07 ` Robert Nelson
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=20161118024436.13447-3-robertcnelson@gmail.com \
--to=robertcnelson@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).