From: Daoyuan Huang <daoyuan.huang@mediatek.com>
To: <hans.verkuil@cisco.com>,
<laurent.pinchart+renesas@ideasonboard.com>, <tfiga@chromium.org>,
<matthias.bgg@gmail.com>, <mchehab@kernel.org>
Cc: devicetree@vger.kernel.org, Sean.Cheng@mediatek.com,
Rynn.Wu@mediatek.com, srv_heupstream@mediatek.com,
daoyuan huang <daoyuan.huang@mediatek.com>,
holmes.chiou@mediatek.com, Jerry-ch.Chen@mediatek.com,
jungo.lin@mediatek.com, sj.huang@mediatek.com,
yuzhao@chromium.org, linux-mediatek@lists.infradead.org,
Ping-Hsun Wu <ping-hsun.wu@mediatek.com>,
zwisler@chromium.org, christie.yu@mediatek.com,
frederic.chen@mediatek.com, linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: [RFC v2 1/4] dt-binding: mt8183: Add Mediatek MDP3 dt-bindings
Date: Thu, 16 May 2019 11:23:29 +0800 [thread overview]
Message-ID: <20190516032332.56844-2-daoyuan.huang@mediatek.com> (raw)
In-Reply-To: <20190516032332.56844-1-daoyuan.huang@mediatek.com>
From: daoyuan huang <daoyuan.huang@mediatek.com>
This patch adds DT binding document for Media Data Path 3 (MDP3)
a unit in multimedia system used for scaling and color format convert.
Signed-off-by: Ping-Hsun Wu <ping-hsun.wu@mediatek.com>
Signed-off-by: daoyuan huang <daoyuan.huang@mediatek.com>
---
.../bindings/media/mediatek,mt8183-mdp3.txt | 217 ++++++++++++++++++
1 file changed, 217 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/mediatek,mt8183-mdp3.txt
diff --git a/Documentation/devicetree/bindings/media/mediatek,mt8183-mdp3.txt b/Documentation/devicetree/bindings/media/mediatek,mt8183-mdp3.txt
new file mode 100644
index 000000000000..cf3e808b7146
--- /dev/null
+++ b/Documentation/devicetree/bindings/media/mediatek,mt8183-mdp3.txt
@@ -0,0 +1,217 @@
+* Mediatek Media Data Path 3
+
+Media Data Path 3 (MDP3) is used for scaling and color space conversion.
+
+Required properties (controller node):
+- compatible: "mediatek,mt8183-mdp"
+- mediatek,scp: the node of system control processor (SCP), using the
+ remoteproc & rpmsg framework, see
+ Documentation/devicetree/bindings/remoteproc/mtk,scp.txt for details.
+- mediatek,mmsys: the node of mux(multiplexer) controller for HW connections.
+- mediatek,mm-mutex: the node of sof(start of frame) signal controller.
+- mediatek,mailbox-gce: the node of global command engine (GCE), used to
+ read/write registers with critical time limitation, see
+ Documentation/devicetree/bindings/mailbox/mtk-gce.txt for details.
+- mboxes: mailbox number used to communicate with GCE.
+- gce-subsys: sub-system id corresponding to the register address.
+- gce-event-names: in use event name list, used to correspond to event IDs.
+- gce-events: in use event IDs list, all IDs are defined in
+ 'dt-bindings/gce/mt8183-gce.h'.
+
+Required properties (all function blocks, child node):
+- compatible: Should be one of
+ "mediatek,mt8183-mdp-rdma" - read DMA
+ "mediatek,mt8183-mdp-rsz" - resizer
+ "mediatek,mt8183-mdp-wdma" - write DMA
+ "mediatek,mt8183-mdp-wrot" - write DMA with rotation
+ "mediatek,mt8183-mdp-ccorr" - color correction with 3X3 matrix
+- reg: Physical base address and length of the function block register space
+- clocks: device clocks, see
+ Documentation/devicetree/bindings/clock/clock-bindings.txt for details.
+- power-domains: a phandle to the power domain, see
+ Documentation/devicetree/bindings/power/power_domain.txt for details.
+- mediatek,mdp-id: HW index to distinguish same functionality modules.
+
+Required properties (DMA function blocks, child node):
+- compatible: Should be one of
+ "mediatek,mt8183-mdp-rdma"
+ "mediatek,mt8183-mdp-wdma"
+ "mediatek,mt8183-mdp-wrot"
+- iommus: should point to the respective IOMMU block with master port as
+ argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
+ for details.
+- mediatek,larb: must contain the local arbiters in the current Socs, see
+ Documentation/devicetree/bindings/memory-controllers/mediatek,smi-larb.txt
+ for details.
+
+Required properties (input path selection node):
+- compatible:
+ "mediatek,mt8183-mdp-dl" - MDP direct link input source selection
+- reg: Physical base address and length of the function block register space
+- clocks: device clocks, see
+ Documentation/devicetree/bindings/clock/clock-bindings.txt for details.
+- mediatek,mdp-id: HW index to distinguish same functionality modules.
+
+Required properties (ISP PASS2 (DIP) module path selection node):
+- compatible:
+ "mediatek,mt8183-mdp-imgi" - input DMA of ISP PASS2 (DIP) module for raw image input
+- reg: Physical base address and length of the function block register space
+- mediatek,mdp-id: HW index to distinguish same functionality modules.
+
+Required properties (SW node):
+- compatible: Should be one of
+ "mediatek,mt8183-mdp-exto" - output DMA of ISP PASS2 (DIP) module for yuv image output
+ "mediatek,mt8183-mdp-path" - MDP output path selection
+- mediatek,mdp-id: HW index to distinguish same functionality modules.
+
+Example:
+ mdp_camin@14000000 {
+ compatible = "mediatek,mt8183-mdp-dl";
+ mediatek,mdp-id = <0>;
+ reg = <0 0x14000000 0 0x1000>;
+ clocks = <&mmsys CLK_MM_MDP_DL_TXCK>,
+ <&mmsys CLK_MM_MDP_DL_RX>;
+ };
+
+ mdp_camin2@14000000 {
+ compatible = "mediatek,mt8183-mdp-dl";
+ mediatek,mdp-id = <1>;
+ reg = <0 0x14000000 0 0x1000>;
+ clocks = <&mmsys CLK_MM_IPU_DL_TXCK>,
+ <&mmsys CLK_MM_IPU_DL_RX>;
+ };
+
+ mdp_rdma0: mdp_rdma0@14001000 {
+ compatible = "mediatek,mt8183-mdp-rdma", "mediatek,mt8183-mdp3";
+ mediatek,scp = <&scp>;
+ mediatek,mdp-id = <0>;
+ reg = <0 0x14001000 0 0x1000>;
+ power-domains = <&scpsys MT8183_POWER_DOMAIN_DISP>;
+ clocks = <&mmsys CLK_MM_MDP_RDMA0>,
+ <&mmsys CLK_MM_MDP_RSZ1>;
+ iommus = <&iommu M4U_PORT_MDP_RDMA0>;
+ mediatek,larb = <&larb0>;
+ mediatek,mmsys = <&mmsys>;
+ mediatek,mm-mutex = <&mutex>;
+ mediatek,mailbox-gce = <&gce>;
+ mboxes = <&gce 20 0 CMDQ_THR_PRIO_LOWEST>,
+ <&gce 21 0 CMDQ_THR_PRIO_LOWEST>,
+ <&gce 22 0 CMDQ_THR_PRIO_LOWEST>,
+ <&gce 23 0 CMDQ_THR_PRIO_LOWEST>;
+ gce-subsys = <&gce 0x14000000 SUBSYS_1400XXXX>,
+ <&gce 0x14010000 SUBSYS_1401XXXX>,
+ <&gce 0x14020000 SUBSYS_1402XXXX>,
+ <&gce 0x15020000 SUBSYS_1502XXXX>;
+ gce-event-names = "rdma0_sof",
+ "rsz0_sof",
+ "rsz1_sof",
+ "tdshp0_sof",
+ "wrot0_sof",
+ "wdma0_sof",
+ "rdma0_done",
+ "wrot0_done",
+ "wdma0_done",
+ "isp_p2_0_done",
+ "isp_p2_1_done",
+ "isp_p2_2_done",
+ "isp_p2_3_done",
+ "isp_p2_4_done",
+ "isp_p2_5_done",
+ "isp_p2_6_done",
+ "isp_p2_7_done",
+ "isp_p2_8_done",
+ "isp_p2_9_done",
+ "isp_p2_10_done",
+ "isp_p2_11_done",
+ "isp_p2_12_done",
+ "isp_p2_13_done",
+ "isp_p2_14_done",
+ "wpe_done",
+ "wpe_b_done";
+ gce-events = <&gce CMDQ_EVENT_MDP_RDMA0_SOF>,
+ <&gce CMDQ_EVENT_MDP_RSZ0_SOF>,
+ <&gce CMDQ_EVENT_MDP_RSZ1_SOF>,
+ <&gce CMDQ_EVENT_MDP_TDSHP_SOF>,
+ <&gce CMDQ_EVENT_MDP_WROT0_SOF>,
+ <&gce CMDQ_EVENT_MDP_WDMA0_SOF>,
+ <&gce CMDQ_EVENT_MDP_RDMA0_EOF>,
+ <&gce CMDQ_EVENT_MDP_WROT0_EOF>,
+ <&gce CMDQ_EVENT_MDP_WDMA0_EOF>,
+ <&gce CMDQ_EVENT_ISP_FRAME_DONE_P2_0>,
+ <&gce CMDQ_EVENT_ISP_FRAME_DONE_P2_1>,
+ <&gce CMDQ_EVENT_ISP_FRAME_DONE_P2_2>,
+ <&gce CMDQ_EVENT_ISP_FRAME_DONE_P2_3>,
+ <&gce CMDQ_EVENT_ISP_FRAME_DONE_P2_4>,
+ <&gce CMDQ_EVENT_ISP_FRAME_DONE_P2_5>,
+ <&gce CMDQ_EVENT_ISP_FRAME_DONE_P2_6>,
+ <&gce CMDQ_EVENT_ISP_FRAME_DONE_P2_7>,
+ <&gce CMDQ_EVENT_ISP_FRAME_DONE_P2_8>,
+ <&gce CMDQ_EVENT_ISP_FRAME_DONE_P2_9>,
+ <&gce CMDQ_EVENT_ISP_FRAME_DONE_P2_10>,
+ <&gce CMDQ_EVENT_ISP_FRAME_DONE_P2_11>,
+ <&gce CMDQ_EVENT_ISP_FRAME_DONE_P2_12>,
+ <&gce CMDQ_EVENT_ISP_FRAME_DONE_P2_13>,
+ <&gce CMDQ_EVENT_ISP_FRAME_DONE_P2_14>,
+ <&gce CMDQ_EVENT_WPE_A_DONE>,
+ <&gce CMDQ_EVENT_SPE_B_DONE>;
+ };
+
+ mdp_imgi@15020000 {
+ compatible = "mediatek,mt8183-mdp-imgi";
+ mediatek,mdp-id = <0>;
+ reg = <0 0x15020000 0 0x1000>;
+ };
+
+ mdp_img2o@15020000 {
+ compatible = "mediatek,mt8183-mdp-exto";
+ mediatek,mdp-id = <1>;
+ };
+
+ mdp_rsz0: mdp_rsz0@14003000 {
+ compatible = "mediatek,mt8183-mdp-rsz";
+ mediatek,mdp-id = <0>;
+ reg = <0 0x14003000 0 0x1000>;
+ clocks = <&mmsys CLK_MM_MDP_RSZ0>;
+ };
+
+ mdp_rsz1: mdp_rsz1@14004000 {
+ compatible = "mediatek,mt8183-mdp-rsz";
+ mediatek,mdp-id = <1>;
+ reg = <0 0x14004000 0 0x1000>;
+ clocks = <&mmsys CLK_MM_MDP_RSZ1>;
+ };
+
+ mdp_wrot0: mdp_wrot0@14005000 {
+ compatible = "mediatek,mt8183-mdp-wrot";
+ mediatek,mdp-id = <0>;
+ reg = <0 0x14005000 0 0x1000>;
+ clocks = <&mmsys CLK_MM_MDP_WROT0>;
+ iommus = <&iommu M4U_PORT_MDP_WROT0>;
+ mediatek,larb = <&larb0>;
+ };
+
+ mdp_path0_sout@14005000 {
+ compatible = "mediatek,mt8183-mdp-path";
+ mediatek,mdp-id = <0>;
+ };
+
+ mdp_wdma: mdp_wdma@14006000 {
+ compatible = "mediatek,mt8183-mdp-wdma";
+ mediatek,mdp-id = <0>;
+ reg = <0 0x14006000 0 0x1000>;
+ clocks = <&mmsys CLK_MM_MDP_WDMA0>;
+ iommus = <&iommu M4U_PORT_MDP_WDMA0>;
+ mediatek,larb = <&larb0>;
+ };
+
+ mdp_path1_sout@14006000 {
+ compatible = "mediatek,mt8183-mdp-path";
+ mediatek,mdp-id = <1>;
+ };
+
+ mdp_ccorr: mdp_ccorr@1401c000 {
+ compatible = "mediatek,mt8183-mdp-ccorr";
+ mediatek,mdp-id = <0>;
+ reg = <0 0x1401c000 0 0x1000>;
+ clocks = <&mmsys CLK_MM_MDP_CCORR>;
+ };
--
2.18.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-05-16 3:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 3:23 [RFC v2 0/4] media: mediatek: support mdp3 on mt8183 platform Daoyuan Huang
2019-05-16 3:23 ` Daoyuan Huang [this message]
2019-06-13 21:25 ` [RFC v2 1/4] dt-binding: mt8183: Add Mediatek MDP3 dt-bindings Rob Herring
2019-05-16 3:23 ` [RFC v2 2/4] dts: arm64: mt8183: Add Mediatek MDP3 nodes Daoyuan Huang
2019-05-16 3:23 ` [RFC v2 3/4] media: platform: Add Mediatek MDP3 driver KConfig Daoyuan Huang
[not found] ` <20190516032332.56844-5-daoyuan.huang@mediatek.com>
2019-06-04 11:20 ` [RFC v2 4/4] media: platform: mtk-mdp3: Add Mediatek MDP3 driver Tomasz Figa
2019-06-11 9:20 ` Daoyuan Huang
2019-06-11 10:11 ` Tomasz Figa
2019-06-20 4:48 ` Alexandre Courbot
2019-06-26 4:41 ` Tomasz Figa
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=20190516032332.56844-2-daoyuan.huang@mediatek.com \
--to=daoyuan.huang@mediatek.com \
--cc=Jerry-ch.Chen@mediatek.com \
--cc=Rynn.Wu@mediatek.com \
--cc=Sean.Cheng@mediatek.com \
--cc=christie.yu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=frederic.chen@mediatek.com \
--cc=hans.verkuil@cisco.com \
--cc=holmes.chiou@mediatek.com \
--cc=jungo.lin@mediatek.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=ping-hsun.wu@mediatek.com \
--cc=sj.huang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@chromium.org \
--cc=yuzhao@chromium.org \
--cc=zwisler@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;
as well as URLs for NNTP newsgroup(s).