Message ID | 20230922072116.11009-6-moudy.ho@mediatek.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:612c:172:b0:3f2:4152:657d with SMTP id h50csp5615409vqi; Fri, 22 Sep 2023 07:22:42 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFztN/kBvdpN3VqHjFMGQNjIWDohsG3zxnd6JREP1OO8cODZ05FT5ok3N31Z24kCmoZ8wuF X-Received: by 2002:a17:902:d486:b0:1c4:4a58:ff65 with SMTP id c6-20020a170902d48600b001c44a58ff65mr10096212plg.64.1695392562393; Fri, 22 Sep 2023 07:22:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1695392562; cv=none; d=google.com; s=arc-20160816; b=hBACc4GFOsWfgUpp5iJIri6wdtu1YTQKAuninrkulje4v3jO5aTkge7Y5KmxSI/gNV bTifgdNvK79DgxWI5Ckd+8MNoaS867h+tzUp4mkgf5DZ4XNjlSughFBkRm8LRHWuSGNJ sQ5EwKkZd/r1o83ataT1xA6IS2a5XcYohWtqdoQ6Wo3x3/xrJZbdadUhaPdWqTOQm8o3 lYkmDbbX2gD2dh7wFodbVljGUBLpREMywWEkgCpEq4E7ct7Gm0377PQk51nf5+hgTWky 5IKd46Tn1Rr+EH/Bautif3VmJGPFyD6xRuVf4QFMIrkdjRbB3KdR1CC3AyiKL+qHJM7K HLZA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from:dkim-signature; bh=o9TyNrz3SR4xQQtRCtzAKiPKHJh47LnMYSwL+P8jdFQ=; fh=wJeRWNSZIQvKzTzARBL2sRJoO2hKwpVy82Mig4ni80M=; b=JmXmw5eAhFhQNKD6M+gduJKD4uGZc4alo1mrIZfiQf1vRpsg8/sD3LL+KecwLTa2kY IPwkX1RdTPfP4due5j2hp6QSIbmABhsGpeOiWLHN7SJwc6j4uACcz7rx5Yi+6Yc1WDC5 iuT6n9016cjkd6OysoM64/YfLXTAkLjG77nNb6pxVvL6FLi391YZnPeJEi1JY8vCbpqx 3OU1qrmL0z5nrEihCQvG1Xm8iSPW41hXjwZaviGdBjfwpoE2/WrEgx8aU1fdJbMY7Sjh JDjPLZwJV6e9k+NSPEqj61dj00m44pfPfC9Gya4lnb3rP95u0g169YkIMoGGNPB/plPY lhJg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@mediatek.com header.s=dk header.b=aT6TVU3q; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.34 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=mediatek.com Received: from howler.vger.email (howler.vger.email. [23.128.96.34]) by mx.google.com with ESMTPS id iz17-20020a170902ef9100b001c589ba4a1bsi3725921plb.83.2023.09.22.07.22.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Sep 2023 07:22:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.34 as permitted sender) client-ip=23.128.96.34; Authentication-Results: mx.google.com; dkim=pass header.i=@mediatek.com header.s=dk header.b=aT6TVU3q; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.34 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=mediatek.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by howler.vger.email (Postfix) with ESMTP id 361A183F424E; Fri, 22 Sep 2023 00:22:44 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at howler.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231594AbjIVHWh (ORCPT <rfc822;chrisfriedt@gmail.com> + 30 others); Fri, 22 Sep 2023 03:22:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58456 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230520AbjIVHVl (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Fri, 22 Sep 2023 03:21:41 -0400 Received: from mailgw02.mediatek.com (unknown [210.61.82.184]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0B19118F; Fri, 22 Sep 2023 00:21:34 -0700 (PDT) X-UUID: a052dcb0591811ee8051498923ad61e6-20230922 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mediatek.com; s=dk; h=Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:CC:To:From; bh=o9TyNrz3SR4xQQtRCtzAKiPKHJh47LnMYSwL+P8jdFQ=; b=aT6TVU3q56sW/jIItTte1afQvQhDqxWQFRONPy1hU2h9zaTkBZfK6dF8MRQuF46O9Yy0/SL874z2GRTmPWqu72MuvRIkEEgd+/mTJ9pM7CTsso9bL2cC4421NJdWkAGhBxbVKvFYvRAQWC6mL6hgskMoFg3j81BplNckL20lTC4=; X-CID-P-RULE: Release_Ham X-CID-O-INFO: VERSION:1.1.32,REQID:7c8529fd-a94e-43bd-8175-1415a823eab2,IP:0,U RL:25,TC:0,Content:-25,EDM:0,RT:0,SF:0,FILE:0,BULK:0,RULE:Release_Ham,ACTI ON:release,TS:0 X-CID-META: VersionHash:5f78ec9,CLOUDID:d1ff54c3-1e57-4345-9d31-31ad9818b39f,B ulkID:nil,BulkQuantity:0,Recheck:0,SF:102,TC:nil,Content:0,EDM:-3,IP:nil,U RL:11|1,File:nil,Bulk:nil,QS:nil,BEC:nil,COL:0,OSI:0,OSA:0,AV:0,LES:1,SPR: NO,DKR:0,DKP:0,BRR:0,BRE:0 X-CID-BVR: 0 X-CID-BAS: 0,_,0,_ X-CID-FACTOR: TF_CID_SPAM_SNR,TF_CID_SPAM_ULN X-UUID: a052dcb0591811ee8051498923ad61e6-20230922 Received: from mtkmbs13n1.mediatek.inc [(172.21.101.193)] by mailgw02.mediatek.com (envelope-from <moudy.ho@mediatek.com>) (Generic MTA with TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384 256/256) with ESMTP id 1304453392; Fri, 22 Sep 2023 15:21:19 +0800 Received: from mtkmbs13n2.mediatek.inc (172.21.101.108) by MTKMBS14N1.mediatek.inc (172.21.101.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.26; Fri, 22 Sep 2023 15:21:18 +0800 Received: from mtksdccf07.mediatek.inc (172.21.84.99) by mtkmbs13n2.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.2.1118.26 via Frontend Transport; Fri, 22 Sep 2023 15:21:17 +0800 From: Moudy Ho <moudy.ho@mediatek.com> To: Chun-Kuang Hu <chunkuang.hu@kernel.org>, Philipp Zabel <p.zabel@pengutronix.de>, David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>, Mauro Carvalho Chehab <mchehab@kernel.org>, Matthias Brugger <matthias.bgg@gmail.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Hans Verkuil <hverkuil-cisco@xs4all.nl> CC: <dri-devel@lists.freedesktop.org>, <linux-mediatek@lists.infradead.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-media@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, "Moudy Ho" <moudy.ho@mediatek.com> Subject: [PATCH v6 05/16] dt-bindings: media: mediatek: mdp3: add support MT8195 RDMA Date: Fri, 22 Sep 2023 15:21:05 +0800 Message-ID: <20230922072116.11009-6-moudy.ho@mediatek.com> X-Mailer: git-send-email 2.18.0 In-Reply-To: <20230922072116.11009-1-moudy.ho@mediatek.com> References: <20230922072116.11009-1-moudy.ho@mediatek.com> MIME-Version: 1.0 Content-Type: text/plain X-TM-AS-Product-Ver: SMEX-14.0.0.3152-9.1.1006-23728.005 X-TM-AS-Result: No-10--9.713800-8.000000 X-TMASE-MatchedRID: O8Jgwx2XgRPhE4ic2WIDe2BDygfqHJtpCt59Uh3p/NX7SBmDTxVcWopb wG9fIuITLSHDQi/tZU+OEmLXxEuoAga1NXbjqus0tw+xHnsmQjNr9+Kgn2XgeCNGK7UC7ElMj9F j+RtK2eCJh4lfRksIUEUHNW/Q98GjJnLCYm9iI2lIRA38P/dwbiFNSRSGhTH1Qmp51f2+39lrQg SRg6yiRRmgGxBaKosCPyxPFILKgxtf4BpTN+neE7dQIb8hCnY+fS0Ip2eEHnyFh/DzryTTlvc8O Jc7+0VJjoczmuoPCq1MRatPwfJPwaLUKJgmeE5OOoIt+KrTpqHr+QpBUoNuBClkx3v7Ew13Qwym txuJ6y0= X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No X-TMASE-Result: 10--9.713800-8.000000 X-TMASE-Version: SMEX-14.0.0.3152-9.1.1006-23728.005 X-TM-SNTS-SMTP: 207E40E0AF5C08A661AF19D7796BDAEE95BBD0DB0C4DC5FB06006ED372971E992000:8 X-MTK: N X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_BLOCKED,RDNS_NONE, SPF_HELO_PASS,SPF_PASS,UNPARSEABLE_RELAY,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (howler.vger.email [0.0.0.0]); Fri, 22 Sep 2023 00:22:44 -0700 (PDT) X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1777747951429236232 X-GMAIL-MSGID: 1777747951429236232 |
Series |
introduce more MDP3 components in MT8195
|
|
Commit Message
Moudy Ho (何宗原)
Sept. 22, 2023, 7:21 a.m. UTC
Support for MT8195 RDMA has been added, allowing for
the configuration of multiple MDP3 pipes.
Furthermore, this particular device does not require
sharing SRAM with RSZ.
Signed-off-by: Moudy Ho <moudy.ho@mediatek.com>
---
.../media/mediatek,mdp3-rdma-8195.yaml | 64 +++++++++++++++++++
1 file changed, 64 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/mediatek,mdp3-rdma-8195.yaml
Comments
On Fri, Sep 22, 2023 at 03:21:05PM +0800, Moudy Ho wrote: > Support for MT8195 RDMA has been added, allowing for > the configuration of multiple MDP3 pipes. > Furthermore, this particular device does not require > sharing SRAM with RSZ. I'm sorry if I am going over past arguments, if this is 90% the same as the 8193 rdma, why the extraction + mostly duplicate file, rather than covering whatever clocks/mboxes differences with an if/then/else in a single file? Thanks, Conor. > > Signed-off-by: Moudy Ho <moudy.ho@mediatek.com> > --- > .../media/mediatek,mdp3-rdma-8195.yaml | 64 +++++++++++++++++++ > 1 file changed, 64 insertions(+) > create mode 100644 Documentation/devicetree/bindings/media/mediatek,mdp3-rdma-8195.yaml > > diff --git a/Documentation/devicetree/bindings/media/mediatek,mdp3-rdma-8195.yaml b/Documentation/devicetree/bindings/media/mediatek,mdp3-rdma-8195.yaml > new file mode 100644 > index 000000000000..f10139aec3c5 > --- /dev/null > +++ b/Documentation/devicetree/bindings/media/mediatek,mdp3-rdma-8195.yaml > @@ -0,0 +1,64 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/media/mediatek,mdp3-rdma-8195.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: MediaTek MT8195 Read Direct Memory Access > + > +maintainers: > + - Matthias Brugger <matthias.bgg@gmail.com> > + - Moudy Ho <moudy.ho@mediatek.com> > + > +description: | > + MediaTek Read Direct Memory Access(RDMA) component used to do read DMA. > + This type of component is configured when there are multiple MDP3 pipelines > + that belong to different MMSYS subsystems. > + It contains one line buffer to store the sufficient pixel data, and > + must be siblings to the central MMSYS_CONFIG node. > + For a description of the MMSYS_CONFIG binding, see > + Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml > + for details. > + > +allOf: > + - $ref: mediatek,mdp3-rdma-common.yaml# > + > +properties: > + compatible: > + items: > + - const: mediatek,mt8195-mdp3-rdma > + > + clocks: > + maxItems: 1 > + > + mboxes: > + maxItems: 5 > + > +required: > + - compatible > + > +additionalProperties: false > + > +examples: > + - | > + #include <dt-bindings/clock/mt8195-clk.h> > + #include <dt-bindings/gce/mt8195-gce.h> > + #include <dt-bindings/power/mt8195-power.h> > + #include <dt-bindings/memory/mt8195-memory-port.h> > + > + dma-controller@14001000 { > + compatible = "mediatek,mt8195-mdp3-rdma"; > + reg = <0x14001000 0x1000>; > + mediatek,gce-client-reg = <&gce1 SUBSYS_1400XXXX 0x1000 0x1000>; > + mediatek,gce-events = <CMDQ_EVENT_VPP0_MDP_RDMA_SOF>, > + <CMDQ_EVENT_VPP0_MDP_RDMA_FRAME_DONE>; > + power-domains = <&spm MT8195_POWER_DOMAIN_VPPSYS0>; > + iommus = <&iommu_vpp M4U_PORT_L4_MDP_RDMA>; > + clocks = <&vppsys0 CLK_VPP0_MDP_RDMA>; > + mboxes = <&gce1 12 CMDQ_THR_PRIO_1>, > + <&gce1 13 CMDQ_THR_PRIO_1>, > + <&gce1 14 CMDQ_THR_PRIO_1>, > + <&gce1 21 CMDQ_THR_PRIO_1>, > + <&gce1 22 CMDQ_THR_PRIO_1>; > + #dma-cells = <1>; > + }; > -- > 2.18.0 >
On Fri, 2023-09-22 at 16:46 +0100, Conor Dooley wrote: > On Fri, Sep 22, 2023 at 03:21:05PM +0800, Moudy Ho wrote: > > Support for MT8195 RDMA has been added, allowing for > > the configuration of multiple MDP3 pipes. > > Furthermore, this particular device does not require > > sharing SRAM with RSZ. > > I'm sorry if I am going over past arguments, if this is 90% the same > as > the 8193 rdma, why the extraction + mostly duplicate file, rather > than > covering whatever clocks/mboxes differences with an if/then/else in a > single file? > > Thanks, > Conor. > Hi Conor, As mentioned in [2/16], please disregard these changes. Sincerely, Moudy > > > > Signed-off-by: Moudy Ho <moudy.ho@mediatek.com> > > --- > > .../media/mediatek,mdp3-rdma-8195.yaml | 64 > > +++++++++++++++++++ > > 1 file changed, 64 insertions(+) > > create mode 100644 > > Documentation/devicetree/bindings/media/mediatek,mdp3-rdma- > > 8195.yaml > > > > diff --git a/Documentation/devicetree/bindings/media/mediatek,mdp3- > > rdma-8195.yaml > > b/Documentation/devicetree/bindings/media/mediatek,mdp3-rdma- > > 8195.yaml > > new file mode 100644 > > index 000000000000..f10139aec3c5 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/media/mediatek,mdp3-rdma- > > 8195.yaml > > @@ -0,0 +1,64 @@ > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > > +%YAML 1.2 > > +--- > > +$id: > > http://devicetree.org/schemas/media/mediatek,mdp3-rdma-8195.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: MediaTek MT8195 Read Direct Memory Access > > + > > +maintainers: > > + - Matthias Brugger <matthias.bgg@gmail.com> > > + - Moudy Ho <moudy.ho@mediatek.com> > > + > > +description: | > > + MediaTek Read Direct Memory Access(RDMA) component used to do > > read DMA. > > + This type of component is configured when there are multiple > > MDP3 pipelines > > + that belong to different MMSYS subsystems. > > + It contains one line buffer to store the sufficient pixel data, > > and > > + must be siblings to the central MMSYS_CONFIG node. > > + For a description of the MMSYS_CONFIG binding, see > > + Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.ya > > ml > > + for details. > > + > > +allOf: > > + - $ref: mediatek,mdp3-rdma-common.yaml# > > + > > +properties: > > + compatible: > > + items: > > + - const: mediatek,mt8195-mdp3-rdma > > + > > + clocks: > > + maxItems: 1 > > + > > + mboxes: > > + maxItems: 5 > > + > > +required: > > + - compatible > > + > > +additionalProperties: false > > + > > +examples: > > + - | > > + #include <dt-bindings/clock/mt8195-clk.h> > > + #include <dt-bindings/gce/mt8195-gce.h> > > + #include <dt-bindings/power/mt8195-power.h> > > + #include <dt-bindings/memory/mt8195-memory-port.h> > > + > > + dma-controller@14001000 { > > + compatible = "mediatek,mt8195-mdp3-rdma"; > > + reg = <0x14001000 0x1000>; > > + mediatek,gce-client-reg = <&gce1 SUBSYS_1400XXXX 0x1000 > > 0x1000>; > > + mediatek,gce-events = <CMDQ_EVENT_VPP0_MDP_RDMA_SOF>, > > + <CMDQ_EVENT_VPP0_MDP_RDMA_FRAME_DONE > > >; > > + power-domains = <&spm MT8195_POWER_DOMAIN_VPPSYS0>; > > + iommus = <&iommu_vpp M4U_PORT_L4_MDP_RDMA>; > > + clocks = <&vppsys0 CLK_VPP0_MDP_RDMA>; > > + mboxes = <&gce1 12 CMDQ_THR_PRIO_1>, > > + <&gce1 13 CMDQ_THR_PRIO_1>, > > + <&gce1 14 CMDQ_THR_PRIO_1>, > > + <&gce1 21 CMDQ_THR_PRIO_1>, > > + <&gce1 22 CMDQ_THR_PRIO_1>; > > + #dma-cells = <1>; > > + }; > > -- > > 2.18.0 > >
diff --git a/Documentation/devicetree/bindings/media/mediatek,mdp3-rdma-8195.yaml b/Documentation/devicetree/bindings/media/mediatek,mdp3-rdma-8195.yaml new file mode 100644 index 000000000000..f10139aec3c5 --- /dev/null +++ b/Documentation/devicetree/bindings/media/mediatek,mdp3-rdma-8195.yaml @@ -0,0 +1,64 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/media/mediatek,mdp3-rdma-8195.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: MediaTek MT8195 Read Direct Memory Access + +maintainers: + - Matthias Brugger <matthias.bgg@gmail.com> + - Moudy Ho <moudy.ho@mediatek.com> + +description: | + MediaTek Read Direct Memory Access(RDMA) component used to do read DMA. + This type of component is configured when there are multiple MDP3 pipelines + that belong to different MMSYS subsystems. + It contains one line buffer to store the sufficient pixel data, and + must be siblings to the central MMSYS_CONFIG node. + For a description of the MMSYS_CONFIG binding, see + Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml + for details. + +allOf: + - $ref: mediatek,mdp3-rdma-common.yaml# + +properties: + compatible: + items: + - const: mediatek,mt8195-mdp3-rdma + + clocks: + maxItems: 1 + + mboxes: + maxItems: 5 + +required: + - compatible + +additionalProperties: false + +examples: + - | + #include <dt-bindings/clock/mt8195-clk.h> + #include <dt-bindings/gce/mt8195-gce.h> + #include <dt-bindings/power/mt8195-power.h> + #include <dt-bindings/memory/mt8195-memory-port.h> + + dma-controller@14001000 { + compatible = "mediatek,mt8195-mdp3-rdma"; + reg = <0x14001000 0x1000>; + mediatek,gce-client-reg = <&gce1 SUBSYS_1400XXXX 0x1000 0x1000>; + mediatek,gce-events = <CMDQ_EVENT_VPP0_MDP_RDMA_SOF>, + <CMDQ_EVENT_VPP0_MDP_RDMA_FRAME_DONE>; + power-domains = <&spm MT8195_POWER_DOMAIN_VPPSYS0>; + iommus = <&iommu_vpp M4U_PORT_L4_MDP_RDMA>; + clocks = <&vppsys0 CLK_VPP0_MDP_RDMA>; + mboxes = <&gce1 12 CMDQ_THR_PRIO_1>, + <&gce1 13 CMDQ_THR_PRIO_1>, + <&gce1 14 CMDQ_THR_PRIO_1>, + <&gce1 21 CMDQ_THR_PRIO_1>, + <&gce1 22 CMDQ_THR_PRIO_1>; + #dma-cells = <1>; + };