From: Moudy Ho <moudy.ho@mediatek.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Chun-Kuang Hu <chunkuang.hu@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
Moudy Ho <moudy.ho@mediatek.com>
Subject: [PATCH v2 1/7] dt-bindings: arm: mediatek: mmsys: Add support for MT8195 VPPSYS
Date: Tue, 11 Oct 2022 15:03:50 +0800 [thread overview]
Message-ID: <20221011070356.682-2-moudy.ho@mediatek.com> (raw)
In-Reply-To: <20221011070356.682-1-moudy.ho@mediatek.com>
For MT8195, VPPSYS0 and VPPSYS1 are 2 display pipes with
hardware differences in power domains, clocks and subsystem counts,
which should be determined by compatible names.
Signed-off-by: Moudy Ho <moudy.ho@mediatek.com>
---
.../devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
index 0711f1834fbd..493aa9e8d484 100644
--- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
+++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
@@ -48,7 +48,10 @@ properties:
- const: syscon
- items:
- - const: mediatek,mt8195-vdosys0
+ - enum:
+ - mediatek,mt8195-vdosys0
+ - mediatek,mt8195-vppsys0
+ - mediatek,mt8195-vppsys1
- const: mediatek,mt8195-mmsys
- const: syscon
--
2.18.0
next prev parent reply other threads:[~2022-10-11 7:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 7:03 [PATCH v2 0/7] add support for MT8195 VPPSYS on MMSYS and MUTEX Moudy Ho
2022-10-11 7:03 ` Moudy Ho [this message]
2022-10-11 12:21 ` [PATCH v2 1/7] dt-bindings: arm: mediatek: mmsys: Add support for MT8195 VPPSYS Krzysztof Kozlowski
[not found] ` <20221011070356.682-6-moudy.ho@mediatek.com>
2022-10-11 10:09 ` [PATCH v2 5/7] soc: mediatek: mmsys: add config api for RSZ switching and DCM AngeloGioacchino Del Regno
[not found] ` <20221011070356.682-8-moudy.ho@mediatek.com>
2022-10-11 10:09 ` [PATCH v2 7/7] soc: mediatek: mutex: support MT8195 VPPSYS AngeloGioacchino Del Regno
[not found] ` <20221011070356.682-7-moudy.ho@mediatek.com>
2022-10-11 10:09 ` [PATCH v2 6/7] soc: mediatek: mutex: Add mtk_mutex_set_mod support to set MOD1 AngeloGioacchino Del Regno
[not found] ` <20221011070356.682-3-moudy.ho@mediatek.com>
2022-10-11 10:09 ` [PATCH v2 2/7] dt-bindings: soc: mediatek: Add support for MT8195 VPPSYS AngeloGioacchino Del Regno
2022-10-11 12:22 ` Krzysztof Kozlowski
[not found] ` <20221011070356.682-4-moudy.ho@mediatek.com>
2022-10-11 12:23 ` [PATCH v2 3/7] dts: arm64: mt8195: add MMSYS and MUTEX configuration for VPPSYS Krzysztof Kozlowski
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=20221011070356.682-2-moudy.ho@mediatek.com \
--to=moudy.ho@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®