From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: "David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
letux-kernel@openphoenux.org, kernel@pyra-handheld.com,
"H. Nikolaus Schaller" <hns@goldelico.com>
Subject: [PATCH 4/7] ARM: DTS: omap3: add sgx gpu child node
Date: Fri, 18 Oct 2019 20:46:27 +0200 [thread overview]
Message-ID: <ebc994aa9e1a5669c2c79a8452562eae10419291.1571424390.git.hns@goldelico.com> (raw)
In-Reply-To: <cover.1571424390.git.hns@goldelico.com>
and add timer and interrupt
Tested on OpenPandora 600 MHz.
Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com>
---
arch/arm/boot/dts/omap34xx.dtsi | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/arch/arm/boot/dts/omap34xx.dtsi b/arch/arm/boot/dts/omap34xx.dtsi
index 7b09cbee8bb8..28d5c77d6d6c 100644
--- a/arch/arm/boot/dts/omap34xx.dtsi
+++ b/arch/arm/boot/dts/omap34xx.dtsi
@@ -111,7 +111,7 @@
* are also different clocks, but we do not have any dts users
* for it.
*/
- sgx_module: target-module@50000000 {
+ target-module@50000000 {
compatible = "ti,sysc-omap2", "ti,sysc";
reg = <0x50000014 0x4>;
reg-names = "rev";
@@ -121,10 +121,13 @@
#size-cells = <1>;
ranges = <0 0x50000000 0x4000>;
- /*
- * Closed source PowerVR driver, no child device
- * binding or driver in mainline
- */
+ sgx: sgx@0 {
+ compatible = "img,sgx530-121", "img,sgx530", "ti,omap-omap3-sgx530-121";
+ reg = <0x0 0x4000>; /* 64kB */
+ reg-names = "sgx";
+ interrupts = <21>;
+ timer = <&timer11>;
+ };
};
};
--
2.19.1
next prev parent reply other threads:[~2019-10-18 18:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 18:46 [PATCH 0/7] ARM: DTS: OMAP: add child nodes describing the PVRSGX present in some OMAP SoC H. Nikolaus Schaller
2019-10-18 18:46 ` [PATCH 1/7] dt-bindings: gpu: pvrsgx: add initial bindings H. Nikolaus Schaller
2019-10-21 15:07 ` Rob Herring
2019-10-21 15:45 ` H. Nikolaus Schaller
2019-10-21 17:10 ` Tony Lindgren
2019-10-21 17:25 ` Tony Lindgren
2019-10-21 18:07 ` H. Nikolaus Schaller
2019-10-22 15:02 ` Tony Lindgren
2019-10-22 15:11 ` H. Nikolaus Schaller
2019-10-22 15:36 ` Tony Lindgren
2019-10-22 16:14 ` H. Nikolaus Schaller
2019-10-30 16:16 ` Tony Lindgren
2019-10-30 16:39 ` H. Nikolaus Schaller
2019-10-18 18:46 ` [PATCH 2/7] ARM: DTS: am33xx: add sgx gpu child node H. Nikolaus Schaller
2019-10-18 18:46 ` [PATCH 3/7] ARM: DTS: am3517: " H. Nikolaus Schaller
2019-10-18 18:46 ` H. Nikolaus Schaller [this message]
2019-10-18 18:46 ` [PATCH 5/7] ARM: DTS: omap36xx: " H. Nikolaus Schaller
2019-10-18 18:46 ` [PATCH 6/7] ARM: DTS: omap4: " H. Nikolaus Schaller
2019-10-18 18:46 ` [PATCH 7/7] ARM: DTS: omap5: " H. Nikolaus Schaller
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=ebc994aa9e1a5669c2c79a8452562eae10419291.1571424390.git.hns@goldelico.com \
--to=hns@goldelico.com \
--cc=airlied@linux.ie \
--cc=bcousson@baylibre.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@pyra-handheld.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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).