From: Matthias Brugger <matthias.bgg@gmail.com>
To: Moudy Ho <moudy.ho@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-clk@vger.kernel.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v6 2/4] dt-bindings: arm: mediatek: mmsys: Add support for MT8195 VPPSYS
Date: Mon, 30 Jan 2023 12:27:52 +0100 [thread overview]
Message-ID: <c8023960-3361-91a3-6fdb-7c66bcabd2e9@gmail.com> (raw)
In-Reply-To: <20230118031509.29834-3-moudy.ho@mediatek.com>
On 18/01/2023 04:15, Moudy Ho wrote:
> 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>
Applied, thanks!
> ---
> .../devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
> index 84de12709323..b08ae7405b1a 100644
> --- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
> +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
> @@ -33,6 +33,8 @@ properties:
> - mediatek,mt8186-mmsys
> - mediatek,mt8188-vdosys0
> - mediatek,mt8192-mmsys
> + - mediatek,mt8195-vppsys0
> + - mediatek,mt8195-vppsys1
> - mediatek,mt8365-mmsys
> - const: syscon
>
_______________________________________________
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:[~2023-01-30 11:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 3:15 [PATCH v6 0/4] Migrate MT8195 VPPSYS 0/1 to mtk-mmsys driver Moudy Ho
2023-01-18 3:15 ` [PATCH v6 1/4] dt-bindings: arm: mediatek: migrate MT8195 vppsys0/1 " Moudy Ho
2023-01-19 11:14 ` Krzysztof Kozlowski
2023-01-19 16:08 ` Matthias Brugger
2023-01-26 2:05 ` Stephen Boyd
2023-01-26 14:32 ` Matthias Brugger
2023-01-26 14:33 ` Matthias Brugger
2023-01-27 23:20 ` Stephen Boyd
2023-01-18 3:15 ` [PATCH v6 2/4] dt-bindings: arm: mediatek: mmsys: Add support for MT8195 VPPSYS Moudy Ho
2023-01-18 15:59 ` Rob Herring
2023-01-30 11:27 ` Matthias Brugger [this message]
2023-01-18 3:15 ` [PATCH v6 3/4] clk: mediatek: remove MT8195 vppsys/0/1 simple_probe Moudy Ho
2023-01-19 15:50 ` Matthias Brugger
2023-01-27 23:20 ` Stephen Boyd
2023-01-30 19:36 ` Stephen Boyd
2023-01-31 1:57 ` Moudy Ho (何宗原)
2023-01-31 8:33 ` AngeloGioacchino Del Regno
2023-01-31 9:50 ` Chen-Yu Tsai
2023-02-07 1:58 ` Moudy Ho (何宗原)
2023-01-18 3:15 ` [PATCH v6 4/4] soc: mediatek: mmsys: add support for MT8195 VPPSYS Moudy Ho
2023-01-30 11:28 ` Matthias Brugger
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=c8023960-3361-91a3-6fdb-7c66bcabd2e9@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=moudy.ho@mediatek.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).