From: Ezequiel Garcia <ezequiel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
To: linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Nicolas Dufresne
<nicolas.dufresne-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>,
Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>,
Tomasz Figa <tfiga-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Hans Verkuil
<hans.verkuil-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
Miouyouyou <myy-tmjzNUIc0P1+EYZtW95mkQ@public.gmane.org>,
kernel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org,
Ezequiel Garcia
<ezequiel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
Subject: [PATCH v6 1/6] dt-bindings: Document the Rockchip VPU bindings
Date: Mon, 17 Sep 2018 14:30:16 -0300 [thread overview]
Message-ID: <20180917173022.9338-2-ezequiel@collabora.com> (raw)
In-Reply-To: <20180917173022.9338-1-ezequiel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
Add devicetree binding documentation for Rockchip Video Processing
Unit IP.
Reviewed-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Signed-off-by: Ezequiel Garcia <ezequiel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
---
.../bindings/media/rockchip-vpu.txt | 30 +++++++++++++++++++
1 file changed, 30 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/rockchip-vpu.txt
diff --git a/Documentation/devicetree/bindings/media/rockchip-vpu.txt b/Documentation/devicetree/bindings/media/rockchip-vpu.txt
new file mode 100644
index 000000000000..5e0d421301ca
--- /dev/null
+++ b/Documentation/devicetree/bindings/media/rockchip-vpu.txt
@@ -0,0 +1,30 @@
+device-tree bindings for rockchip VPU codec
+
+Rockchip (Video Processing Unit) present in various Rockchip platforms,
+such as RK3288 and RK3399.
+
+Required properties:
+- compatible: value should be one of the following
+ "rockchip,rk3288-vpu";
+ "rockchip,rk3399-vpu";
+- interrupts: encoding and decoding interrupt specifiers
+- interrupt-names: should be "vepu" and "vdpu"
+- clocks: phandle to VPU aclk, hclk clocks
+- clock-names: should be "aclk" and "hclk"
+- power-domains: phandle to power domain node
+- iommus: phandle to a iommu node
+
+Example:
+SoC-specific DT entry:
+ vpu: video-codec@ff9a0000 {
+ compatible = "rockchip,rk3288-vpu";
+ reg = <0x0 0xff9a0000 0x0 0x800>;
+ interrupts = <GIC_SPI 9 IRQ_TYPE_LEVEL_HIGH>,
+ <GIC_SPI 10 IRQ_TYPE_LEVEL_HIGH>;
+ interrupt-names = "vepu", "vdpu";
+ clocks = <&cru ACLK_VCODEC>, <&cru HCLK_VCODEC>;
+ clock-names = "aclk", "hclk";
+ power-domains = <&power RK3288_PD_VIDEO>;
+ iommus = <&vpu_mmu>;
+ };
+
--
2.19.0.rc2
next prev parent reply other threads:[~2018-09-17 17:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 17:30 [PATCH v6 0/6] Add Rockchip VPU JPEG encoder Ezequiel Garcia
[not found] ` <20180917173022.9338-1-ezequiel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2018-09-17 17:30 ` Ezequiel Garcia [this message]
[not found] ` <20180917173022.9338-2-ezequiel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2018-09-28 11:53 ` [PATCH v6 1/6] dt-bindings: Document the Rockchip VPU bindings Hans Verkuil
[not found] ` <2184b772-2b40-289f-5537-7ebb693479fd-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
2018-10-04 22:24 ` Ezequiel Garcia
2018-09-17 17:30 ` [PATCH v6 2/6] ARM: dts: rockchip: add VPU device node for RK3288 Ezequiel Garcia
2018-09-17 17:30 ` [PATCH v6 3/6] arm64: dts: rockchip: add VPU device node for RK3399 Ezequiel Garcia
2018-09-17 17:30 ` [PATCH v6 4/6] media: Add JPEG_RAW format Ezequiel Garcia
2018-09-17 17:30 ` [PATCH v6 5/6] media: Add controls for JPEG quantization tables Ezequiel Garcia
2018-09-17 17:30 ` [PATCH v6 6/6] media: add Rockchip VPU JPEG encoder driver Ezequiel Garcia
[not found] ` <20180917173022.9338-7-ezequiel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2018-09-28 11:58 ` Hans Verkuil
2018-09-28 12:33 ` [PATCH v6 0/6] Add Rockchip VPU JPEG encoder Hans Verkuil
[not found] ` <7bd9573e-e0c6-71a6-84ed-deb0904593fd-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
2018-10-01 17:54 ` Ezequiel Garcia
[not found] ` <faca3960d0478610b73071b471acfa26df987985.camel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2018-10-04 23:39 ` Ezequiel Garcia
[not found] ` <5ce82f591ab9bd1a9a0a476f01bbf4f0fe4ab0e2.camel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2018-10-05 12:10 ` Mauro Carvalho Chehab
[not found] ` <20181005091034.7d8399ed-qA1ZUp+OV9c@public.gmane.org>
2018-10-05 15:37 ` Ezequiel Garcia
[not found] ` <25d61645856120ad010b604ec4c14b0677ab9197.camel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2018-10-05 16:49 ` Mauro Carvalho Chehab
[not found] ` <20181005134914.4947841d-qA1ZUp+OV9c@public.gmane.org>
2018-10-05 17:39 ` 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=20180917173022.9338-2-ezequiel@collabora.com \
--to=ezequiel-zgy8ohtn/8qb+jhodadfcq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hans.verkuil-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=kernel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
--cc=linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=myy-tmjzNUIc0P1+EYZtW95mkQ@public.gmane.org \
--cc=nicolas.dufresne-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=tfiga-F7+t8E8rja9g9hUCZPvPmw@public.gmane.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