From: Rob Herring <robh@kernel.org>
To: Moudy Ho <moudy.ho@mediatek.com>
Cc: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
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>,
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
Subject: Re: [PATCH v8 02/16] dt-bindings: media: mediatek: mdp3: merge the indentical RDMA under display
Date: Mon, 30 Oct 2023 14:22:32 -0500 [thread overview]
Message-ID: <20231030192232.GA1922580-robh@kernel.org> (raw)
In-Reply-To: <20231030100022.9262-3-moudy.ho@mediatek.com>
On Mon, Oct 30, 2023 at 06:00:08PM +0800, Moudy Ho wrote:
> To simplify maintenance and avoid branches, the identical component
> should be merged and placed in the path belonging to the MDP
> (from display/* to media/*).
>
> In addition, currently only MDP utilizes RDMA through CMDQ, and the
> necessary properties for "mediatek,gce-events", and "mboxes" have been
> set up for this purpose.
> Within DISP, it directly receives component interrupt signals.
>
> Signed-off-by: Moudy Ho <moudy.ho@mediatek.com>
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> ---
> .../display/mediatek/mediatek,mdp-rdma.yaml | 88 -------------------
> .../bindings/media/mediatek,mdp3-rdma.yaml | 55 +++++++++---
> 2 files changed, 45 insertions(+), 98 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,mdp-rdma.yaml
> diff --git a/Documentation/devicetree/bindings/media/mediatek,mdp3-rdma.yaml b/Documentation/devicetree/bindings/media/mediatek,mdp3-rdma.yaml
> index 3e128733ef53..c043204cf210 100644
> --- a/Documentation/devicetree/bindings/media/mediatek,mdp3-rdma.yaml
> +++ b/Documentation/devicetree/bindings/media/mediatek,mdp3-rdma.yaml
> @@ -20,8 +20,9 @@ description: |
>
> properties:
> compatible:
> - items:
> - - const: mediatek,mt8183-mdp3-rdma
> + enum:
> + - mediatek,mt8183-mdp3-rdma
> + - mediatek,mt8195-vdo1-rdma
>
> reg:
> maxItems: 1
> @@ -49,17 +50,18 @@ properties:
> maxItems: 1
>
> clocks:
> - items:
> - - description: RDMA clock
> - - description: RSZ clock
> + minItems: 1
> + maxItems: 2
Keep the description here and just add 'minItems: 1' and...
>
> iommus:
> maxItems: 1
>
> mboxes:
> - items:
> - - description: used for 1st data pipe from RDMA
> - - description: used for 2nd data pipe from RDMA
> + minItems: 1
> + maxItems: 2
> +
> + interrupts:
> + maxItems: 1
>
> '#dma-cells':
> const: 1
> @@ -68,13 +70,46 @@ required:
> - compatible
> - reg
> - mediatek,gce-client-reg
> - - mediatek,gce-events
> - power-domains
> - clocks
> - iommus
> - - mboxes
> - '#dma-cells'
>
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: mediatek,mt8183-mdp3-rdma
> +
> + then:
> + properties:
> + clocks:
> + items:
> + - description: RDMA clock
> + - description: RSZ clock (shared SRAM with RDMA)
Then just need 'minItems: 2' here and...
> +
> + mboxes:
> + items:
> + - description: used for 1st data pipe from RDMA
> + - description: used for 2nd data pipe from RDMA
> +
> + required:
> + - mboxes
> + - mediatek,gce-events
> +
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: mediatek,mt8195-vdo1-rdma
> +
> + then:
> + properties:
> + clocks:
> + items:
> + - description: RDMA clock
'maxItems: 1' here.
The same thing applies to mboxes.
Rob
next prev parent reply other threads:[~2023-10-30 19:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 10:00 [PATCH v8 00/16] introduce more MDP3 components in MT8195 Moudy Ho
2023-10-30 10:00 ` [PATCH v8 01/16] dt-bindings: media: mediatek: mdp3: correct RDMA and WROT node with generic names Moudy Ho
2023-10-30 10:00 ` [PATCH v8 02/16] dt-bindings: media: mediatek: mdp3: merge the indentical RDMA under display Moudy Ho
2023-10-30 19:22 ` Rob Herring [this message]
2023-10-30 10:00 ` [PATCH v8 03/16] dt-bindings: media: mediatek: mdp3: add config for MT8195 RDMA Moudy Ho
2023-10-30 19:26 ` Rob Herring
2023-10-31 6:39 ` Moudy Ho (何宗原)
2023-10-30 10:00 ` [PATCH v8 04/16] dt-bindings: media: mediatek: mdp3: add compatible for MT8195 RSZ Moudy Ho
2023-10-30 10:00 ` [PATCH v8 05/16] dt-bindings: media: mediatek: mdp3: add compatible for MT8195 WROT Moudy Ho
2023-10-30 10:00 ` [PATCH v8 06/16] dt-bindings: media: mediatek: mdp3: add component FG for MT8195 Moudy Ho
2023-10-30 10:00 ` [PATCH v8 07/16] dt-bindings: media: mediatek: mdp3: add component HDR " Moudy Ho
2023-10-30 10:00 ` [PATCH v8 08/16] dt-bindings: media: mediatek: mdp3: add component STITCH " Moudy Ho
2023-10-30 10:00 ` [PATCH v8 09/16] dt-bindings: media: mediatek: mdp3: add component TCC " Moudy Ho
2023-10-30 10:00 ` [PATCH v8 10/16] dt-bindings: media: mediatek: mdp3: add component TDSHP " Moudy Ho
2023-10-30 10:00 ` [PATCH v8 11/16] dt-bindings: display: mediatek: aal: add compatible " Moudy Ho
2023-10-30 10:00 ` [PATCH v8 12/16] dt-bindings: display: mediatek: color: " Moudy Ho
2023-10-30 10:00 ` [PATCH v8 13/16] dt-bindings: display: mediatek: merge: " Moudy Ho
2023-10-30 10:00 ` [PATCH v8 14/16] dt-bindings: display: mediatek: ovl: " Moudy Ho
2023-10-30 10:00 ` [PATCH v8 15/16] dt-bindings: display: mediatek: split: " Moudy Ho
2023-10-30 10:00 ` [PATCH v8 16/16] dt-bindings: display: mediatek: padding: " Moudy Ho
2023-10-30 19:26 ` Rob Herring
2023-10-31 7:43 ` Moudy Ho (何宗原)
2023-10-31 8:57 ` Moudy Ho (何宗原)
2023-10-31 7:37 ` Moudy Ho (何宗原)
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=20231030192232.GA1922580-robh@kernel.org \
--to=robh@kernel.org \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=moudy.ho@mediatek.com \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=tzimmermann@suse.de \
/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).