From: Ezequiel Garcia <ezequiel@collabora.com>
To: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-rockchip@lists.infradead.org
Cc: Hans Verkuil <hans.verkuil@cisco.com>,
kernel@collabora.com,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Tomasz Figa <tfiga@chromium.org>,
Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Miouyouyou <myy@miouyouyou.fr>,
Ezequiel Garcia <ezequiel@collabora.com>
Subject: [PATCH v7 3/6] arm64: dts: rockchip: add VPU device node for RK3399
Date: Thu, 4 Oct 2018 21:12:23 -0300 [thread overview]
Message-ID: <20181005001226.12789-4-ezequiel@collabora.com> (raw)
In-Reply-To: <20181005001226.12789-1-ezequiel@collabora.com>
Add the Video Processing Unit node for the RK3399 SoC.
Also, fix the VPU IOMMU node, which was disabled and lacking
its power domain property.
Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com>
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
index c88e603396f6..5efb124e5c3a 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
@@ -1198,6 +1198,18 @@
status = "disabled";
};
+ vpu: video-codec@ff650000 {
+ compatible = "rockchip,rk3399-vpu";
+ reg = <0x0 0xff650000 0x0 0x800>;
+ interrupts = <GIC_SPI 114 IRQ_TYPE_LEVEL_HIGH 0>,
+ <GIC_SPI 113 IRQ_TYPE_LEVEL_HIGH 0>;
+ interrupt-names = "vepu", "vdpu";
+ clocks = <&cru ACLK_VCODEC>, <&cru HCLK_VCODEC>;
+ clock-names = "aclk", "hclk";
+ power-domains = <&power RK3399_PD_VCODEC>;
+ iommus = <&vpu_mmu>;
+ };
+
vpu_mmu: iommu@ff650800 {
compatible = "rockchip,iommu";
reg = <0x0 0xff650800 0x0 0x40>;
@@ -1205,8 +1217,8 @@
interrupt-names = "vpu_mmu";
clocks = <&cru ACLK_VCODEC>, <&cru HCLK_VCODEC>;
clock-names = "aclk", "iface";
+ power-domains = <&power RK3399_PD_VCODEC>;
#iommu-cells = <0>;
- status = "disabled";
};
vdec_mmu: iommu@ff660480 {
--
2.19.0.rc2
next prev parent reply other threads:[~2018-10-05 7:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 0:12 [PATCH v7 0/6] Add Rockchip VPU JPEG encoder Ezequiel Garcia
2018-10-05 0:12 ` [PATCH v7 1/6] dt-bindings: Document the Rockchip VPU bindings Ezequiel Garcia
2018-10-05 0:12 ` [PATCH v7 2/6] ARM: dts: rockchip: add VPU device node for RK3288 Ezequiel Garcia
2018-10-05 12:04 ` Heiko Stuebner
2018-10-17 13:09 ` Heiko Stuebner
2018-10-05 0:12 ` Ezequiel Garcia [this message]
2018-10-05 12:04 ` [PATCH v7 3/6] arm64: dts: rockchip: add VPU device node for RK3399 Heiko Stuebner
2018-10-05 0:12 ` [PATCH v7 4/6] media: Add JPEG_RAW format Ezequiel Garcia
2018-10-05 11:09 ` Mauro Carvalho Chehab
2018-10-05 11:53 ` Ezequiel Garcia
2018-10-05 12:20 ` Mauro Carvalho Chehab
2018-10-05 0:12 ` [PATCH v7 5/6] media: Add controls for JPEG quantization tables Ezequiel Garcia
2018-10-05 0:12 ` [PATCH v7 6/6] media: add Rockchip VPU JPEG encoder driver Ezequiel Garcia
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=20181005001226.12789-4-ezequiel@collabora.com \
--to=ezequiel@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=hans.verkuil@cisco.com \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=myy@miouyouyou.fr \
--cc=nicolas.dufresne@collabora.com \
--cc=robh+dt@kernel.org \
--cc=tfiga@chromium.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