From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: f.fainelli@gmail.com, Saenz Julienne <nsaenzjulienne@suse.de>,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>
Cc: phil@raspberrypi.com, wahrenst@gmx.net, linux-kernel@vger.kernel.org
Subject: [RFC/PATCH 09/11] ARM: dts: bcm2711: Enable V3D
Date: Fri, 5 Feb 2021 14:52:45 +0100 [thread overview]
Message-ID: <20210205135249.2924-10-nsaenzjulienne@suse.de> (raw)
In-Reply-To: <20210205135249.2924-1-nsaenzjulienne@suse.de>
This enables V3D for bcm2711 (used in the Raspberry Pi 4).
Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
---
arch/arm/boot/dts/bcm2711.dtsi | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/bcm2711.dtsi b/arch/arm/boot/dts/bcm2711.dtsi
index 537498a93a3a..dd8376f474db 100644
--- a/arch/arm/boot/dts/bcm2711.dtsi
+++ b/arch/arm/boot/dts/bcm2711.dtsi
@@ -548,6 +548,18 @@ genet_mdio: mdio@e14 {
#size-cells = <0x1>;
};
};
+
+ v3d: gpu@7ec04000 {
+ compatible = "brcm,bcm2711-v3d";
+ reg = <0x0 0x7ec00000 0x4000>,
+ <0x0 0x7ec04000 0x4000>;
+ reg-names = "hub", "core0";
+
+ power-domains = <&pm BCM2835_POWER_DOMAIN_GRAFX_V3D>;
+ resets = <&pm BCM2835_RESET_V3D>;
+ clocks = <&firmware_clocks 5>;
+ interrupts = <GIC_SPI 74 IRQ_TYPE_LEVEL_HIGH>;
+ };
};
};
--
2.30.0
next prev parent reply other threads:[~2021-02-05 15:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 13:52 [RFC/PATCH 00/11] Raspberry PI 4 V3D enablement Nicolas Saenz Julienne
2021-02-05 13:52 ` [RFC/PATCH 01/11] dt-bindings: soc: bcm: bcm2835-pm: Convert bindings to DT schema Nicolas Saenz Julienne
2021-02-06 11:34 ` Stefan Wahren
2021-02-05 13:52 ` [RFC/PATCH 02/11] dt-bindings: soc: bcm: brcm,bcm2835-pm: Add support for bcm2711 Nicolas Saenz Julienne
2021-02-06 11:36 ` Stefan Wahren
2021-02-05 13:52 ` [RFC/PATCH 03/11] ARM: dts: bcm2711: Use proper compatible in PM/Watchdog node Nicolas Saenz Julienne
2021-02-05 13:52 ` [RFC/PATCH 04/11] mfd: bcm2835-pm: Add support for BCM2711 Nicolas Saenz Julienne
2021-02-05 13:52 ` [RFC/PATCH 05/11] soc: bcm: bcm2835-power: Add support for BCM2711's ARSAN ASB Nicolas Saenz Julienne
2021-02-05 16:56 ` Florian Fainelli
2021-02-05 18:30 ` Nicolas Saenz Julienne
2021-02-05 13:52 ` [RFC/PATCH 06/11] soc: bcm: bcm2835-power: Bypass power_on/off() calls Nicolas Saenz Julienne
2021-02-05 13:52 ` [RFC/PATCH 07/11] drm/v3d: Get rid of pm code Nicolas Saenz Julienne
2021-02-05 13:52 ` [RFC/PATCH 08/11] drm/v3d: Add support for bcm2711 Nicolas Saenz Julienne
2021-02-05 13:52 ` Nicolas Saenz Julienne [this message]
2021-02-06 11:50 ` [RFC/PATCH 09/11] ARM: dts: bcm2711: Enable V3D Stefan Wahren
2021-02-05 13:52 ` [RFC/PATCH 10/11] ARM: configs: Enable DRM_V3D Nicolas Saenz Julienne
2021-02-05 13:52 ` [RFC/PATCH 11/11] arm64: config: " Nicolas Saenz Julienne
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=20210205135249.2924-10-nsaenzjulienne@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=phil@raspberrypi.com \
--cc=robh+dt@kernel.org \
--cc=wahrenst@gmx.net \
/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).